Bam.nr-data.net Post returns 403 error

Hi All - Our site is returning a 403 (Forbidden) error when posting to bam.nr-data.net.

VM69:1 POST https://bam.nr-data.net/events/1/6f8ec1fe?a=1022612&v=1210.e2af80&to=YgdYRcFEcHUUWFtNeQlaSXZLF0dUDmRbCgADaCVdVxZFxR4Wg5UUBc4KFsCV28UkIhV1sRFgYCldLTwlDC11C&rst=40948&ck=1&ref=https://www.mycompany.com/requestinfo 403 (Forbidden)

This randomly started happening about a week ago. Any help is greatly appreciated.

Thanks,
John

1 Like

Hi @jshields!

If you’re receiving a 403 error, it’s possible you could have a malfunctioning security webfilter that’s blocking the calls to New Relic from your internal network.

Can you confirm and let me know?

Hey there

I have been receiving that error as well. Multiple environments.

I can’t really see how its a webfilter as something is returning a 403 error. A webfilter would just block it as a 404 because you can’t reach the resource.

We are seeing this problem as well in our production environment. Started happening about a week ago.

VM6:1 POST https://bam.nr-data.net/events/1/ec4b7d5e6c?a=9872589&v=1210.e2a3f80&to=MQdSNkZZCktZAUVdCghNdhdaWxBRVwweQxIRTEYLUU8XAlANXFE%3D&rst=10879&ck=1&ref=https://www.mycompany.com/ 403 (Forbidden)

Quick follow-up to my previous post. Our production environment runs on Heroku and we use the New Relic APM add-on. @jshields and @roy.delima, are your applications running on Heroku as well?

We are running on Heroku with a Ruby on Rails stack.

1 Like