Unable to access the Snare Server via the web

Owned by Carlos Osorio
Last updated: Dec 17, 2020 by Steve Challans
1 min read


SUMMARY

17th Dec 2020

Symptoms

A web browser is used to connect to the Snare Server, but it either 'times out' or a page is displayed stating that the site cannot be found.

 Recommended

  1. Check server is alive by 'pinging' the DNS name or IP Address of the box, as shown below. If the machine is not able to be 'pinged', then it is either off line, turned off, or the network is down or unable to be accessed at some point.

  2. Check proxy settings on the browser. Try and connect via the agency/company browser, and then turn off the proxy setting, OR configure the proxy bypass settings.

  3. Check if there is a firewall that is blocking access on port 80

  4. If the above task is successful, then attempt to connect to the Snare Server using SSH. If a connection attempt is slow, then it is likely to be due to the Snare Server undertaking a large scheduled task. However, in most cases, the Snare Server should respond reasonably quickly to web requests when a user attempts to connect to it via a web browser.

  5. Login to the console and check the system does not have a file system full, run

    1. df -h - and check for any file system that is showing as 100%, if it does then check what is consuming the disks space

    2. cd do the file system location and run “ du -sh *” this will report on what directories or files are using space in this location.

  6. If you are unable to resolve the space problem then please contact support.