Tech Backpack/Troubleshooting: Difference between revisions
Created page with "This is a troubleshooting guide for Safety AI field technician. === Cannot connect to Visor on a remote Visbox === You opened a browser, typed in IP address of the Visbox and 5000 as port (such as http://10.1.1.10:5000) but page does not load. Check: # You have internet access by loading another external page, such as google.com. # Make sure you have network connection to the Visbox by pinging its ip address. If you can ping that means (1) Visbox is up and running,..." |
|||
| Line 4: | Line 4: | ||
You opened a browser, typed in IP address of the Visbox and 5000 as port (such as http://10.1.1.10:5000) but page does not load. | You opened a browser, typed in IP address of the Visbox and 5000 as port (such as http://10.1.1.10:5000) but page does not load. | ||
Check: | '''Check:''' | ||
# You have internet access by loading another external page, such as google.com. | # You have internet access by loading another external page, such as google.com. | ||
# Make sure you have network connection to the Visbox by pinging its ip address. If you can ping that means (1) Visbox is up and running, (2) you are on the same network. | # Make sure you have network connection to the Visbox by pinging its ip address. If you can ping that means (1) Visbox is up and running, (2) you are on the same network. | ||
# If you can ping, check the response time. A slow connection may prevent Visor from loading. | # If you can ping, check the response time. A slow connection may prevent Visor from loading. | ||
# If you cannot ping, check No connection to remote Visbox. | # If you cannot ping, check [[Tech Backpack/Troubleshooting#No connection to remote Visbox|No connection to remote Visbox]]. | ||
=== No connection to remote Visbox === | === No connection to remote Visbox === | ||
You cannot ping a remote Visbox. For that you need to make sure you are on the same network and Visbox is up and running. | You cannot ping a remote Visbox. For that you need to make sure you are on the same network and Visbox is up and running. | ||
Check: | '''Check:''' | ||
# Assuming you are connecting over ZeroTier VPN, check you are on the respective ZeroTier network with the device you want to connect to. | # Assuming you are connecting over ZeroTier VPN, check you are on the respective ZeroTier network with the device you want to connect to. | ||
# Check ZeroTier web site for the Visbox and make sure it is connected to ZeroTier as well. If it is not check Visbox not seen on ZeroTier network. | # Check ZeroTier web site for the Visbox and make sure it is connected to ZeroTier as well. If it is not check Visbox not seen on ZeroTier network. | ||
# Sometimes ZeroTier client service may fail. Restart the service. | # Sometimes ZeroTier client service may fail. Restart the service. | ||
=== Visbox not seen on ZeroTier network === | |||
You have a Visbox that is included in a ZeroTier network. ZeroTier management web page on zerotier.com shows when it was last online. This value must be close to zero, otherwise it means that this Visbox is not on that ZeroTier network and won't be accessible remotely, as least not for peer devices on the same network. | |||
Check: | |||
# The Visbox is up and running. | |||
# Check it has internet access by visiting an external site via browser or pinging a server on the internet, such as <code>ping 8.8.8.8</code>, public Google DNS server. If the device does not have internet access, fix it. For completing this item you would most probable need local access to the Visbox. | |||
# If Visbox is online and still not on ZeroTier, make sure ZeroTier service on the Visbox is running by <code>systemctl status zerotier-one</code>. If it is not, start the service by <code>systemctl start zerotier-one</code>, if it is running, restart the service by <code>systemctl restart zerotier-one</code>. | |||
# If still not visible on ZeroTier network, escalate to Event Gates Service Desk. | |||
Revision as of 12:45, 6 December 2025
This is a troubleshooting guide for Safety AI field technician.
Cannot connect to Visor on a remote Visbox
You opened a browser, typed in IP address of the Visbox and 5000 as port (such as http://10.1.1.10:5000) but page does not load.
Check:
- You have internet access by loading another external page, such as google.com.
- Make sure you have network connection to the Visbox by pinging its ip address. If you can ping that means (1) Visbox is up and running, (2) you are on the same network.
- If you can ping, check the response time. A slow connection may prevent Visor from loading.
- If you cannot ping, check No connection to remote Visbox.
No connection to remote Visbox
You cannot ping a remote Visbox. For that you need to make sure you are on the same network and Visbox is up and running.
Check:
- Assuming you are connecting over ZeroTier VPN, check you are on the respective ZeroTier network with the device you want to connect to.
- Check ZeroTier web site for the Visbox and make sure it is connected to ZeroTier as well. If it is not check Visbox not seen on ZeroTier network.
- Sometimes ZeroTier client service may fail. Restart the service.
Visbox not seen on ZeroTier network
You have a Visbox that is included in a ZeroTier network. ZeroTier management web page on zerotier.com shows when it was last online. This value must be close to zero, otherwise it means that this Visbox is not on that ZeroTier network and won't be accessible remotely, as least not for peer devices on the same network.
Check:
- The Visbox is up and running.
- Check it has internet access by visiting an external site via browser or pinging a server on the internet, such as
ping 8.8.8.8, public Google DNS server. If the device does not have internet access, fix it. For completing this item you would most probable need local access to the Visbox. - If Visbox is online and still not on ZeroTier, make sure ZeroTier service on the Visbox is running by
systemctl status zerotier-one. If it is not, start the service bysystemctl start zerotier-one, if it is running, restart the service bysystemctl restart zerotier-one. - If still not visible on ZeroTier network, escalate to Event Gates Service Desk.