Username: Password:

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - miwi

Pages: [1]
In a lot of groups are advices not to run the new UI on a public server, below is a small how to, to protect your UI with a password behind the proxy.

First of we to install nginx depends on your operation system, in this case we use debian/ubuntu.

sudo apt install nginx

then you navigate to /etc/nginx/site-enable/ with

cd /etc/nginx/sites-enabled

<editor of your choice>  default
remove everything inside and replace it with

server {
    listen 80;

    server_name your_hostname;

    location / {
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;
   auth_basic "Restricted Content";
        auth_basic_user_file /etc/nginx/.htpasswd;

Create the Password File
To start out, we need to create the file that will hold our username and password combinations. You can do this by using the OpenSSL utilities that may already be available on your server. Alternatively, you can use the purpose-made htpasswd utility included in the apache2-utils package (Nginx password files use the same format as Apache). Choose the method below that you like best.

Create the Password File Using the OpenSSL Utilities

If you have OpenSSL installed on your server, you can create a password file with no additional packages. We will create a hidden file called .htpasswd in the /etc/nginx configuration directory to store our username and password combinations.

You can add a username to the file using this command. We are using sammy as our username, but you can use whatever name you'd like:

sudo sh -c "echo -n 'miwi:' >> /etc/nginx/.htpasswd"
Next, add an encrypted password entry for the username by typing:

sudo sh -c "openssl passwd -apr1 >> /etc/nginx/.htpasswd"
You can repeat this process for additional usernames. You can see how the usernames and encrypted passwords are stored within the file by typing:

cat /etc/nginx/.htpasswd

Create the Password File Using Apache Utilities

While OpenSSL can encrypt passwords for Nginx authentication, many users find it easier to use a purpose-built utility. The htpasswd utility, found in the apache2-utils package, serves this function well.

Install the apache2-utils package on your server by typing:

sudo apt-get install apache2-utils
Now, you have access to the htpasswd command. We can use this to create a password file that Nginx can use to authenticate users. We will create a hidden file for this purpose called .htpasswd within our /etc/nginx configuration directory.

The first time we use this utility, we need to add the -c option to create the specified file. We specify a username (miwi in this example) at the end of the command to create a new entry within the file:

sudo htpasswd -c /etc/nginx/.htpasswd miwi
You will be asked to supply and confirm a password for the user.

Leave out the -c argument for any additional users you wish to add:

sudo htpasswd /etc/nginx/.htpasswd another_user
If we view the contents of the file, we can see the username and the encrypted password for each record:

cat /etc/nginx/.htpasswd

Please replace the username miwi with your own username.

Have fun!

General Discussion / Re: Question about 5.0.4 experiances
« on: September 28, 2017, 01:39:33 PM »
Ok ic. I should have read github first.. sorry for that. Well then I will just wait for 5.0.5 to see if it improves.

Should be in the next few days.

General Discussion / Re: 2 License
« on: September 27, 2017, 09:17:54 AM »
Upgrades are free, as it has always been. Just needs validation for version 501 and higher (only once, generally a matter of an hour or so, but there was a cue since the first v.5xx release). The validation can only be received from Gunthar personally (no charge for license holders). I believe he wants to make sure only true (or better genuine?) license holders can upgrade to versions 501 and higher. From what I'm reading, there seem to be counterfeit/hacked licences on the market which by this additional validation procedure are denied upgrades.


Thank you so much!

General Discussion / Re: 2 License
« on: September 26, 2017, 05:07:59 PM »
Thanks for your input. Just double checking update are no longer free?

General Discussion / 2 License
« on: September 26, 2017, 01:47:10 PM »
I am not sure if that is the right place to post that question... apologise upfront if it isnt.

So my question is, my friend and me plan to buy 2 bittrex licenses, so since there are 2 license 2 different pplz is it allow to join then the telegram groups for both or just one person (the license holder). Second question would be lets say my friend dont wanna upgrade, I am allowed to upgrade the license for the next version. (from my understanding for each release we have to request for an upgrade for the next higher version.)

Thanks in advance.

Pages: [1]