Product Activation Failure

Product Activation Failure

Issues

  1. I uploaded my activation key, but still, SafeSquid UI is showing Failed to set Subscription details.
  2. After uploading the activation key, I am getting the template on the browser proxy server refusing connections.
  3. Unable to see subscription details on the support page from the SafeSquid User Interface.

Root Causes

  1. SafeSquid server is unable to contact the SafeSquid Subscription server. 
  2. The file (activation key) was not uploaded correctly. 
  3. The file name you uploaded is other than activation_key.
  4. After uploading the activation key, the page shows the proxy server refusing connections.
  5. SafeSquid service restart was not done properly.

Troubleshooting

Case 1: Check for the activation_key file on the SafeSquid server.

Run the below command and check for the file 
  1. ls -lrt /usr/local/safesquid/security/
root@dev:~# ls -lrt /usr/local/safesquid/security/
total 60
drwxrwxr-- 2 ssquid root  4096 Jul 10 11:55 dns
-rw-rw-r-- 1 ssquid root   724 Jul 28 11:23 krb5.conf
-rw-rw-r-- 1 ssquid root  2111 Aug  3 18:52 activation_key
drwxrwxr-- 2 ssquid root 12288 Aug  4 16:04 policies
drwxrwxr-- 5 ssquid root  4096 Aug  4 16:09 ssl
-rw-rw-r-- 1 ssquid root 15744 Aug  5 09:51 activation_key.updates.backup
-rw-rw-r-- 1 ssquid root 15744 Aug  5 09:51 activation_key.updates
If the file was not found, then upload your activation key again and click on restart.
Notes
Note: Restart SafeSquid service from the SafeSquid Interface will work, only if the monit service is configured properly on the SafeSquid server.
Otherwise, you can directly restart the SafeSquid service from the LINUX box by using the below commands:
  1. /etc/init.d/safesquid stop
  2. /etc/init.d/safesquid start

Case 2: Check the connection to the Subscription server, by using the following commands

root@dev:~# ping swgupdates2.safesquid.net
PING swgupdates2.safesquid.net (104.236.27.61) 56(84) bytes of data.
64 bytes from 104.236.27.61: icmp_seq=1 ttl=52 time=309 ms
64 bytes from 104.236.27.61: icmp_seq=2 ttl=52 time=228 ms
--- swgupdates2.safesquid.net ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 228.387/269.078/309.770/40.694 ms
  1. nslookup swgupdates2.safesquid.net
Server:         127.0.0.1
Address:        127.0.0.1#53
Non-authoritative answer:
Name:   swgupdates2.safesquid.net
Address: 104.236.27.61
After uploading the activation key, the page shows the proxy server refusing connections
SafeSquid restart was not done, start the SafeSquid from the server console by using the below command:
  1. /etc/init.d/safesquid start




    • Related Articles

    • DNS Failure

      Issue Via proxy sometimes an error "DNS Lookup for safesqddns.com failed" occurs. Root Causes If the FQDN of the website is incorrect. The local DNS server service is not running. If the forwarder DNS server is not able to resolve the query. If ...

    • Connection failure to websites

      Issues When I access the website, it displays the connection failed error “Connection to 192.168.27.30:80 failed”. When I access https://abc.safesquid.com/ via proxy and log in using my corporate email ID, it displays the connection failed error ...

    • ISO installation Failure

      Issues When you misconfigure any of your DNS IP, Gateway or NIC cards, you will face the issue "Failed to retrieve the pre-configuration file". The IP address that you assigned for the SafeSquid proxy is blocked because of the firewall, you will face ...

    • SSL certificate downloaded with zero size OR unable to download SSL certificate

      Issues SSL certificate downloaded with zero size Unable to download SSL certificate Note: If you generate new activation key from Self-Service Portal and activate SafeSquid using same activation key. And directly download SSL certificate from ...

    • Standard Operating Procedure (SOP) for Troubleshooting Issues in your SafeSquid proxy server

      Purpose To provide a consistent and effective approach to troubleshooting network connectivity and web server issues using key commands. Scope This SOP applies to troubleshooting sessions involving DNS resolution, port connectivity, web server ...