This article explains why the Insight node page freezes when accessing and the solution to resolve it.

-- When you access the Insight Node, the page freezes and throws an error "UNAUTHORIZED". When you check the Browser Debug logs, we will observe the below error.
 

"response": {

     "status": 401,

     "statusText": "UNAUTHORIZED",

     "httpVersion": "HTTP/1.1",

"cookies": [],

     "content": {

      "size": 31,

      "mimeType": "application/json",

      "compression": 0,

      "text": "{\"result\":\"Not authenticated\"}\n"

401 (Unauthorized) status code indicates that the request has not been applied because it lacks valid authentication credentials for the target resource.

-- This issue is observed because the connectivity between the SDI and SD is broken --

Analysis:

-- Check the connectivity between the SDI and SD is fine.

From SDI CLI using cysupport user

-- Run the below commands in SDI.

# netstat -anep | grep :443
# nc -zvw10 <Space_VIP_address> 443

-- When you run the nc command, you will observe a similar error.

nc: connect to <Space_VIP_address> port 443 (tcp) timed out: Operation now in progress

-- When you run the netstat command, you will observe the SYN_SENT packet, however, there won't be any ACK packet from the SD end.

From SD CLI

-- Run the below command for connectivity check.
# netstat -anep | grep <SDI_IP_address>

-- From SDI, we can observe the below error log.
 

# grep "10.x.x.x" /var/log/apache2/error.log
[Wed Mar xx 07:02:27.462723 20xx] [php7:notice] [pid 18330] [client 127.0.0.1:37092] Unable to connect to space: https://<space_vip_address>/api/space/user-management/users/1

-- By looking at the analysis above, we can understand that the connectivity between the SDI and SD_VIP address is not working. This is because there should be a FIREWALL which is DROPPING the SD acknowledgement packet.
-- First, check the firewall sessions and see if the packet is traversing through the firewall. Then check the session tables and see for the forward packet and if there is a return packet with some numbers in the bytes. If the bytes in the acknowledge packet show 0, then it's an issue at the firewall end where it is dropping the packet.
 

Session ID: 1234, Policy name: xxxxxx/98, Timeout: 16, Session State: Valid
 In: 10.xx.xx.xx/60148 --> 10.xx.xx.xx/22;tcp, Conn Tag: 0x0, If: irb.1011, Pkts: 3, Bytes: 180,
 Out: 10.xx.xx.xx/22 --> 10.xx.xx.xx/60148;tcp, Conn Tag: 0x0, If: irb.7, Pkts: 0, Bytes: 0,
Total sessions: 1

10.xx.xx.xx/60148 >> SDI
10.xx.xx.xx/22 >> SD

-- Another way to confirm >> Check the SUBNET of SDI and SD and if both are in different SUBNET, this issue will come.
 

Check in the firewall, if both the SDI and SD_VIP address are allowed to communicate between each other over the port 443. If not, allow the connection to resolve the issue.