My Nginx Proxy Manager had been working fine for years, no issues. Recently it stopped and I can't start it back up again. Rather, I start it, and then it looks like it's started but then it stops. I can't figure out what's wrong. I've tried removing and readding the container, deleting the image, moving the appdata folder to see if it was configs of somekind. i'm at a loss. I'm on 7.1.4, but I only updated today thinking that that was causing it, I was on 7.0.0 when I noticed the issue and since updating, same thing.

This seems to be the only error I can see in the logs. Just a SIGBUS. GPT seems to think it's some kind of faulty file or hardware, which doesn't make a lot of sense considering I've got a dozen other conatiners running on the same hardware no issues, all using the same pool for appdata, no issues. And I've moved the appdata folder, reinstalled container, etc... and still getting the same issue.

supervisor ] starting service 'nginx'...

[supervisor ] starting service 'app'...

[supervisor ] all services started.

[supervisor ] service 'nginx' exited (got signal SIGBUS).

GPT seems to think that I'm supposed to have a sqlite database in a data folder within the NginxProxyManager folder inside of appdata, which I don't. So it's saying that since I'm missing that it's not working. But I can't recall if it's supposed to have one or not, and if not... why?

GPT is right. I created a sqlite file with the name expected from what was in the production.json file in the root of the NginxProxyManager directory and it tried to start but there was no migration table (of course since i created an empty db). So, for some reason no matter what I do it's not making the necessary sqlite table?

You will likely get a better/faster response if you post in the appropriate support thread in the Applications Support > Docker Containers sub-forum.

1 hour ago, ConnerVT said:

You will likely get a better/faster response if you post in the appropriate support thread in the Applications Support > Docker Containers sub-forum.

Oh, dang, I hadn't realized that, thank you. I'll note that for future issues.

As a note, I solved it by switching to a different Nginx Proxy Manager. I have to redo the proxy hosts, etc. But at least the container works.

Glad you got this sorted. There are currently 3 Nginx Proxy Manager containers in CA, and who knows how many out in the wilds of the Internet. The ones in CA each have a different spin on how they are configured, so your question was definitely one to ask in the container's support thread.