I am running on-premise sentry (version 9.1.2) in a kubernetes cluster. Lately, I am seeing a 500 error every time I attempt to create a new release and upload source maps to any project in sentry. When I check the release, I do not see any artifacts uploaded.
It shows you the error id that you can look up on the “internal” project on your Sentry instance to get more details: 414e2adb4f5c4666991731bb53c15bd5
These error IDs never show up on the sentry web logs. All I can see is the API POST call failure with the error code 500. I can see the release created in the project, but not even a single artifact gets uploaded.
This is not specific to one internal project. This is now happening for all projects. Is there a way to enable verbose logging in sentry web to capture the root cause of these API request failures?
We encountered this very issue today when setting up Sentry on premise v21.03. Here is the log we retrieved from the internal project on our sentry application.
@maxence if you are sure your settings are correct (regarding signing keys and credentials) I’d check if the time is correctly set on your Sentry instance as some signing methods rely on correct & synced clocks.
I did not have that in the configuration file. I added it now and I was able to schedule the pod. Thanks! I will check the logs and see what is going on under the hood.