Hi!

 

sorry for setting this in the wrong thread but wasant able to set it on the application support > docker container.

 

im trying to setup Seafile and then using swag to reverse proxy it to only use the SSL ports open, i have setup a docker with seafile-mc and out of box it works fine to get to the site locally on the lan ip/port but as soon i setup swag ontop of it the http site just gets bad gateway(should be normal) but https:// only gives me ERR_CONNECTION_REFUSED or if i try to use the hostname i setup with cloudflare that doesnt work either it only comes to depending on if i use to proxy tro cloudlfare there "error 522" page that connection to cloudflare works but the connection to seafile doesnt work or i get something with SSL error.

 

It feels like something is missing in the swag config file but everything else i host out of the same server works and i dont pretty much the same thing on all of them changeing the variables that they need of course.

 

attached is how i setup the container in unraid, with the subdomain file in swag

 

 

second picture how the internal docker ip vs external side and third picture is the firewall rule i have in my router as i want all traffic going through 443/SSL and go through swag this seems to work on everything i host Jellyfin etc etc but seafile for some reason doesnt want to work like this.

 

so am i missing something or is the sample file from swag not fully finished?

seafile.subdomain.conf

 

both seafile and swag sits under the same internal UnRaid network tower as my other dockers that i am and will be hosting through swag just to make it easier to use the hostnames

Edited July 17, 20223 yr by Nothingtoxic

Have you checked the url in seafile settings itself?

23 hours ago, Aran said:

Have you checked the url in seafile settings itself?

 

will check these again, but correct my thinking, as i set it up as seafile.* and made a cname on cloudflare do i need another cname for the FILE_SERVER_ROOT aswell?