Website won't load: operation timed out
I'm new to PFSense (and more advanced networking), and I'm having some troubles..
I have an 2.4.4-RELEASE-p2 Pfsense.
Certain website's won't load (anymore), I'm pretty sure of 1 that worked 2 months ago without changing configuration on the router. The websites timing out.
When I enable Squid / Squidquard I get an error message by squid:
(60) Operation timed out.
When I disable squid / squidquard I get the default "browser time out" error.
What I already tried (after searching the internet):
- removing the cache of squid (/var/squid/cache)
- changing the MTU to default 1500 (no difference, and it has to be 1500 because of another network programmation)
- disabling squid/squidquard
- adding the ip's to "do Not Cache" in squid Proxy Server (found it on the internet) (ipadresse & domain.com 1 per line)
- created a group of the website's in "Target Categories" under SquidGuard and whitelisted them.
Nothing seems to work, so I can't find other sollutions on the internet.
Can someone guide me how to fix this, or what I have to check for more information (ping / commands / logs/ ...)?
This is a package issue ( squid related ). Because : when you remove squid, problem solved, right ?
Or more precise : wrong settings => bad results.
See the Squid package forum for more info Home > pfSense Packages > Cache/Proxy
Squid experts hang around over there.
At the beginning, I thought that the reason was squid / squidquard (blocking website's).
But after disabling this packages the problem still occurs.
Even after removing the packages now, there is no difference.
So there should be another reason. I don't know why, that's the reason why I posted it in General.
Also tested: I can access the website on a VPN connection...
could be a dns problem, what are you using as dns ? do you have another pc to try on the same lan?
Gertjan last edited by
Also a VPN ?
It's time to detail your setup.
10.0.0.10 is our local DNS-server
184.108.40.206 is the DNS of our provider.
Allow DNS servers to be overridden by DHCP/PPP on WAN is Enabled
That's the reason why 220.127.116.11 & 18.104.22.168 is enabled.
@Gertjan Not a VPN on the router, I used another VPN to check if it's accessible from outside the problemnetwork. What else do you need to know?
DNS resolution works well on pfSense ( use SSH or console access to test ).
Same thing for LAN devices ?
Btw : p3 is out for a while now.
try to set 22.214.171.124 as dns on your network interface as a test
@Gertjan I don't understand the question... (Same thing for LAN devices ?)
- I updated now to P3.
- I changed the DNS-servers. They are now:
Still not fixed..
So squid is not installed, and you can still not resolve?
Out of the box pfsense "resolves" it doesn't forward.. Can pfsense resolve site your trying to go to?
Are you forwarding to 10.0.0.10 - why would that be on your list of dns?
Do a simple test on pfsense, can it resolve say google?
Once you have validated pfsense can resolve, then you need to check if client is asking pfsense for dns, and does it resolve?
$ nslookup www.google.com Server: sg4860.local.lan Address: 192.168.9.253 Non-authoritative answer: Name: www.google.com Addresses: 2607:f8b0:4009:816::2004 126.96.36.199
I get this as result for DNS lookup on the pfsense for the problemdomain:
127.0.0.1 0 msec 188.8.131.52 17 msec 10.0.0.10 32 msec
When I do an nslookup, I get this:
nslookup google.com Server: UnKnown Address: 10.0.0.10 Non-authoritative answer: Name: google.com Addresses: 2a00:1450:400e:80e::200e 184.108.40.206
What is this 10.0.0.10, so your forwarding not resolving..
Did you setup some vpn client? Did you mess with your outbound nat?
Clients are using pfsense as their gateway? Do a simple traceroute from your clients to an outside IP.. Can you ping say 220.127.116.11 from your clients?
What are you lan rules on pfsense?
$ tracert -d 18.104.22.168 Tracing route to 22.214.171.124 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.9.253 2 10 ms 9 ms 9 ms 126.96.36.199 3 18 ms 9 ms 10 ms 188.8.131.52 4 8 ms 19 ms 10 ms 184.108.40.206 5 22 ms 13 ms 12 ms 220.127.116.11
As you there from my client, its first hop is pfsense, and then next hop is outside to isp..
Yes, the gateway is the ip of the PFsense (10.0.0.254).
I can ping and has this as a result for tracert of 18.104.22.168
Tracing route to 22.214.171.124 over a maximum of 30 hops 1 1 ms 1 ms 4 ms 10.0.0.254 2 24 ms 12 ms 11 ms 126.96.36.199 3 10 ms 19 ms 13 ms 188.8.131.52 4 15 ms 14 ms 15 ms 184.108.40.206 5 23 ms 16 ms 33 ms 220.127.116.11 6 * * * Request timed out. 7 20 ms 18 ms 17 ms 18.104.22.168 Trace complete.
And for the problemwebsite this is the result:
Tracing route to 235.*.belgacom.be [91.*.*.235] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 10.0.0.254 2 86 ms 16 ms 11 ms d51530001.static.telenet.be [22.214.171.124] 3 12 ms 11 ms 8 ms dd5e0c951.access.telenet.be [126.96.36.199] 4 15 ms 14 ms 25 ms dd5e0fa75.access.telenet.be [188.8.131.52] 5 * * * Request timed out. 6 18 ms 16 ms 14 ms 184.108.40.206 7 * * * Request timed out. 8 * 17 ms 17 ms svc10030.epemar7.isp.proximus.com [220.127.116.11] 9 * * * Request timed out. 10 24 ms 23 ms 34 ms 235.*.belgacom.be [91.*.*.235]
I had OpenVPN installed, but not anymore.. I removed it a while ago.
Outbound NAT Mode is Automatic.
Automatic Rules: Interface Source Source Port Destination Destination Port NAT Address NAT Port Static Port Description WAN 127.0.0.0/8 ::1/128 10.0.0.0/16 * * 500 WAN address * Auto created rule for ISAKMP WAN 127.0.0.0/8 ::1/128 10.0.0.0/16 * * * WAN address * Auto created rule
well clearly you leaving pfsense and getting to the wan via trace.
So what are you rules on your lan?
Don't understand the use of /16 for your local network - do you have 65K clients? But that is not going to be cause of your problem.
Is your browser still pointing to proxy? From your traceroute and your able to resolve.
So lets be clear is this ALL websites or just 1 or a couple?
And for the problemwebsite
That would indicate to me its just 1 site?
I will post the rules on Monday. (no remote accesss).
/16 is a gift from the past (schoolnetwork that grow very fast). For the moment we have +- 500 devices).
Of record: The whole network should be reconfigured. It's a work in progress, but not yet possible, as it is in use most of the time and I'm the only IT'er.
The problem is with "some" websites. Most of the time we didn't notice it (thinking it's a bad website), but this time it is the website of an important supplier. So we need this website every day.
"browser time out" error.
That doesn't seem like DNS unless it's resolving wrong. Assuming that really is the error seen on clients.
But yeah still unclear what clients are using for DNS here; is it pfSense?
And what mode pfSense is using for DNS; is it using the DNS Forwarder? The DNS Resolver in forwading mode or the default Resolver settings?
but this time it is the website of an important supplier.
But you are resolving this website to its IP.. So unless that is wrong? And your accessing other websites, and your not using proxy or ips.. How would the issue be related to pfsense?
Since on pfsense wan when you try and access this site - does pfsense sense the syn out its wan, what do you get back - if anything?
Picture of LAN-rules:
DNS-server 10.0.0.10 is an Windows Server. But the PFSense router is "new", configured by someone else (can't get in touch anymore).
DNS-resolver was enabled, default settings (normally, see screenshots). DNS forwarding is disabled.
LAN rules :
The second rule is overlapped by the third rule - remove that second rule, because it's TCP only, thus very strange at best.
Rule 3 and 4 - the last 2 - handle all traffic just fine.
DNS forwarding is disabled.
So pfSense doesn't use 10.0.0.10 to resolve. It goes directly to "the source".
Are you using DHCP on your LAN ? How is the DNS setup on your LAN clients ? Static ? By DHCP ? Check the DHCP server page : what is the DNS to hand over to LAN clients (if set) ?
Btw : why suing this local "10.0.0.10" DNS server (which probably forwards to again another DNS server, or it resolves directly, as pfSense does )?
Again - if you can resolve it, and just doesn't answer.. Unless your using proxy or ips.. pfsense not going to be doing anything different with traffic going there vs going to google.com
I would do a packet capture to prove to yourself pfsense is sending on your syn or not to the site.. There is nothing in your setup that you have shown that would stop one site over another site.
If you're using Squid/Squidguard you should really make sure both Squid and clients coming through it are using the same DNS server(s). If you are handing 10.0.0.10 to clients to use you should set that in Squid also.
However that would not explain why it still fails with Squid disabled. I agree I think a packet capture showing the failed connection would be the next step here.
10 24 ms 23 ms 34 ms 235..belgacom.be [91..*.235]
He seems to be able to trace there, so unless he is running proxy or ips - its not going to be pfsense issue.. Maybe a mtu problem getting there?
Might be helpful if actually posted the site fqdn.. So we could test it even.. What is the big deal about posting some public site on the internet... If I had problem going to say www.cnn.com how would saying I can not get to www.cnn.com be any sort of privacy concern? Unless this is some sort of p0rn site or something you don't want anyone knowing you visit ;)
We are using a DNS server (10.0.0.10) because we have a domain. The public DNS of that server is 18.104.22.168.
The url of the problem site is:
The lanrules are changed. (no overwrites anymore).
@johnpoz packet capture
15:51:27.776037 IP my.ip.. > 22.214.171.124.80: tcp 0
15:51:27.777709 IP my.ip.. > 126.96.36.199.80: tcp 0
15:51:28.025853 IP my.ip.. > 188.8.131.52.80: tcp 0
15:51:30.776740 IP my.ip...16614 > 184.108.40.206.80: tcp 0
15:51:30.778734 IP my.ip..29026 > 220.127.116.11.80: tcp 0
15:51:31.026104 IP my.ip...41937 > 18.104.22.168.80: tcp 0
there is a sonicwall there with Gateway GEO-IP Filter enabled.
are you sure is not the sonicwall that have a ban on you?
5:51:27.777709 IP my.ip.. > 22.214.171.124.80: tcp 0
15:51:28.025853 IP my.ip.. > 126.96.36.199.80: tcp 0
Well you sending.. but getting nothing back.. So its not pfsense blocking you.
Yup I get this
I am able to connect to it from the UK. It then invites me to login over http. If I try to use https I get a bad cert.
Those things tell me whoever is managing that site isn't paying much attention so you could well have been blocked by some automated system nobody ever checks.
It then invites me to login over http
Wow - that is a major vendor of yours? I would find a different vendor ;)
Yeah it's bad in numerous ways!
Sure hope maybe they do bathroom supplies or something and nothing to do with IT ;) Whatever they do, guess they don't want to do business with the US ;)
.. or italy, they do catering services anyway, i doubt they want to send food and staff to usa anyway :)
that subdomain is probably for sales representatives only
But maybe a secretary in the US wants to have an event their company is throwing in Belgium catered ;) Blocking IPs from other countries prob not the best way to grow the business ;)
i can see that web page using a proxy
from a security point of view it is useless
Ok, I'm glad we found the problem.. I didn't got the Sonicwall message, and because the router is pretty new, I thought it was my own fault..
The vendor is now aware of the problem. They will fix it. Thanks for the help, sorry it wasn't really a pfsense issue.