Closed beyondverage0908 closed 7 months ago
It seems like the CLI is configured to upload to the incorrect URL. Your issue description states that your self-hosted instance is located at https://fenewmonitor.money.com/, but according to the CLI logs, the CLI is making requests to https://fenewmonitor.eastmoney.com.
You should reconfigure the CLI URL to https://fenewmonitor.money.com/. You can configure the URL in an environment variable or the .sentryclirc
configuration file.
Awkward, there was a typo. The correct access address is: https://fenewmonitor.eastmoney.com/. I have also configured the .sentryclirc file as follows. However, the same error still occurs.
@beyondverage0908 You accidentally included your auth token in the screenshot of your .sentryclirc
above. I already edited your comment to remove the screenshot, but I would recommend that you revoke the auth token immediately and regenerate it. Since this issue is public, anyone could have seen your auth token!
I will continue investigating, thank you for the information!
@szokeasaurusrex Thank you very much. Through continuous attempts, it was found that after modifying the system.url-prefix and system.internal-url-prefix in the deployment configuration file config.yml
, the previous error no longer appeared, and the artifacts were successfully uploaded.
before:
system.url-prefix: "http://fenewmonitor.eastmoney.com"
system.internal-url-prefix: 'http://web:9000'
after:
# use https
system.url-prefix: "https://fenewmonitor.eastmoney.com"
system.internal-url-prefix: "https://fenewmonitor.eastmoney.com"
However, I still have a question. After a successful upload, the release details panel displays the number of artifacts. Yet, when navigating to the Source Maps panel, I cannot view the artifact files. As shown in the following image:
release details panel :
Source Maps panel:
@beyondverage0908, according to the issue description, you were uploading to release_01
, not to release_v_04
. Can you please check and confirm whether you were uploading to the correct release?
Environment
➜ ✗ sentry-cli --version sentry-cli 2.28.6
OS: centos7, self-hosted sentry
Sentry version: Sentry 23.5.2 ad182e5
Steps to Reproduce
Step 1: self-hosted Deployment For private deployment of Sentry, I only made modifications to use an external service for Postgres. The configuration is as follows:
Then, execute ./install.sh for installation. After successful installation, start with docker compose up -d. Access via: https://fenewmonitor.eastmoney.com/.
Step 2: Create a Test Project and Prepare to Upload Source Maps Check the organization and project names and generate the authToken.
Step 3: Upload Source Maps Using sentry-cli
sentry-cli sourcemaps upload dist -p bibivue -o emnj --auth-token 005db25e4131457dbe4d45f0c***********61c984d2b804802469d714c8e -r release_01 --log-level debug
Expected Result
The
sourcemaps
were successfully uploaded, and you can view them in the release section on the web platform.Actual Result
tip:error: Project not found. Please check that you entered the project and organization slugs correctly.
Logs