Hi, from my lan i have a problem to access my external web site.
the problem seemed tied to the exit on the wan1 so leaving the wan 2 everything seemed fine. after a few days, even coming out of wan 2, the problem arose. doing tests from a linux, this is the result:
* About to connect() to 18.104.22.168 port 80
* Trying 22.214.171.124... connected
* Connected to 126.96.36.199 (188.8.131.52) port 80
> GET / HTTP/1.1
> User-Agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.5
> Host: 184.108.40.206
> Accept: */*
< HTTP/1.1 503 Service Unavailable
< Server: squid/3.5.23
< Mime-Version: 1.0
< Date: Wed, 31 Jan 2018 08:46:36 GMT
< Content-Type: text/html;charset=utf-8
< Content-Length: 49
< X-Squid-Error: ERR_CONNECT_FAIL 111
< Vary: Accept-Language
< Content-Language: en
< X-Cache: MISS from mE0553D03EC60
< X-Cache-Lookup: MISS from mE0553D03EC60:3128
< Via: 1.1 mE0553D03EC60 (squid/3.5.23)
< Connection: close
Closing connection #0
Internal Error: Missing Template ERR_CONNECT_FAIL[root@lineeleccolnx ~]#
A 503 error normally indicates that the problem is with the HTTP server itself, common causes of this are,
Do you currently own/have Root access to the server? I'd check it and the logs on the server to ensure that it's not being overloaded.
Hi, thank for the answer.
unfortunately the site is not in my management. the problem is that it does not respond only if I'm on my LAN behind the MXx64.
if I try from other networks the site is reachable even if not very quick to respond.
Do you have an MX as your security gateway for your LAN environment? Are you running Content filtering or Threat protection, just wanting to ensure neither of these could be at fault?
Hi, i have disable trheat protection and prevention but problem not change. The device is not blocking from content filter
I remember if reboot the mx64 the problem it is resolved. But i have a problem to reboot the firewall.
Does the webserver itself have a firewall or whitelist that limits who can browse its content?
Are you using a Static or Dynamic public IP on the MX? As per @Adam comment above their might be a firewall/host-based firewall on the web server side which is blocking connectivity from your IP.