Correcting a ?401 Invalid Proxy Tunnel Client ID? Error for an On Premise Monitor

Document ID : KB000029043
Last Modified Date : 14/02/2018
Show Technical Document Details

Correcting a “401 Invalid Proxy Tunnel Client ID” Error for an On Premise Monitor

Summary:

This article will discuss how to address the error “WARNING  Deamon will close as websocket returned: Invalid response status: 401 Invalid Proxy Tunnel Client ID” in the optunnel-client.log of the On Premise Monitor. This error prevents communication between the On Premise Monitor and App Synthetic Monitor, causing the monitor to fail to report. It is caused when the field “client-tunnel-cid:” is not set properly and config.yaml properties file.

Solution:

The “client-tunnel-cid” is normally set by the On Premise installer and under normal circumstances should require modification. However, should an issue occur with the id, you can also retrieve the ID from the API:

1-        First login to API by https://api.cloudmonitor.ca.com/1.6/acct_login?doc  to obtain an API user session (nKey).

2-        Then call https://api.cloudmonitor.ca.com/1.6/tunnel_id_list?doc . The “client-tunnel-cid” will appear in the tag <proxy_user> in the xml output.

3-         On the On Premise server, copy the <proxy_ user>  into the “client-tunnel-cid”….

client:

pidfile: /var/run/optunnel/optunnel-client.pid

client-tunnel-cid: '<proxy_user>’

4-       Restart the On Premise Monitor using the command: monit restart.

Should you need any assistance with this, please contact CA Support.