Domain started showing 404 page not found

[Ashutosh_Jha]

i am using a self hosted n8n but after updtae to latest version. domain started showing 404 page not found.
docker compose up shows this
root-n8n-1 | Error: Command “start” not found
root-n8n-1 exited with code 0
root-n8n-1 | Error: Command “start” not found
root-n8n-1 exited with code 1
root-traefik-1 | 2025-08-29T16:03:29Z ERR error=“service "n8n-root" error: unable to find the IP address for the container "/root-n8n-1": the server is ignored” container=n8n-root-0e8448a2e3d53645e0d70920b29294bffa03154a5e07929b5fadff9fa25591bb providerName=docker
root-n8n-1 | Error: Command “start” not found
root-n8n-1 exited with code 1
root-traefik-1 | 2025-08-29T16:03:31Z ERR error=“service "n8n-root" error: unable to find the IP address for the container "/root-n8n-1": the server is ignored” container=n8n-root-0e8448a2e3d53645e0d70920b29294bffa03154a5e07929b5fadff9fa25591bb providerName=docker
root-n8n-1 | Error: Command “start” not found
root-n8n-1 exited with code 1
root-traefik-1 | 2025-08-29T16:03:33Z ERR error=“service "n8n-root" error: unable to find the IP address for the container "/root-n8n-1": the server is ignored” container=n8n-root-0e8448a2e3d53645e0d70920b29294bffa03154a5e07929b5fadff9fa25591bb providerName=docker
root-n8n-1 | Error: Command “start” not found
root-n8n-1 exited with code 1
root-traefik-1 | 2025-08-29T16:03:36Z ERR error=“service "n8n-root" error: unable to find the IP address for the container "/root-n8n-1": the server is ignored” container=n8n-root-0e8448a2e3d53645e0d70920b29294bffa03154a5e07929b5fadff9fa25591bb providerName=docker
root-n8n-1 | Error: Command “start” not found
root-n8n-1 exited with code 1
root-traefik-1 | 2025-08-29T16:03:40Z ERR error=“service "n8n-root" error: unable to find the IP address for the container "/root-n8n-1": the server is ignored” container=n8n-root-0e8448a2e3d53645e0d70920b29294bffa03154a5e07929b5fadff9fa25591bb providerName=docker
root-n8n-1 | Error: Command “start” not found
root-n8n-1 exited with code 1
root-traefik-1 | 2025-08-29T16:03:45Z ERR error=“service "n8n-root" error: unable to find the IP address for the container "/root-n8n-1": the server is ignored” container=n8n-root-0e8448a2e3d53645e0d70920b29294bffa03154a5e07929b5fadff9fa25591bb providerName=docker
root-n8n-1 | Error: Command “start” not found
root-n8n-1 exited with code 1
root-traefik-1 | 2025-08-29T16:03:53Z ERR error=“service "n8n-root" error: unable to find the IP address for the container "/root-n8n-1": the server is ignored” container=n8n-root-0e8448a2e3d53645e0d70920b29294bffa03154a5e07929b5fadff9fa25591bb providerName=docker.
If your question hasn’t been asked before, please follow the template below. Skip the questions that are not relevant to you. →

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[Gonzalo_Romero_Herna]

Hey @Ashutosh_Jha welcome to the community!!

Would you mind sharing your current docker-compose file please?

Happy to read your comments!

[Ashutosh_Jha]

my docker-compose.yml

[Ashutosh_Jha]

when i saw the update, i just pulled and docker compose up -d , after that it started showing 404 page not found, i dont wanna loose my database, please help

[Gonzalo_Romero_Herna]

Are you able to reboot with your previous functional version? Don’t worry about your database just be careful not delete the n8n_data Docker volume

[Ashutosh_Jha]

No, its not REbooting up. @Gonzalo_Romero_Herna

[Gonzalo_Romero_Herna]

Lets verify the logs. Once your containers are running, Could you please share the logs?

Just run the following command:

docker-compose logs -f n8n

BTW, What version did you use before the update?

[Ashutosh_Jha]

@Gonzalo_Romero_Herna i think i was 4-5 updates before.

docker-compose logs -f n8n command returned this –

root-n8n-1 | Error: Command “start” not found
root-n8n-1 | Error: Command “start” not found
root-n8n-1 | Error: Command “start” not found
root-n8n-1 | Error: Command “start” not found
root-n8n-1 | Error: Command “start” not found
root-n8n-1 | Error: Command “start” not found
root-n8n-1 | Error: Command “start” not found
root-n8n-1 | Error: Command “start” not found
root-n8n-1 | Error: Command “start” not found
root-n8n-1 | Error: Command “start” not found
root-n8n-1 | Error: Command “start” not found
root-n8n-1 | Error: Command “start” not found
root-n8n-1 | Error: Command “start” not found
root-n8n-1 | Error: Command “start” not found
root-n8n-1 | Error: Command “start” not found
root-n8n-1 | Error: Command “start” not found
root-n8n-1 | Error: Command “start” not found
root-n8n-1 | Error: Command “start” not found
root-n8n-1 | Error: Command “start” not found
root-n8n-1 | Error: Command “start” not found
root-n8n-1 | Error: Command “start” not found
root-n8n-1 | Error: Command “start” not found
root-n8n-1 | Error: Command “start” not found
root-n8n-1 | Error: Command “start” not found
root-n8n-1 | Error: Command “start” not found
root-n8n-1 | Error: Command “start” not found
root-n8n-1 | Error: Command “start” not found
root-n8n-1 | Error: Command “start” not found
root-n8n-1 | Error: Command “start” not found
root-n8n-1 | Error: Command “start” not found
root-n8n-1 | Error: Command “start” not found
root-n8n-1 | Error: Command “start” not found
root-n8n-1 | Error: Command “start” not found
root-n8n-1 | Error: Command “start” not found

[Gonzalo_Romero_Herna]

I tried to reproduce the error by deploying a docker-compose self-hosted instance from a previous version and then by upgrading to the current one, however it worked fine for me. By any chance is there another executed step before the upgrade that could change things like file locations or user permissions? If you are using a cloud provider you could try by making a backup of your n8n_data docker volume(be careful not to delete it), starting a new VM just for test purposes, creating a new docker volume from your back up and then running a new instance of n8n to see the result. You can also check this similar reported issue