Error Loading Configuration #27

New issue

Closed

opened 2025-09-24 22:54:43 -05:00 by sottey · 1 comment

sottey commented

2025-09-24 22:54:43 -05:00

(Migrated from github.com)

Hey there! Love the idea! It looks great! I have an app that allows people to automagically port their homelab configs to different dashboards and am excited to add this to it!

I have set up 100's of docker compose projects, so I am not a newbie, but I have been known to be an idiot once in a while so this might be on me....

I followed the exact steps (create the dir, wget the compose file, sudo docker compose up -d) and it started fine. But when I try to use the config pages (.../config) I get a pupup in the bottom left that says Error Loading Configuration.

I have verified permissions, checked that none of the ports are already allocated, etc. Still nothing. Logs show that the db is up and communicating. API is responding, webapp loads fine. But I cannot make any changes.

Any ideas? Thanks!

Hey there! Love the idea! It looks great! I have an app that allows people to automagically port their homelab configs to different dashboards and am excited to add this to it! I have set up 100's of docker compose projects, so I am not a newbie, but I have been known to be an idiot once in a while so this might be on me.... I followed the exact steps (create the dir, wget the compose file, sudo docker compose up -d) and it started fine. But when I try to use the config pages (.../config) I get a pupup in the bottom left that says Error Loading Configuration. I have verified permissions, checked that none of the ports are already allocated, etc. Still nothing. Logs show that the db is up and communicating. API is responding, webapp loads fine. But I cannot make any changes. Any ideas? Thanks! <img width="714" height="228" alt="Image" src="https://github.com/user-attachments/assets/4ef552e2-3dcc-44e8-8cfc-abbe2097272d" />

SluberskiHomeLab commented

2025-09-30 07:23:30 -05:00

(Migrated from github.com)

Thanks for opening the issue. I have seen this recently with my testing, specifically accessing the config on a different machine that is not the one running the container.

I just released version 2.1 which should fix that, plus add some easier access to the config page.

If you're using the :latest tag docker images, you can update by:
docker compose down
docker compose pull
docker compose up -d

Let me know if that fixes your issue,

Thanks for opening the issue. I have seen this recently with my testing, specifically accessing the config on a different machine that is not the one running the container. I just released version 2.1 which should fix that, plus add some easier access to the config page. If you're using the :latest tag docker images, you can update by: `docker compose down` `docker compose pull` `docker compose up -d` Let me know if that fixes your issue,