Secure Access Cloud

  • Private Community
 View Only

  • 1.  ztna connector troubleshooting

    Posted May 20, 2026 03:54 PM

    Hi All
    I'm trying to troubleshoot a client's ZTNA issue.

    I'm seeing a lot of errors in the ZTNA connectors logs.
    For example:

    time="2026-05-19T08:58:24Z" level=error msg="Error while reading message" ApplicationId=0555c057-da93-4617-b466-f8fc742cb2da ClientSessionId=a361caf7-1968-44 43-95a3-4da1d9b49efa connectorVersion=2.11.9+124 error="read tcp 192.168.0.179:50158->34.165.64.68:443: read: connection reset by peer" PID=11
    time="2026-05-19T08:58:24Z" level=error msg="Problem closing connection" ApplicationId=0555c057-da93-4617-b466-f8fc742cb2da ClientSessionId=a361caf7-1968-444 3-95a3-4da1d9b49efa connectorVersion=2.11.9+124 error="tls: failed to send closeNotify alert (but connection was closed anyway): write tcp 192.168.0.179:5015 8->34.165.64.68:443: write: broken pipe" PID=11

    Or

    time="2026-05-17T07:17:54Z" level=error msg="Problem closing connection" ApplicationId=8b5fdb46-44c2-4dad-97c6-297063ddd3df ClientSessionId=471247af-b23a-4ad a-878b-193246330494 connectorVersion=2.11.9+124 error="tls: failed to send closeNotify alert (but connection was closed anyway): write tcp 192.168.0.179:5556 4->34.165.64.68:443: write: broken pipe" PID=11
    time="2026-05-17T07:17:54Z" level=error msg="Error while reading message" ApplicationId=14c3c8d2-3204-4d60-9918-f3c7648e12cf ClientSessionId=8c7d97dd-b200-4f54-b175-93fb6e2f1c6a connectorVersion=2.11.9+124 error="websocket: close 1011 (internal server error): Ping Timeout Reached Detected By Core-Server" PID=11

    But unfortunately, I can't understand these logs.
    For example, how can I figure out which application corresponds to ApplicationId=8b5fdb46-44c2-4dad-97c6-297063ddd3df?
    Or
    What does the following information tell me: error="websocket: close 1011 (internal server error): Ping Timeout Reached Detected By Core-Server"
    Or this
    error="tls: failed to send closeNotify alert (but connection was closed anyway): write tcp 192.168.0.179:5015 8->34.165.64.68:443: write: broken pipe" PID=11?

    Has anyone tried to figure this out?

    Thanks in advance.
    Dima



    -------------------------------------------


  • 2.  RE: ztna connector troubleshooting

    Broadcom Employee
    Posted May 24, 2026 02:15 PM

    Hey Dima,

    There are several ways to troubleshoot the connector.

    You mentioned that you are handling a customer case. Could you please open a support ticket and share it with me privately ?

    Thanks,

    Stas.

    -------------------------------------------