A Discourse server I’m trying to upgrade is stuck restarting (and due to the constant restarts I can’t seem to be able to get a shell on it), this is what I have from ./launcher logs app: [Fri 29 Mar 12:51:47 UTC 2019] Run reload cmd: sv reload nginx warning: nginx: unable to open supervise/ok: fil…

I agree that ideally the VM server and the DNS would be configured for IPv6, but this isn’t the case with this server and I might not be the only person still running a server using IPv4 so it appears fairly reasonable to me to disable IPv6 in the Nginx config in the Docker container, it is a simply…

I’d check disk space and rebuild the container.

The virtual server has one partition and it doesn’t seem too bad in terms of usage, do you think more space might be the issue here? df -h | egrep '(/$|^Filesystem)' Filesystem Size Used Avail Use% Mounted on /dev/vda2 64G 44G 17G 72% / I have tried rebuilding the container sever…

Do you have plugins installed? What happens when you rebuild? (Space looks fine.)

The rebuild seems to go OK but then the container keep restarting and I can’t get a shell on the container because of this — I want to see if /run exists — the error logs above appear to be saying that this directory doesn’t exist… After a rebuild with all the plugins disabled it looks OK to start …

Do you have anything in your yml that affects the nginx config?

This plugin was enabled (but isn’t for now): https://github.com/muhlisbc/discourse-images-guardian And I’m currently trying to work out if this commit broke the Nginx config: https://github.com/muhlisbc/discourse-images-guardian/commit/8a79b86d0a0f344504a75a38eb417c820787b3bb I can’t see anythin…

But this virtual server don’t have IPv6 configured and it appears that as a result the IPv6 line in /etc/nginx/letsencrypt.conf: listen [::]:80; Is the thing that is stopping Nginx from starting — I’m not sure what solution you are suggesting, my solution appears to work: I, [2019-03-29T14:57…

There’s no reason to disable IPv6 in the VM, you’re just setting yourself up for trouble.

FWIW, I just did an install on a DigitalOcean droplet that does not have ipv6 configured and there is no problem. Here’s this from an install from a couple days ago: root@forum:~# grep ipv6 /etc/sysctl.conf #net.ipv6.conf.all.forwarding=1 #net.ipv6.conf.all.accept_redirects = 0 #net.ipv6.conf.all…

Ngnix fails to start on VM with IPv6 disabled

Product Support Self-hosting

supermathie (Michael Brown) March 29, 2019, 2:58pm 8

Don’t disable IPv6 support. From the SF answer you linked:

Topic		Replies	Views
Docker constantly restarting after turning off ipv6 no longer running on the host Self-hosting	3	594	April 3, 2023
NGINX fails to start Self-hosting	16	2708	March 9, 2024
Is it possible to install with IPv6 disabled? (Spoiler: I don't think so) Self-hosting	2	243	September 2, 2025
Nginx not binding to ipv6 address using the Discourse Docker image Self-hosting	8	812	February 17, 2021
Discourse not serving pages Self-hosting	25	3418	August 4, 2020

Ngnix fails to start on VM with IPv6 disabled

Related topics