Cloudron Forum

@nebulon great, glad it's already fixed! Then a start/stop of the app will resolve it.

This got fixed after rebooting the server and repairing all apps. For some reason, the server ran out of file descriptors

Perfect @BrutalBirdie .. Thanks a lot Man! What's this error? And how can we prevent this moving forward. Thanks!

Thank you. I will try cloudron-support --troubleshoot next time.

@Kubernetes Yeah this is specific to the Nginx Ingress Controller which runs on Kubernetes. It won’t be related to Cloudron at all since Cloudron doesn’t use Kubernetes. Cloudron won’t be vulnerable to this.

Quick update - The issue had nothing to do with Cloudron server and everything to do with the Nginx Proxy Manager host sitting in front of the Cloudron server. Good time to mention that NPM in front of a Cloudron server is not an officially supported Cloudron setup. Yet, with this being said, once Websockets relay was enabled on NPM proxy host, everything fell into places. Many many thanks for @nebulon and the cloudron team for their support as always.

Thanks, that worked!

@amoslipara this is a Cloudron forum . Not a Minecraft forum or a Linux help forum. Did you intend to post it here?

Just to note here, a server reboot often is not the best idea if some services are still up and running. Nearly everything can be fixed while the server is active and a reboot might just bring down those unnecessarily.

Many thanks, after deleting config file for freshrss the restart of nginx went OK.

@girish Ooh, that sounds handy! I almost wish for another broken nginx config just to try it!

@philkunz

@avatar1024 there is crash in cert renewal indeed. A fix is coming in 7.5.2

@alwynispat actually, https://forum.cloudron.io/topic/8321/forwarding-the-true-client-ip-address/ is the feature request . Let's continue there.

Issue was https://forum.cloudron.io/topic/6506/after-a-reboot-nginx-does-not-start

@girish sweet- that worked! I saw that's also what you said here: https://forum.cloudron.io/topic/5457/site-is-not-reachable/7 And is basically what's described in the troubleshooting as well. At first this was just an issue with the uninstalled containers, but then when I restarted for a cloudron update it took down the whole thing, which made me think ngnix really was broken Thank you!

@eddowding Ah, perfect. I actually sent you a note from support early today morning, but that was probably too late.

@nebulon perfect, thanks for confirming!

@shan 7.3.3 I believe.