Stopped Apps generate Cert errors
-
There is a pattern where an upgrade or restart of an app fails to bring it up with this error in the UI:
Nginx Error: Error reloading nginx: reverseproxy exited with code 1 signal nullThe logs show nginx failing to reload due to missing certs for some other app. That app on my system is stopped. So it seems stopped apps eventually lose their cert and cause this error.
Cert refresh problem or config cleanup problem?
From recent issue1, issue2, and more found on the forum, this is a pattern that should be prevented from happening.
I can use the manual temporary solutions there, or even come up with my own band-aid, but that doesn't solve the deeper issue. So I won't run those.
This is a request for the deeper maintenance fix to prevent this from occurring again.
-
Ah indeed, I overlooked that. So current Cloudron versions already have that fixed. The stop action now purges those nginx configs, however if you have a stopped app which got stopped in previous Cloudron versions (ie pre 7.1.0) then those may still be around.
-
There is a pattern where an upgrade or restart of an app fails to bring it up with this error in the UI:
Nginx Error: Error reloading nginx: reverseproxy exited with code 1 signal nullThe logs show nginx failing to reload due to missing certs for some other app. That app on my system is stopped. So it seems stopped apps eventually lose their cert and cause this error.
Cert refresh problem or config cleanup problem?
From recent issue1, issue2, and more found on the forum, this is a pattern that should be prevented from happening.
I can use the manual temporary solutions there, or even come up with my own band-aid, but that doesn't solve the deeper issue. So I won't run those.
This is a request for the deeper maintenance fix to prevent this from occurring again.
-
Hello @robi
Could you please provide the Cloudron version you are using where this issue arises?
If you run
cloudron-support --troubleshootThis should fix it.
But indeed it should not happen in the first place. -
Hello @robi
Thanks.
Did you try to runcloudron-support --troubleshootand did it solve the issue? -
hm strange, the
--troubleshootshould purge all .conf files for nginx where certs don't exist. Can you send the output of the tool to support@cloudron.io and maybe enable remote ssh access for us?@nebulon I'm sure it does. Perhaps review the OP.
If you'd like to inspect the system, I'm happy to email support@ towards the fix of the root cause, instead of a quick temp fix.
Ideally preventing certs from going missing, or catch the exception of missing certs and clean up automagically.
-
Ah indeed, I overlooked that. So current Cloudron versions already have that fixed. The stop action now purges those nginx configs, however if you have a stopped app which got stopped in previous Cloudron versions (ie pre 7.1.0) then those may still be around.
-
Ah indeed, I overlooked that. So current Cloudron versions already have that fixed. The stop action now purges those nginx configs, however if you have a stopped app which got stopped in previous Cloudron versions (ie pre 7.1.0) then those may still be around.
-
R robi has marked this topic as solved
