You may get locked out yourselves whenever you are trying to create policies in the Access Restrictions section of SafeSquid.
You suddenly get messages as Access Denied on the browser.
Root Cause
SafeSquid actually evaluates entries in the Access Restrictions one by one from top-down order matching each entry with the connection. Once an entry with an IP address or the user name matches a connection, the following entries will not be evaluated against that connection.
So, once you are trying to create an entry in the Access Restrictions, always make sure that there is at least one entry that is going to allow you to access the web interface (http://safesquid.cfg/). This in other words means that there must be an entry that matches your connections and has Web interface (Config) selected from the Access field.
Example
Consider a scenario wherein you have three entries in the Allow List of Access Restrictions section.
The first one is to access the web interface via SSH tunnel.
The second one is to allow the AUTHENTICATION BYPASS profile.
The third one is the entry through which you're accessing the internet.
You have created another entry in which you have removed the Web interface in the Access field and added it. The entry is added as the fourth one and you have moved it to 3rd by clicking on move up. Now the third entry matches your connections (since the first is for SSH tunnels and the second is for the AUTHENTICATION BYPASS profile) in which you have disabled the Web interface. So, you will be locked out and given a template Access Denied.
To avoid this kind of situation, you always need to maintain an entry that allows you to access the Web interface.
Troubleshooting