-
Notifications
You must be signed in to change notification settings - Fork 678
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Apache IP Binding with IPv6 #3441
Comments
Hi, may I ask why 127.0.0.1 is not sufficient for you? |
Thanks for your reply. Well, there are two main reasons for that.
As per documentation, if you run behind a reverse proxy and nextcloud is being targeted by an IP you should use 0.0.0.0 Nextcloud AIO in general seems to support IPv6 https://github.com/nextcloud/all-in-one/blob/main/docker-ipv6-support.md |
|
We would need to make sure that the |
compose supports [], so you mean that they need to be escaped?
|
|
This is now released with v7.4.0 Beta. Testing and feedback is welcome! See https://github.com/nextcloud/all-in-one#how-to-switch-the-channel |
Currently I use the beta channel and everything seems to work fine. I may mention that it wasn't enough to set APACHE_IP_BINDING to IPv6 to fully support IPv6.
I looking forward to see it on the latest channel. |
Steps to reproduce
Expected behavior
Apache should bind to [::]
Actual behavior
Error message:
You provided an ip-address for the apache container's ip-binding but it was not a valid ip-address.
It is set to '[::]'.
Host OS
Alpine Linux v3.13
Nextcloud AIO version
nextcloud/all-in-one:latest
Current channel
You are running the latest channel
Other valuable info
The host runs behind a reverse proxy
The text was updated successfully, but these errors were encountered: