RayGun Exception Message: The remote server returned an error: (403) Forbidden.

Hi , we've updated our solution to Latest version (Version 3.3.1 for .Net 4.5) and raygun logging stopped. when we set throwOnError in web.config it throws "The remote server returned an error: (403) Forbidden." . should we revert to the older version ?

I have the same problem! using v3.0.1

Same problem here, started just recently. We are still in trial mode, using (among others) Mindscape.Raygun4Net v3.3.0.

Same here, using raygun4js 1.10.0. Getting 403s most of the time.

Hi, we're currently encountering this error after updating to raygun for javascript v2. It appears to be a problem with the "heartbeat". url that returns forbidden: https://api.raygun.io/events?apikey=[insert a correct key]

We're pretty sure we're using a correct key as: 1. We generated a new one and placed it for "apiKey" 2. The connections with Raygun.send() work and actually send stuff to Raygun.

Hi Gunter,

Looks like there's a couple of issues with your Raygun configuration, primarily the reason why you're seeing 403 for the Pulse heartbeats is that you have enabled Pulse in your Raygun4JS config, but haven't unlocked it in the app and haven't purchased a Pulse plan or are currently running a trial.

To disable Pulse in Raygun4JS, change the disablePulse flag to true.

The second issue is the page is currently mixing the V1 and V2 APIs. The page is using the snippet correctly to load the script asynchronously, but then is checking for the presence of the V1 Raygun global variable and manually calling the init() function then attach.

These functions should be replaced with the rg4js() calls (which are present, but are commented out). This is the V2 API which is designed to be used with the snippet. The rg4js calls should be place directly below the snippet's script block (but in a script block of their own), and shouldn't be wrapped in the closure with the setInterval function and the typeof Raygun !== "undefined" check - instead, they should be in global script scope and executed immediately.

After these config changes are made to use the new V2 API, you can then call rg4js('disablePulse', true) to prevent the heartbeat 403ing.

I originally set the correct implementation with rg4js calls, no closure etc. You noticed that. The entire thing was still there commented out. You really didn't have to mention all that, but thanks anyway I guess. :|

I however now know that disablePulse is the cause. Which I really should've guessed from the heartbeats (pulses). facepalm As a suggestion, wouldn't it have been better if the error returned wasn't merely "forbidden", but more like "pulse not active" or something? Mentioning what certain error messages mean in the documentation would also help.

Thank you for the quick reply, Callum. Those 403 errors will be no more. :D