Product Activation Failure

Product Activation Failure

Issues

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

Root Causes

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

Troubleshooting

Case 1: Check for 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 
Note: Restart SafeSquid service from SafeSquid Interface will work, only if the monit service configured properly on SafeSquid server.
Otherwise, you can directly restart the SafeSquid service from LINUX box by using 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 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, page is showing proxy server refusing connections
SafeSquid restart was not done, start the SafeSquid from the server console by using below command 
  1. /etc/init.d/safesquid start


    • Related Articles

    • DNS failure

      Issue: Via proxy sometimes occur an error "DNS Lookup for safesqddns.com failed". Root Causes If the FQDN of the website is incorrect. Local DNS server service is not running. If forwarder DNS server not able to resolve the query. If network service ...
    • Connection failure to websites

      Issues When I access website, it is displaying connection fail error “Connection to 192.168.27.30:80 failed” When I access https://abc.safesquid.com/ via proxy and login using my corporate email ID, it is displaying connection fail error “Connection ...
    • ISO installation Failure

      Issues When you misconfigured any of your DNS IP, Gateway or the NIC card, you will face issue as "Failed to retrieve the pre-configuration file". IP address which you assigned for SafeSquid proxy if blocked because of firewall, you will face issue ...
    • 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 ...