CORS issue – self hosted Sentry

  • Resolved irinelmita

    (@irinelmita)


    2 years, 7 months ago

    Hello,
    We are getting the following issue:

    Access to fetch at 'https://sentryf.ongage.net/api/72/envelope/?sentry_key=a14cd4c11ce14856b899e9d3d5bc1e9c&sentry_version=7' from origin 'https://dev2-www.ongage.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

    Our sentry is self hosted. We are at the latest version of the plugin (4.16.0)
    Is there anything we can do to fix this issue?

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author stayallive

    (@stayallive)

    There is a setting in the project settings in your Sentry that configures the allowed domains, is it possible you did not add the domain to there?

    I don’t think there is anything the plugin can do for you since CORS is a server-side thing (as in the Sentry server controls that, not your site),

    Thread Starter irinelmita

    (@irinelmita)

    Thanks for the reply.

    That the allowed domain value is *.

    What should be done in this situation?

    Plugin Author stayallive

    (@stayallive)

    Since it’s a self-hosted server, maybe there is some configuration set on the reverse proxy or something, the project settings sound like they are setup properly.

    The only other problem I can think of next to the proxy configuration is that you are running a very old instance of Sentry, can you confirm the version of the self-hosted Sentry instance? Just to make sure the endpoint the SDK is trying to reach even exists (there were some changes in the API endpoints) which could explain the problems you are seeing.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘CORS issue – self hosted Sentry’ is closed to new replies.