Error 502 - Error 500 - Can't upgrade from 0.15.10 to 1.0.0+
I am new at using things like nginx, jellyfin, docker but i love it. I used ai to resolve the majority of my problems but this, i can't seem to be able to do it. I saw the "upgrade to 1.0.0" and wondered "am i using an old version ?", i tried getting the new one but i kept getting 502 (blank page) or 500 (homarr interface but internal server error page) and since i was going in a loop with the ai, i thought maybe we can't replace humans with it. I need help.
Setup :
OS : Windows 11
Docker Engine: Docker Desktop
File Structure: All my files (compose.yml, data folders) are located in C:\docker.
Reverse Proxy: I'm using jc21/nginx-proxy-manager, which works perfectly with my other services (Jellyfin, Joplin, etc.).
Network: All relevant services are on a shared Docker network named proxy-network.
(i don't know if my setup is the best way to do what i want, i'm just a guy discovering and trying to add more services)
My full docker-compose.yml :
https://gist.github.com/Halilman04/13ed12566262f218711d93d956c9e1a6
What I've Already Tried :
Completely removed the old Homarr version (container, volumes, image).
Manually created the C:\docker\homarr-data folder before running docker compose up.
Ran docker compose down and docker compose up -d after every change to the compose.yml file.
Confirmed that my other services using PUID=1000 and PGID=1000 are working without any permission issues.
Checked my Nginx Proxy Manager configuration, which correctly points to http://homarr:7575.
Thanks in advance for your patience and help
Solution:Jump to solution
i got it working, i just deleted everything about homarr, used this code in my compose.yml, and didn't use ports, since i just realised i don't need em, and i also deleted it on nginx and redone it from scratch. Code "homarr:
container_name: homarr
image: ghcr.io/homarr-labs/homarr:latest
restart: unless-stopped
networks:...
16 Replies
Thank you for submitting a support request.
Depending on the volume of requests, our team should get in contact with you shortly.
⚠️ Please include the following details in your post or we may reject your request without further comment: - Log (See https://homarr.dev/docs/community/faq#how-do-i-open-the-console--log) - Operating system (Unraid, TrueNAS, Ubuntu, ...) - Exact Homarr version (eg. 0.15.0, not latest) - Configuration (eg. docker-compose, screenshot or similar. Use ``your-text`` to format) - Other relevant information (eg. your devices, your browser, ...)
Frequently Asked Questions | Homarr documentation
Can I install Homarr on a Raspberry Pi?
log
it could be that my newbie brain is completely missing something
Please post the logs, not your console
My bad i misundestood here''s the logs : https://gist.github.com/Halilman04/f985cc25cdc453d404a779125c37acce
Did i send the right log ?
message: 'SECRET_ENCRYPTION_KEY is required, please generate a 64 character secret in hex format or use the following: "4c9c507fc4d94e3b0ff6bbfa504c12a13c4c50e80850a16f0b325aab57473e9a"'Please read the docs: https://homarr.dev/docs/getting-started/installation/docker
Docker | Homarr documentation
Docker is our recommended installation method for beginners and professionals.
Also be advised that the compose you linked is not correct. See https://homarr.dev/blog/2025/01/19/migration-guide-1.0
Migrate from 0.15.10+ to 1.0.0 | Homarr documentation
In this guide, we will show you how to migrate from Homarr 0.15.10+ to 1.0.0.
You will loose data if you ignore this warning and continue anyway.
I'm getting a 502 Bad Gateway error when trying to access Homarr now. Here's what I've done:
- I'm not worried about losing data—I can recreate the setup if needed
- I generated a new SECRET_DECRYPTION_KEY and updated my compose.yml
- I changed the port mapping to 7576:7575 both in Docker Compose and Nginx
Problem:
- With the old compose.yml, I at least got an error in Homarr itself. Now, I only get 502 Bad Gateway.
- I already tried using the encryption key as mentioned in the docs, but it didn’t help.
Any ideas why this is happening?
I can provide logs, configs, or anything else needed. Here are the logs:
https://gist.github.com/Halilman04/4e081242b141ec255770929dadb0244f
Let me know what else could help
Bad Gateway is not a Homarr related issue. This is out of our support scope.
Your proxy is likely misconfigured or cannot reach Homarr.
hmm okay ill get back in a bit thanks already tho
Solution
i got it working, i just deleted everything about homarr, used this code in my compose.yml, and didn't use ports, since i just realised i don't need em, and i also deleted it on nginx and redone it from scratch. Code "homarr:
container_name: homarr
image: ghcr.io/homarr-labs/homarr:latest
restart: unless-stopped
networks:
- proxy-network
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- ./homarr/appdata:/appdata
environment:
- SECRET_ENCRYPTION_KEY= * the key *
- PUID=1000
- PGID=1000"
do i do that thing where i mark as a solution ? i guess i just misconfigured it so idk
Glad you got it to work. Yes, you can mark this as resolved if your Homarr works now
Right click on message > Apps > Mark solution
Thanks man !