Service migration issue

[swenker]

Self-Hosted Version

23.7.2

CPU Architecture

x86_64

Docker Version

24.0.9

Docker Compose Version

2.27.0

Steps to Reproduce

1.install sentry on Server1 and make sure it works well;
2.stop docker service on Server1
3. copy the full docker data folder(/var/lib/docker) from Server1 to Server2.
4. start docker service on Server2
5. on Server2 docker-compose up -d

Expected Result

the service on Server2 works well .

Actual Result

I can login and view the projects and issues under projects. but the request http://server2:9000/organizations/myorg-sentry/issues/ doesn't work.
I check browser console, there's request like this http://server1:9000/api/1/envelope/?sentry_key=e86296ce46df9af06d9e99d56ff941c7&sentry_version=7&sentry_client=sentry.javascript.react%2F7.60.1'

and this leads to" Content Security Policy" issue in browser.

Now it seems all the others features works well except this one.

Do you guys know how I can fix this issue?

Event ID

No response

[azaslavsky]

Did you run ./install.sh on server 2? It configures your server in ways that I don't think are entirely captured by docker exports (ex: the config file lives in the self-hosted repo, not inside docker).

[swenker]

Did you run ./install.sh on server 2? It configures your server in ways that I don't think are entirely captured by docker exports (ex: the config file lives in the self-hosted repo, not inside docker).

mm, I didn't run install.sh because Server2 couldn't connect to internet. That's why I copied all the docker data folder from Server1 to Server2.
As to the result , it seems the Server1 address is saved ? I searched both docker data folder and sentry folder(containing install.sh ) nothing found. Maybe it's saved in some database table of sentry?

[hubertdeng123]

We would highly recommend you to run install.sh on Server2 to make sure the config changes are picked up. I would suspect the address is saved somewhere in postgres but unsure exactly where.