Cloudron Forum

@ei8fdb said in Cannot load certificate key .../_.sub.domain.org.key failed - No such file or directory: _.sub.domain.org.key One of the nginx config files is referencing this key. You can delete the config file and the key/cert file. You can find out which file is referencing it by grep'ing inside /etc/nginx/applications . Once deleted, you can systemctl restart nginx

@girish this was more for Nginx not starting, including 0 byte files. Happy to mod the FR to be more inclusive. Done.

@subven said in out of space error leading to missing certs: @girish there is no way to trigger certificate renewal over the (SSH) console? I'd like an answer to this question.. as I just ran into the missing cert problem too. Having deleted all the conf/cert files, and gotten nginx started, the UI is still not accessible after box restart. All apps are inaccessible too. box restart seems to recreate the /etc/nginx/applications/my.domain.conf BUT doesn't check if the /home/yellowtent/platformdata/nginx/certs/my.domain.host.cert is there. How are they regenerated from the CLI?

Thanks for the info, but we do not use this module, so we are all good.

@Mastadamus yes, reverse proxy is implemented in next release (7.3) - https://forum.cloudron.io/topic/6655/what-s-coming-in-7-3/21

@robi Yes, sorry, I just followed the tutorial that was previously posted by @scooke https://cloak.ist/blog/how-to-put-a-ghost-blog-at-a-subdirectory-using-cloudflare-workers/

Just wanted to say I've also hit just this issue. Cleaning up the nginx app config files did the trick but I wonder if this can be avoided in the future? Or may be it has already be addressed and I'm only hitting it because of some legacy stuff from previous Cloudron version? (this instance is currently running 7.5.0 but hasn't had a fresh install in a long while).

@ashkaptsov So, AppGyver's browser UI is going to make requests from the browser to n8n and baserow ? Can you tell us a bit more as to why would it want to do that? In general, adding CORS headers without knowing the app knowing about is a security hole.

I did a clean installation and restored a backup. Since than, everything is working fine. Thanks

@mastadamus thanks so much for investigating. I have removed it for next release (7.1) - https://git.cloudron.io/cloudron/box/-/commit/6492c9b71f80120413ff4ae7eefa2f03dc96ea0f

@mastadamus Can you add that as a feature request and mention this thread?

Yeah, I found this exact same spam text in another forum.

it's solved, it was a problem with resolv.conf. The DNS servers of my scaleway instance are not responding anymore ...

I am currently debugging that instance, but just for others to read up, using nginx -s reload as root usually reveals the syntax errors in config files right away, like it was in this instance as well.

nginx configs became corrupt. Once we got nginx up, it uninstalled. I am putting notes on why nginx configs were corrupt at https://forum.cloudron.io/topic/5457/site-is-not-reachable

@nebulon You try to make things easy for us but we'll screw it up somehow. ; )

@mehdi This my friend is a good point, thank you for pulling me out of the tunnel. lol

@nebulon there was no error reported by cloudron. The issue was that if I tried to curl, there was nothing returned back (I don't remember the exact reply -- sorry for that). Basically it was like nginx was not routing properly, as if nothing was running at the subdomain.

I patch the my.domainname.fr.conf with the missing part (taken from my other Cloudron server). I then uninstalled and re-installed jingo, and everything seems to work fine now.