Unable to start service - potential corruption in config files

[SprMario]

Hi all,

Not long ago I found out that my sites were not reachable anymore due to "invalid ssl certificates: error code 526". I initially tried to recreate the image because I was unable to reach the service, by doing that I couldn't start the image anymore at all:

I could successfully retrieve the database information but I am kinda stuck. I cant reach NPM to handle certs so I cant approach any of my services. If I dig deeper in the logs I also notice some weird error in docker:

This is the conf file content:

Version I am on is 2.13.3

Does anyone know what I can do?

[sleighton]

I saw this error mentioned somewhere, the problem is a community install script that is no longer compatible. That poster got things working by doing a regular docker compose. You might try search for that error message for more info. Sorry I can't remember where I saw it, Discord, Github or Reddit probably.

[jc21]

Yes that is likely it. However if you do still have the problem with vanilla configuration, you can remove the 2.conf file from the folder you're mounting and restart. This is the nginx config file for that proxy host, and to regenerate it, just find it in the interface, edit and save.

[SprMario]

I have a test image up and running but I do not know how to restore my original configuration. I do have the sql backup but there is no way to restore it in the UI

[SprMario]

Can anyone help out with restoring my old config using the sql file?