Can't proceed through onboarding since deleting configuration to reset password
Hi,
I had Homarr working fine until I had to delete the configuration to reset the password. Now clicking the
Start update process
or the dark mode button does nothing. I killed the container, removed it, deleted the Homarr config directory and started up the container again.
I get the following console errors in Edge.23 Replies
You shouldn't delete the configuration to reset password. You need to delete the database
Oh ok.
The db.sqlite file in the "/data" mount
Yes. Ok. I deleted the full root
/.config/Homarr
directory which would have deleted everything, including the data
directory. So, it should be the same as starting for the first time.Don't delete everything, it's gonna cause problems...
Ok. I know that now. Is there a way I can resolve this?
Well, since you're deleting everything to start from scratch, start your container from scratch too and repull the image
How do I do that with compose?
Never mind. I think I've found the right command.
Ok.
docker kill homarr
docker rm homarr
docker compose pull homarr
docker compose -up -d
And still no luck.@Manicraft1001 I'm still not really good with docker, can you help?
Delete the image
Then, pull it again and start from scratch
docker kill
, docker rm
, docker pull
and docker compose -up d
again?What is the compose file?
And delete the image with docker image rm <image-name>
docker image rm homarr
Error response from daemon: No such image: homarr:latest
Homarr is not the image name. It's the one starting with ghcr
docker image rm ghcr.io/ajnart/homarr:latest
Error response from daemon: conflict: unable to remove repository reference "ghcr.io/ajnart/homarr:latest" (must force) - container 3d685f49016d is using its referenced image 829e4e04e3c3
docker kill homarr
Error response from daemon: Cannot kill container: homarr: Container 3d685f49016d0c6a8f984d56106a9b15c11cc8d3ba976a01b4a96af502a9997d is not running
docker rm homarr , the issue is not that the container is running, the issue is that it exists
I get the same result as
docker kill homarr
with docker rm homarr ?
That did it. Still learning docker. lol
That still didn't work. I'm still unable to get a response from the buttons on the onboarding screen. I'll come back to it in a couple of hours... gonna hit up the boxing day sales.
Deleting the image and re-pulling it doesn't help. I have even deleted browser data, quit and re-launched it... still can't setup Homarr
Can you post your server log as well as your full browser console?
Also, do you run Homarr using a proxy or tunnel?
Nginx proxy
Do you route using a sub path?
access.log: https://pastebin.com/hL6eFRjQ
conf: https://pastebin.com/QQ1en5up
sites-available: https://pastebin.com/iEU1UGzq
default.conf: https://pastebin.com/iqbrqd40
default_proxy.conf: https://pastebin.com/RqYhXiT6
proxy.conf: https://pastebin.com/jehkyf7n
error.log: https://pastebin.com/HwWN01UQ
Could the SSL handshake error in the error log cause this?
Subdomain