Open flo-at opened 3 years ago
It's crazy there is no response of this PR at all. I guess they only do things when they get support requests from paying customers.
@robclancy This is also true for other (bigger) problems in Seafile. If you are still using it, you might want to consider switching to something else. There are concerns that it's not safe anymore to expose Seafile on a public host. Also the repository is a hot mess.
These changes to the nginx config files/templates make IPv6 work.
For IPv6-only setups this solves a more complex problem where you need to initially start the container with Let’s Encrypt disabled because it cannot get the chellenge file due to this missing listen directive in the nginx config. Then you would need to manually change the nginx config which is only generated at the initial start-up and therefore does not include the TLS config.