Lorell2 Posted April 17, 2019 Report Share Posted April 17, 2019 I installed Resilio on a new/clean Ubuntu 18.04 server by following these instructions. https://www.linuxbabe.com/ubuntu/install-resilio-sync-btsync-ubuntu-18-04-18-10 Because the server is in the cloud, I installed the reverse-proxy nginx proxy following the same instructions. When I browse to the public hostname of the device it works quite well (even using https!). It automatically appends /gui/ to the end of my URL. I would like to be able to browse to the same web server in a different directory to access regular html pages and use a subfolder for Resilio Sync. Currently I browse to: https://fake.hostname.org and am redirected to https://fake.hostname.org/gui/ and the web uUI for Resilio Sync comes up. I would like to browse to https://fake.hostname.org and get regular HTML pages in the regular nginx html folder ( /var/share/nginx/html/ ? ). And I would like to browse to https://fake.hostname.org/resilio and get the Resilio Sync UI. How do I go about doing this? This would allow me to use the server as both a regular webserver and as Resilio Sync server. Thanks! Here is my current /etc/nginx/conf.d/resilio-sync.conf: server { server_name fake.hostname.org; access_log /var/log/nginx/resilio_access.log; error_log /var/log/nginx/resilio_error.log; location / { proxy_pass http://127.0.0.1:8888; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } listen 443 ssl; # managed by Certbot ssl_certificate /etc/letsencrypt/live/fake.hostname.org/fullchain.pem; # managed by Certbot ssl_certificate_key /etc/letsencrypt/live/fake.hostname.org/privkey.pem; # managed by Certbot include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot add_header Strict-Transport-Security "max-age=31536000" always; # managed by Certbot ssl_trusted_certificate /etc/letsencrypt/live/fake.hostname.org/chain.pem; # managed by Certbot ssl_stapling on; # managed by Certbot ssl_stapling_verify on; # managed by Certbot } server { if ($host = fake.hostname.org) { return 301 https://$host$request_uri; } # managed by Certbot listen 80; server_name fake.hostname.org; access_log /var/log/nginx/resilio_access.log; error_log /var/log/nginx/resilio_error.log; location / { proxy_pass http://127.0.0.1:8888; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } } Quote Link to comment Share on other sites More sharing options...
Timbo Posted May 7, 2019 Report Share Posted May 7, 2019 I would suggest making a separate /etc/nginx/conf.d/browsing.conf whereby server_name will use something like browsing.hostname.org. Just add another A record to your domain DNS. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.