Backup restore fails

[vimwitch]

Bug description
After restoring from backup the primary environment is unreachable. An error "Environment is unreachable" is shown.

Expected behavior
Environment is reachable.

Portainer Logs

2023/04/06 05:24AM INF github.com/portainer/portainer/api/cmd/portainer/main.go:530 > encryption key file not present | filename=portainer
2023/04/06 05:24AM INF github.com/portainer/portainer/api/cmd/portainer/main.go:549 > proceeding without encryption key |
2023/04/06 05:24AM INF github.com/portainer/portainer/api/database/boltdb/db.go:124 > loading PortainerDB | filename=portainer.db
2023/04/06 05:24AM INF github.com/portainer/portainer/api/cmd/portainer/main.go:515 > instance already has defined environments, skipping the environment defined via CLI |
2023/04/06 05:24:11 server: Reverse tunnelling enabled
2023/04/06 05:24:11 server: Fingerprint [redacted]
2023/04/06 05:24:11 server: Listening on 0.0.0.0:8000...
2023/04/06 05:24AM INF github.com/portainer/portainer/api/cmd/portainer/main.go:789 > starting Portainer | build_number=25294 go_version=1.19.3 image_tag=linux-amd64-2.16.2 nodejs_version=18.12.1 version=2.16.2 webpack_version=5.68.0 yarn_version=1.22.19
2023/04/06 05:24AM INF github.com/portainer/portainer/api/http/server.go:337 > starting HTTPS server | bind_address=:9443
2023/04/06 05:24AM INF github.com/portainer/portainer/api/http/server.go:322 > starting HTTP server | bind_address=:9000
{"time":1680758714,"message":"http: TLS handshake error from 10.0.0.6:47204: EOF"}
{"time":1680758838,"message":"http: TLS handshake error from 10.0.0.7:45178: EOF"}

Steps to reproduce the issue:

1. Make a backup
2. Restore the backup

Technical details:

• Portainer version: 2.16.2 and 2.17.1
• Docker version (managed by Portainer):
• Kubernetes version (managed by Portainer):
• Platform (windows/linux): linux
• Command used to start Portainer (docker run -p 9443:9443 portainer/portainer):
• Browser:
• Use Case (delete as appropriate): Using Portainer at Home, Using Portainer in a Commercial setup.
• Have you reviewed our technical documentation and knowledge base? Yes/No

Additional context

[tamarahenson]

@vimwitch

I am unable to reproduce this issue.

Can you send me a copy of your backup via message in our Community Slack and I can test further? https://join.slack.com/t/portainer/shared_invite/zt-190q9nm5v-uT0p0WFkn~K1yv2QlnHJNQ

Thanks!

[wumixa]

for me to not working when i restore my portainer backup created with the webinterface

[JamborJan]

I have create a backup of portainer in one instance and I wanted to migrate it. In that setup portainer is managing a remote endpoint, nothing local. Importing fails immediately and this can be seen in the logs:

# docker logs portainer 
2023/06/03 06:22PM INF main.go:568 > encryption key file not present | filename=portainer
2023/06/03 06:22PM INF main.go:602 > proceeding without encryption key |
2023/06/03 06:22PM INF github.com/portainer/portainer-ee/api/database/boltdb/db.go:124 > loading PortainerDB | filename=portainer.db
2023/06/03 06:22PM INF github.com/portainer/portainer-ee/api/internal/ssl/ssl.go:146 > no cert files found, generating self signed SSL certificates |
2023/06/03 06:22PM INF github.com/portainer/portainer-ee/api/cloud/cluster_setup.go:93 > starting cloud cluster setup service |
2023/06/03 18:22:49 server: Reverse tunnelling enabled
2023/06/03 18:22:49 server: Fingerprint 7a:a4:b7:fe:38:eb:e9:f5:91:92:80:39:e6:1a:30:fa
2023/06/03 18:22:49 server: Listening on 0.0.0.0:8000...
2023/06/03 06:22PM INF main.go:902 > starting Portainer | build_number=30955 go_version=1.19.4 image_tag=linux-amd64-2.18.3 nodejs_version=18.16.0 version=2.18.3 webpack_version=5.65.0 yarn_version=1.22.19
2023/06/03 06:22PM INF github.com/portainer/portainer-ee/api/http/server.go:417 > starting HTTPS server | bind_address=:9443
2023/06/03 06:22PM INF github.com/portainer/portainer-ee/api/http/server.go:402 > starting HTTP server | bind_address=:9000
2023/06/03 06:23PM INF main.go:905 > HTTP server exited | error="http: Server closed"
2023/06/03 06:23PM INF main.go:568 > encryption key file not present | filename=portainer
2023/06/03 06:23PM INF main.go:602 > proceeding without encryption key |
2023/06/03 06:23PM INF github.com/portainer/portainer-ee/api/database/boltdb/db.go:124 > loading PortainerDB | filename=portainer.db
2023/06/03 06:23PM FTL main.go:122 > failed opening store | error="invalid database"
2023/06/03 06:23PM INF main.go:568 > encryption key file not present | filename=portainer
2023/06/03 06:23PM INF main.go:602 > proceeding without encryption key |
2023/06/03 06:23PM INF github.com/portainer/portainer-ee/api/database/boltdb/db.go:124 > loading PortainerDB | filename=portainer.db
2023/06/03 06:23PM FTL main.go:122 > failed opening store | error="invalid database"
2023/06/03 06:23PM INF main.go:568 > encryption key file not present | filename=portainer
2023/06/03 06:23PM INF main.go:602 > proceeding without encryption key |
2023/06/03 06:23PM INF github.com/portainer/portainer-ee/api/database/boltdb/db.go:124 > loading PortainerDB | filename=portainer.db

Removing the portainer container and volume and recreating all from scratch always brings the same issue.

Update: in my first attempt I tried restoring a 2.17.1 backup into a 2.18.3 portainter instance. I updated the source now and re-created the backup. But nothing changed.

[jirisykora83]

i try several times and restoring backup just not work for me