A user was experiencing an issue with a monitor server, receiving a "Failed to authenticate" message. They had tried various solutions including double checking the time on the server, but a colleague was eventually able to solve the issue by identifying a mismatch between the certificate used and the one on the machine. Reinstalling the DX console and relinking resolved the issue.
Read the entire ‘Troubleshooting "Failed to Authenticate" issue on ControlUp Monitor Server’ thread below:
Hello all, looking for some advice on an issue I’m having for one monitor server.
Set this monitor up the same way I would with any other but I just keep getting "Failed to authenticate using advanced authentication."
I have tried fully removing and re-importing the shared cert, removing and re-adding the shared credential (which validates fine) and also tried giving the account I’m currently logged in with permission to the cert (which it should already have as its an admin account).
Anyone have any suggestions?
is the time correct on the server? that’s something that can break certs
Just double checked and times match across the board.
A colleague managed to get to the bottom off it, somehow there was a mismatch between the cert the controlup account was using that was signed into DX and the cert on the machine.
Had to remove all certs and re-install DX console and re-link.
Continue reading and comment on the thread ‘Troubleshooting “Failed to Authenticate” issue on ControlUp Monitor Server’. Not a member? Join Here!
Categories: All Archives, ControlUp Real-Time DX