can't get portainer to load. here's the log �2026-06-05T20:54:42.408539259Z [90m2026/06/05 08:54PM[0m [32mINF[0m [1mgithub.com/portainer/portainer/api/cmd/portainer/main.go:325[0m[36m [0m encryption key file not present | [36mfilename=[0m/run/secrets/portainer �2026-06-05T20:54:42.408570886Z [90m2026/06/05 08:54PM[0m [32mINF[0m [1mgithub.com/portainer/portainer/api/cmd/portainer/main.go:363[0m[36m [0m proceeding without encryption key | �2026-06-05T20:54:42.408622441Z [90m2026/06/05 08:54PM[0m [32mINF[0m [1mgithub.com/portainer/portainer/api/database/boltdb/db.go:137[0m[36m [0m loading PortainerDB | [36mfilename=[0mportainer.db �2026-06-05T20:54:42.596517895Z [90m2026/06/05 08:54PM[0m [32mINF[0m [1mgithub.com/portainer/portainer/api/cmd/portainer/main.go:509[0m[36m [0m instance already has an administrator user defined, skipping admin password related flags. | �2026-06-05T20:54:42.596538577Z [90m2026/06/05 08:54PM[0m [32mINF[0m [1mgithub.com/portainer/portainer/api/chisel/service.go:199[0m[36m [0m found Chisel private key file on disk | [36mprivate-key=[0m/data/chisel/private-key.pem V2026-06-05T20:54:42.596628205Z 2026/06/05 20:54:42 server: Reverse tunnelling enabled t2026-06-05T20:54:42.596644045Z 2026/06/05 20:54:42 server: Fingerprint UnbaTuQ4UZr+WI01FORoQ0bhKuwnUvAXkd8pB3EaJjM= \2026-06-05T20:54:42.596792015Z 2026/06/05 20:54:42 server: �2026-06-05T20:54:42.601204157Z [90m2026/06/05 08:54PM[0m [32mINF[0m [1mgithub.com/portainer/portainer/api/cmd/portainer/main.go:628[0m[36m [0m starting Portainer | [36mbuildnumber=[0m25 [36mgoversion=[0mgo1.26.2 [36mimagetag=[0m2.42.0-linux-amd64 [36mnodejsversion=[0mv22.22.2 [36mpnpmversion=[0m10.27.0 [36mversion=[0m2.42.0 [36mwebpackversion=[0m5.105.0 �2026-06-05T20:54:42.605596467Z [90m2026/06/05 08:54PM[0m [32mINF[0m [1mgithub.com/portainer/portainer/api/http/server.go:362[0m[36m [0m starting HTTPS server | [36mbindaddress=[0m:9443 �2026-06-05T20:54:42.650132380Z [90m2026/06/05 08:54PM[0m [32mINF[0m [1mgithub.com/portainer/portainer/api/http/server.go:346[0m[36m [0m starting HTTP server | [36mbindaddress=[0m:9000 Close
8 replies
jackhammer57 wrote:
had to remove a line in the middle in regards to listening on port 8000 Demox wouldn't let me proceed with it in the log.
tomspark wrote:
No worries about the line you had to trim — that was just Portainer's internal tunnel port, nothing to do with your problem. And the good news: that log is Portainer starting up perfectly. Both its web servers came up and your admin account is intact, so nothing crashed or got lost. The issue is just reaching it in the browser. In SparkBox, Portainer runs as plain http on port 9000, and browsers love to silently jump to https, which won't connect on that port. Open it with the address typed exactly like this — note http, not https: http://YOUR-BOX-IP:9000 If it still won't load that way, tell me and we'll check whether your box's IP changed.
jackhammer57 wrote:
still won't load. same can't connect to server. all my other containers open via ip:port without any problems
tomspark wrote:
That's a really useful clue — if every other app opens on its ip:port but only Portainer won't, then Portainer just isn't being published on the port we're expecting. One quick command shows exactly which port it's actually on: sudo docker ps --filter name=sb-portainer Paste the PORTS column it prints. If it shows 0.0.0.0:9000-9000 we'll look at the box's firewall next; if the number on the left is different, that's the port to open it on instead. Either way that tells me the fix.
jackhammer57 wrote:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 1eb8544b98fb portainer/portainer-ce:2.42.0 "/portainer --admin-…" 19 hours ago Up 2 minutes 8000/tcp, 9443/tcp, 0.0.0.0:9001-9000/tcp, :::9001-9000/tcp sb-portainer Joe@DXP4800PRO-868A:~$
tomspark wrote:
There it is — that 0.0.0.0:9001-9000 line is the whole answer. On your box Portainer's web page is published on port 9001, not 9000 (something else was already using 9000, so it got bumped). So open it at: http://YOUR-BOX-IP:9001 That'll load it straight up. Sorry for the back-and-forth — the :9001 was the missing piece. Once you're in, if that "needs attention" tag from your other thread is still showing, tell me which app it's on and we'll clear that one too.
jackhammer57 wrote:
so if I'm reading that right its showing port 9001 as the active port
tomspark wrote:
Yep, you read it exactly right — 9001 is the live port for Portainer on your box. Open it at http://YOUR-BOX-IP:9001 and it'll load straight up. Nothing's broken; it just got moved off the usual 9000 because something else had already grabbed that port, so the system bumped it to 9001. That's the whole story. Glad we got to the bottom of it.