Unable to Add Docker Apps After Loss of Power

[anonhostpi]

Environment

Docker

Version

0.14.6

Describe the problem

After host lost power, I am unable to add any docker apps to my boards:

Logs

Exporting hostname... Migrating database... yarn run v1.22.19 $ ts-node ./migrate.ts Done in 3.36s. Starting production server... Listening on port 7575 url: http://8235bb6de0b9:7575 ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... ℹ Database is writeable ℹ Database is writeable ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable... ℹ Database is writeable user anonhostpi is trying to log in. checking password... user anonhostpi successfully authorized ℹ Local icons repository directory exists and contains 0 icons ℹ Local icons repository directory exists and contains 0 icons ℹ Local icons repository directory exists and contains 0 icons

ERROR Unexpected response: connect ECONNREFUSED 127.0.0.1:53

ℹ Saving updated configuration of 'default' config.

ERROR Unexpected response: connect ECONNREFUSED 127.0.0.1:53

user anonhostpi is trying to log in. checking password... user anonhostpi successfully authorized ℹ Local icons repository directory exists and contains 0 icons

ERROR Unexpected response: connect ECONNREFUSED 127.0.0.1:53

ERROR App [object Object] not found

Context

No response

Please tick the boxes

• [X] I confirm that I attached the proper logs
• [X] I've read the docs
• [X] I've checked for duplicate issues
• [X] I've tried to debug myself

[manuel-rw]

Hi, does the docker user have the permissions? What is your compose?

Is the file corrupted or did you have to restore data after the power loss?

[anonhostpi]

I no longer have the original compose. I ended up rebuilding the system from scratch. Still kept getting problems periodically.

I would close as "not repro"

Is there any way to disable caching? I've noticed that homarr uses quite a bit of page caching and that may have been part of the problem.

TBH it doesn't make a whole lot of sense to even support caching in a homelab environment. I'd think most of the target end users would rather see a web page become unavailable when the server goes offline than see a cached page.

• Cached webpages are mostly indistinguishable from working ones and can be misleading when troubleshooting.

[manuel-rw]

Caching is only partially in our control. Your Browser will do caching by default and there's nothing we can do against that. We do "cache" our API communications but those should expire after a few minutes. If you're having troubles with it, I'd suggest you to clear browser data (cookies and cache) for the Homarr site in your browser.

Just to confirm: It mostly works after starting from scratch, correct?

Flakey behaviour could also be caused by bad storage or a corrupt operating system after your hard reset. Do you have parit / RAID and did you confirm whether the data is still "valid" and mustn't be corrected? A way to confirm if it's Homarr or not would be to use a different browser on a different device.

[ajnart]

We don't cache the page manually, the libraries we use probably take advantage of similarities in the structure of the pages to remember shared elements and caches them for easier access, any other data loads on page load

[github-actions[bot]]

Hello 👋, this issue has been open for 60 days without activity. We mark issues to help prioritise and close dead issues. Can you confirm that this issue is still relevant on the latest version? I'll remove the stale label as soon as there is further activity on this issue. Thank you 🙏

[manuel-rw]

Closing this because it cannot be reproduced.