I just set up a Seafile Server (self-hosted Cloud) with Nginx. This Seafile-server uses https (443). So to access the server from my LAN I use: https://seafile
With my SG230 I have to setup the WAF accordingly. The "real webserver" is HTTPS with Port 443, and as the "virtual webserver" I set it to HTTP & 80. Now I can access my Seafile cloud from https://seafile (internal) and also http://cloud.my-domain.com (external). I'm not sure how this method is called (redirect http to https), but I think this is a "Reverse Proxy" with redirecting traffic.
I don't have a paid SSL-certificate, so I can't run https://cloud.my-domain.com.
I have only a self-signed SSL-certifcate. Now when I access the cloud from external over my http -> https redirection there is no SSL-warning at all. Works flawlessly!
When I connect now over http I'm pretty sure the cloud still works only with https (internally), the question is, if I input usernames & passwords now on the site http://cloud.my-domain.com, is it encrypted or not? (that's the whole point in running the cloud with HTTPS)
This thread was automatically locked due to age.
