POrtainer not available after restart

[drnicolas]

Ask a Question!

My portainer is not reachable via WebGUI after a restart.
I see multiple log-messages of this kind:

2026/01/12 23:06:11 server: Reverse tunnelling enabled
2026/01/12 23:06:11 server: Fingerprint EJlMxVX9CXYGGW6QMXm5OxlY4orzxx6GGCiU21lkdGs=
2026/01/12 23:06:11 server: Listening on http://0.0.0.0:8000
2026/01/12 11:06PM INF github.com/portainer/portainer/api/datastore/postinit/migrate_post_init.go:112 > Executing post init migration for environment 3 |
2026/01/12 11:06PM INF github.com/portainer/portainer/api/cmd/portainer/main.go:636 > starting Portainer | build_number=251 go_version=1.24.11 image_tag=2.33.6-linux-amd64 nodejs_version=18.20.8 version=2.33.6 webpack_version=5.88.2 yarn_version=1.22.22
2026/01/12 11:06PM INF github.com/portainer/portainer/api/http/server.go:367 > starting HTTPS server | bind_address=:9443
2026/01/12 11:06PM INF github.com/portainer/portainer/api/http/server.go:351 > starting HTTP server | bind_address=:9000
2026/01/12 11:08PM INF github.com/portainer/portainer/api/cmd/portainer/main.go:325 > encryption key file not present | filename=/run/secrets/portainer
2026/01/12 11:08PM INF github.com/portainer/portainer/api/cmd/portainer/main.go:365 > proceeding without encryption key |
2026/01/12 11:08PM INF github.com/portainer/portainer/api/database/boltdb/db.go:137 > loading PortainerDB | filename=portainer.db
2026/01/12 11:08PM INF github.com/portainer/portainer/api/chisel/service.go:200 > found Chisel private key file on disk | private-key=/data/chisel/private-key.pem
2026/01/12 23:08:44 server: Reverse tunnelling enabled
2026/01/12 23:08:44 server: Fingerprint EJlMxVX9CXYGGW6QMXm5OxlY4orzxx6GGCiU21lkdGs=
2026/01/12 23:08:44 server: Listening on http://0.0.0.0:8000
2026/01/12 11:08PM INF github.com/portainer/portainer/api/datastore/postinit/migrate_post_init.go:112 > Executing post init migration for environment 3 |
2026/01/12 11:08PM INF github.com/portainer/portainer/api/cmd/portainer/main.go:636 > starting Portainer | build_number=251 go_version=1.24.11 image_tag=2.33.6-linux-amd64 nodejs_version=18.20.8 version=2.33.6 webpack_version=5.88.2 yarn_version=1.22.22
2026/01/12 11:08PM INF github.com/portainer/portainer/api/http/server.go:367 > starting HTTPS server | bind_address=:9443
2026/01/12 11:08PM INF github.com/portainer/portainer/api/http/server.go:351 > starting HTTP server | bind_address=:9000

WHat can I do?

BTW: I have 2 instances pf paperless NGX running and they are also not reachable. docker ps says something tehy are starting, but I think it is a re-start

There was an apt update/upgrade with tons of updated paxkages

UPDATE:
neither portainer nor the paperless NGX seem to have a port attached. portainer is running, the paperless instances stay in staring

Update #2
"checking docker logs portainer", I do not see ANY signs of error messages. Startup seems just to be fine
Anyway, netstat does not show anyone listening on port 9000 or 9443.
Also a "curl https:localhost:9443" fails

[drnicolas]

I partially solved the problem.
Installed a new instance and now I can log in again. But I lost my stacks

[Nick-Portainer]

@drnicolas When you say you installed a new instance, are you referring to Portainer Server? If you reinstalled it and referenced the previous Portainer server volume your Stacks will still be referenced in Portainer.

Please note, your deployments will continue to run outside of Portainer, so if Portainer Server and your other Docker deployments are down this points to a lower level issue which will require more details around how you are deploying your services and what type of instance you are using.

[drnicolas]

I am not sure about the wording.
I re-installed Portainer as I couldn't log-in anymore. The typical workarounds did not work.

After re-installing and re-applying a new password, I have my containers back; bot up and running (2 independet instances of paperless).
Nevertheless, my stacks are gone! It sayys they were generated outside of Portainer and therefore access is limited.
Actually, I d not see anything of the settings for the paperless containers.

What can I do?

[Nick-Portainer]

It sounds like you deleted the Portainer volume which contains the datatbase that contains the information about the stacks you deployed within Portainer. These will continue to run outside of Portainer, but unless you took backups and can restore the database then you will need to redeploy these stacks within Portainer again

[AlexanderQueen]

@Nick-Portainer The problem is that this kind of "puzzle" musn't happen never ever... Imagine having EE portainer with 50+ containers, carefull updating and re-deploying, keeping the configuration data and receiving something like @drnicolas has listed.. I must also delete entire portainer volume with its data and to re-create it from scratches cause now i can't even deploy anything from stack...

My example + which has posted @drnicolas above:

"failed to interpolate config for stack . error: compose config operation failed: failed to create compose project: failed to resolve services environment: env file /opt/nextdns-monitor/stack.env not found: stat /opt/nextdns-monitor/stack.env: no such file or directory"

To anticipate, i have this file in the folder. From docker-compose cli it launches like a NASA rocket with no error... In almost 4 years which i'm using Portainer i never expected something like that.....