-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Service migration issue #3032
Comments
Did you run |
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. |
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. |
I tried execute install.sh on Server2 , it shows internet connection is needed. So it failed . I also tried to clean the issues by the following steps :
do you have a more detailed guide on how to clean the data in sentry except the admin user? |
An instance can't really be created without running install.sh. More generally, we didn't really design the install and setup process to work offline, because a self-hosted server requires an internet connection anyway. |
finally I found the config item in /manage/status/environment/ ,
It can be changed within "Settings" -> "Root URL" I also found the item is stored in table sentry_option with key name system.url-prefix. Let me make a simple summary :
Thanks for your support. |
Thanks for the writeup, and I'm glad you were able to get your instance working. Is there anything else we can help you with? |
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
The text was updated successfully, but these errors were encountered: