Troubleshooting
List of the most common errors and their solutions
Infrastructure
-
Check a website's route:
In some cases, it's useful to know whether a website is unavailable because of the proxy service
or because of the server's network settings. -
ERR_ACCESS_DENIED - Forbidden - Local network:
You are unable to access the Internet through the proxy and you notice this error real-time events
-
Debugging the Proxy ACLs.
To enable detailed debugging for Access Control Lists (ACLs) in Proxy service, you have to adjust the debugging level to show more information about how ACLs are being evaluated
-
Roolback to the old Proxy version
You’ve just updated the proxy version, and since that update the proxy no longer starts or is malfunctioning.
Performance
- Proxy is very slow and Active Directory connection is unstable - 4.30 Unstable service pack or v4.40
- Proxy is very slow and Active Directory connection is unstable - 4.30 SP206/208
- After rebooting, file descriptors return back to default value
- How to check file descriptors using unix console ?
- Got system memory exceed notifications on proxy
Windows Active Directory
- Issues after apply the KB5055523
- KDC has no support for encryption type while getting credentials
- KDC Resolve False
- ERROR_PROXY_AUTH_UNSUPPORTED
- NT_STATUS_ACCOUNT_LOCKED_OUT
- NT_STATUS_NO_LOGON_SERVERS
- NT_STATUS_LOGON_FAILURE
- result=BH, notes=message: received type 1 NTLM token
- Strong(er) authentication required 00002028: LdapErr: DSID-0C09023C
- Unspecified GSS failure - Cannot decrypt ticket
- Unspecified GSS failure - Clock skew too great
- Unspecified GSS failure - keytab is likely out of date
- Unspecified GSS failure - Ticket not yet valid
- Unspecified GSS failure - Request is a replay
- Unspecified GSS failure - Service key not available
- Unspecified GSS failure - Cannot find key for xxx kvno xx in keytab (HaCluster)
- Error displayed "Unable to resolve xxx"
- xx.xxxx.local lookup activedirectory.local on 127.0.0.1:53: no such host
Web-filtering
No web-filtering after upgrade From 4.30x to v4.40/4.50
Monitoring
- Error accessing the Internet via proxy
By default, Artica will test Internet access by trying to connect to the Microsoft server www.msftncsi.com.
If it fails to do so, it will display an error and a report in the Web console.
- Capture an entire “surf sequence" on Chrome
How to capture a NetLog for protocol-level troubleshooting