tech.safesquid.com

Register on SafeSquid Self-Service Portal and obtain a Product Activation Key
Follow instructions on How to Activate a SafeSquid Instance
Now you should be able to validate the product activation like this:

Setup SSL Certificates as explained in Setting up SSL certificates from Self Service Portal

Configure your SafeSquid for HTTPS Inspection as explained in HTTPS Inspection

Now you should be able to check the enablement like this:

This may occur if the Virtual CD-ROM that was used for the SAB-ISO was not automatically disconnected / ejected on reboot post-installation.
So just disconnect the CD-ROM on your virtual machine, and reboot it.

I presume you followed instructions from: https://docs.safesquid.com/wiki/Standard_Installation for installation After the installation was done, the first login should have prompted you to set password for user administrator https://docs.safesquid.com/images/a/ac/Resetpassword.png Next you would ne...

Obviously then your desktop cannot resolve the FQDN swg.safesquid.in
Instead of setting the FQDN as the proxy host, you should set the IP address of your proxy service in your browser configuration

Check if your desktop can access swg.safesquid.in:8080
From your desktop:

1. ping swg.safesquid.in
   This should tell you if the FQDN is resolvable by your desktop
2. telnet swg.safesquid.in 8080
   If the FQDN is resolvable, this will tell you if your desktop can actually connect to the service

Please share screenshot of:

1. http://safesquid.cfg
2. Proxy Configuration for your browser

You could be frequently discovering websites that your enterprise may choose to block for all users. Various SOC service providers supply lists of websites that may be malignant or inappropriate. You could add such sites into a category using the Custom Category feature of SafeSquid. Creating an ent...

What do you see in the MySQL logs for the authentication failure error events?
What is the result of pamtester?

Looks like the database on MySQL needs to be given proper permissions.
Did you validate the credemtials for user@localhost?

Recommend use of pamtester for validating PAM related setup.
http://pamtester.sourceforge.net/