topic Re: Synthetic monitor creation failed with 401 in Synthetic Monitoring

Synthetic monitor creation failed with 401

Islam_Zedan — Fri, 07 Jul 2023 06:48:09 GMT

Hello,

We are facing an error while we try to create a synthetic monitor on the customer environment, checking the log we found the below error

[browser-BeaconSenderService-thread-1910] WARN BeaconSenderService: Failed to send beacon BeaconData[beaconEndpoint: https://localhost:9999/beacon/synthetic/browser/xxxxx-xxxx-xxxx-xxx-xxxxxxx?flavor=cors&app=xxxxxxxxxxxxxxxxxxx type: MessageType{value='BeaconRequest'}, beaconId: 1], got 401 (token: *****####))

Any ideas why the AG can't authenticate with the cluster server.

thanks,

Islam

Re: Synthetic monitor creation failed with 401

HannahM — Thu, 06 Jul 2023 08:37:21 GMT

Please can you create a chat or support ticket so we can check the Synthetic tokens are not stale in you environment.

Re: Synthetic monitor creation failed with 401

radek_jasinski — Thu, 06 Jul 2023 09:34:06 GMT

Hi @Islam_Zedan

Please note that you are trying to send a beacon to localhost. Have you verified the configuration of your AG and synthetic monitor?

Radek

Re: Synthetic monitor creation failed with 401

HannahM — Thu, 06 Jul 2023 09:59:52 GMT

This is expected in a Private ActiveGate. The beacon goes to the localhost and is redirected to the cluster. The logs just show the localhost connection

Re: Synthetic monitor creation failed with 401

radek_jasinski — Thu, 06 Jul 2023 10:03:02 GMT

Yes, you are right!

Re: Synthetic monitor creation failed with 401

Islam_Zedan — Sun, 06 Aug 2023 12:06:02 GMT

The problem solved after opening a support ticket, to fix the token issue.