I see in the web template where it checks to see if /proc/net/if_inet6 exists and turns off the listen for [::]:80, but there’s still one in the default nginx file. I added these to try to fix that: - exec: sed -i '/listen \[::\]:80 default_server;/d' /etc/nginx/sites-available/default - exec:…

Doubtful. I’ve also recently removed a similar line in the ssl file recently with some eyes by @schleifer - just hadn’t gotten to the web template yet. IPv6 support is pretty baked into our package, so it’s fairly difficult to rip out cleanly everywhere, and provide verification/support for it.

Is it possible to install with IPv6 disabled? (Spoiler: I don't think so)

Product Support Self-hosting

pfaffman (Jay Pfaffman) September 2, 2025, 11:14pm 3

Thanks so much for the quick confirmation! I was pretty sure that was the case, and am relieved that I hadn’t overlooked some obvious simple solution.

Topic		Replies	Views
Nginx not binding to ipv6 address using the Discourse Docker image Self-hosting	8	810	February 17, 2021
Docker constantly restarting after turning off ipv6 no longer running on the host Self-hosting	3	592	April 3, 2023
Ngnix fails to start on VM with IPv6 disabled Self-hosting unsupported-install	14	1703	March 29, 2019
Nginx not listen on IPv6 if not use HTTPS Self-hosting	2	969	May 25, 2022
Using IPv6 NAT function in Docker with Discourse Self-hosting	4	971	April 5, 2023

Is it possible to install with IPv6 disabled? (Spoiler: I don't think so)

Related topics