Access Seafile with Nginx Proxy Manager via SSL

[ZerkMen]

I have successfully installed Seafile using the Seafile Official Guide and got it running on port 8080. Now I want to use https on port 443 (10443). I get the error 502 Bad Gateway.

How can I solve this problem?

[piranha771]

Please show me your NPM config. Please be aware that NPM is a reverse proxy. So your application (seafile) is only communicating on port 8080.

So

Plain HTTP no SSL
[Seafile Container] <---Port 8080---> [NPM Container] <---Port 80---> Client/Browser

Secure HTTPS / SSL
[Seafile Container] <---Port 8080---> [NPM Container] <--Port 443--> Client/Browser

[Kurasami]

I have successfully installed Seafile using the Seafile Official Guide and got it running on port 8080. Now I want to use https on port 443 (10443). I get the error 502 Bad Gateway.

How can I solve this problem?

If you are using Unraid like I am. You need to click "more settings" when editing the container on Unraid. Then add a port for 443. I had the same problem and I am also using Nginxproxymanager. When I added a port for 443, (I used 9443) it worked fine.

Just make sure that your Nginxproxymanager is set to "http" and uses the HTTP port, so your config upgrades you to SSL when you try to connect, but that http traffic can still flow freely.

EDIT: Here is how mine looks:

And here is the config on Unraid (the official docker image on Unraid has a long list of instructions):

Lastly, you will get a "network error" when you try to upload a file. Make sure that you set the domain.tld in your Seafile instance as the admin user like so:

This should be all you need to get going.