Nirvash

Honestly I'd rather find a fix that will work for everyone.
 
Edit: I think I figured it out:
Checked /var/log/nginx/error.log and had these errors:
2025/05/06 15:12:09 [emerg] 13282#13282: "nchan_shared_memory_size" directive is duplicate in /etc/nginx/conf.d/servers.conf:4 2025/05/06 19:18:44 [emerg] 960158#960158: "nchan_shared_memory_size" directive is duplicate in /etc/nginx/conf.d/servers.conf:4  
Which points me to some instructions I found in the forums some time ago that suggested editing /etc/nginx/nginx.conf to add more nchan_shared memory_size among other things.
 
I needed to go back to /boot/config/go and remove the line that alters nchan_shared_memory_size and reboot again. That fixed the issue.
 
# Fix NGINX limits to stop stupid log messages sed -i "s;zone=authlimit:1m rate=30r/m;zone=authlimit:1m rate=60r/m;g" /etc/nginx/nginx.conf sed -i "s;zone=authlimit burst=20;zone=authlimit burst=60;g" /etc/nginx/conf.d/locations.conf # Fix nchan memory leak REMOVE THIS LINE ->>>> sed -z 's|nchan publishers\n\t#|nchan publishers\n\t#\n\tnchan_shared_memory_size 2M;|' -i /etc/rc.d/rc.nginx sed -z 's|nchan_publisher;|nchan_publisher;\n\t error_log /var/log/nginx/nchan_error.log;|' -i /etc/rc.d/rc.nginx /usr/sbin/nginx -s reload  
 
I suggest the devs to enable nginx error logs into the diagnostics. AFAIK you don't have this info when people share their diags and you are blind against these issues. I'm fortunate I had that enabled.

Well, turns out all these strange extra routing table entries were the issue.
 
Delete them with ip link delete <interface name>
 
And done.

Turns out I just needed to edit /data/nginx/stream/1.conf in appdata, restart NPM, and then change all the proxies from hostname to IP and everything is working fine again.