Connection failure to websites

Connection failure to websites

Issues

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

Root Causes

  1. If the website which you are trying to reach is not up.
  1. If you are unable to reach to the particular website because of internet slowness issues.

Troubleshooting

Case1

Check whether the website is opening without proxy configuration inside the browser (No proxy in the middle).
If the website is not opening without a proxy, then it is not the problem with SafeSquid.
If it is opening without a proxy, then run the below command to verify whether the website is resolving or not.
  1. Command:  nslookup 192.168.27.30
To check SafeSquid server is connecting to 192.168.27.30 on port 80
  1. Command: telnet <WEBSITE> <PORT_TO_CONNECTON> 
you will get this output if the website is not able to connect
  1. telnet 192.168.27.30 80
  2. Trying 192.168.27.30...
  3. telnet: Unable to connect to remote host: No route to host
If the website can connect you will get the below output
  1. telnet <WEBSITE> <PORT_TO_CONNECTON>
you will get this output if the website is not able to connect:
  1. Command:telnet 192.168.27.30 80
you will get this output if the website can connect:
  1. root@dev:~# telnet 192.168.27.30 80
  2. Trying 192.168.27.30...
  3. Connected to 192.168.27.30.
  4. Escape character is '^]'.

Case 2

If you have a server with an on-premises environment integrated with directory services. DNS resolution is done by the directory DNS server.
To check the configuration on a local internal network and its address record pointed to an active directory (AD) or local DNS server
Run the below commands on the command prompt for abc.safesquid.com
  1. Command:  nslookup abc.safesquid.com
If the website is resolving to the local internal network e.g. (10.10.11.78,10.10.128.106)
You have to do the conditional forwarding to safesquid local caching DNS server
Go to the path: /etc/bind/
and create a file
  1. Command: vim named.conf
  2. root@swg:/etc/bind# vim named.conf
  3. // This is the primary configuration file for the BIND DNS server named.

  5. //

  7. // Please read /usr/share/doc/bind9/README.Debian.gz for information on the

  9. // structure of BIND configuration files in Debian, *BEFORE* you customize

  11. // this configuration file.

  13. //

  15. // If you are just adding zones, please do that in /etc/bind/named.conf.local

  17.  

  19. include "/etc/bind/named.conf.options";

  21. include "/etc/bind/named.conf.local";

  23. include "/etc/bind/named.conf.default-zones";

  25. include "/etc/bind/safesquid.dns.conf";

  27. include "/etc/bind/abc.safesquid.com";

  29. Go to the path
  30. Command: cd /etc/bind/
  31.  And create a file
  32. Command: vim abc.safesquid.co
  33. Add below lines
  34. zone "abc.safesquid.com" {

  36.   type forward;

  38.   forwarders {10.10.124.101;};

  40. };
Command to restart bind9 service:
  1. Command:/etc/init.d/bind9 restart
Verify whether the website is resolving to the local IP successfully or not.



    • 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 ...

    • Product Activation Failure

      Issues I uploaded my activation key, but still, SafeSquid UI is showing Failed to set Subscription details. After uploading the activation key, I am getting the template on the browser proxy server refusing connections. Unable to see subscription ...

    • 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 ...

    • 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 ...

    • Category update is not working

      Issues I am trying to add new websites to the whitelist or blacklist category, but it is not updating. Uploaded a new file with some websites and added them to a specific category, but I did not find those websites in the respective category. ...