strange wget error behind pfsense
-
hi,
I have a debian 11 vm behind pfense(last version). when try to use wget it sometimes return error. at the same time a have no problem on chrome/opera/firefox clients!wget http://yahoo.com --2023-01-23 04:32:28-- http://yahoo.com/ Resolving yahoo.com (yahoo.com)... 98.137.11.164, 74.6.143.25, 98.137.11.163, ... Connecting to yahoo.com (yahoo.com)|98.137.11.164|:80... connected. HTTP request sent, awaiting response... 503 Service Unavailable 2023-01-23 04:32:28 ERROR 503: Service Unavailable.access to most sites are ok:
wget http://google.com --2023-01-24 09:19:25-- http://google.com/ Resolving google.com (google.com)... 216.239.38.120, 2001:4860:4802:32::78 Connecting to google.com (google.com)|216.239.38.120|:80... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: http://www.google.com/ [following] --2023-01-24 09:19:25-- http://www.google.com/ Resolving www.google.com (www.google.com)... 216.239.38.120, 2001:4860:4802:32::78 Reusing existing connection to google.com:80. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: 'index.html' index.html [ <=> ] 13.69K --.-KB/s in 0s 2023-01-24 09:19:26 (138 MB/s) - 'index.html' saved [14014]traffic capture ...
any idea?!
-
The remote server is sending a 503 error. That's nothing pfSense can do anything with.
Does it fail with https? It works fine every time for me here but it's automgically switching to https on this system:
steve@steve-NUC9i9QNX:~$ wget -O /dev/null http://yahoo.com URL transformed to HTTPS due to an HSTS policy --2023-01-24 13:52:44-- https://yahoo.com/ Resolving yahoo.com (yahoo.com)... 98.137.11.163, 74.6.231.20, 74.6.143.26, ... Connecting to yahoo.com (yahoo.com)|98.137.11.163|:443... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://www.yahoo.com/ [following] --2023-01-24 13:52:45-- https://www.yahoo.com/ Resolving www.yahoo.com (www.yahoo.com)... 87.248.100.215, 87.248.100.216, 2a00:1288:110:c305::1:8000, ... Connecting to www.yahoo.com (www.yahoo.com)|87.248.100.215|:443... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: ‘/dev/null’ /dev/null [ <=> ] 678.42K 1.78MB/s in 0.4s 2023-01-24 13:52:45 (1.78 MB/s) - ‘/dev/null’ saved [694706]Steve
-
@mr-pine Are you behind a VPN? I have had problems in the past connecting to the Yahoo! fantasy football site from a Hurricane Electric IPv6 address. Unfortunately I do not recall the error message. But if you're using a VPN they may be blocking it only one some of their servers...? As noted the response means the web server saw your request and returned the error code/message, so it's not a communication problem.
-
@steveits TNX for reply ,
No, I have a small LAN. some Opera/Windows/Linux clients. Only wget got this error !!! I AIso change browser agent id in wget but ... -
Did you try https?
-
@stephenw10
Https Works! it seems that http redirect has a problem.! -
And / or your test client is not respecting the HSTS policy maybe?
