When troubleshooting the connectivity to a website, trying to pinpoint
where a problem might be; my tip would be to use the traceroute command
with the TCP option *and* the port number. For example:
sudo traceroute www.postfix.org -T -p 443
Intermediate routers can be configured not to reply or with lower
priority, for packets which the router administrators deem not important
/ relevant..
Traceroute output below is from a system in the same data center as
where the postfix.org website is hosted. (Hops 3 & 4 are formatted for
readability; regarding different systems for intermediate hops, for each
of the 3 attempts used by this trace):
$ sudo traceroute www.postfix.org -T -p 443
traceroute to www.postfix.org (65.108.3.114), 30 hops max, 60 byte
packets
3 core31.hel1.hetzner.com (213.239.224.125) 0.421 ms
core32.hel1.hetzner.com (213.239.224.129) 0.417 ms
core31.hel1.hetzner.com (213.239.224.125) 0.413 ms
4 ex9k1.dc6.hel1.hetzner.com (213.239.252.198) 0.558 ms
ex9k1.dc6.hel1.hetzner.com (213.239.252.194) 0.613 ms
ex9k1.dc6.hel1.hetzner.com (213.239.252.198) 0.609 ms
5 ra.horus-it.com (65.108.3.114) 0.611 ms 0.606 ms 0.468 ms
The same system can access the Postfix website, tested with:
$ curl https://www.postfix.org/
If your traceroute with TCP / port 443 also gets (at least one) response
from ex9k1.dc6.hel1.hetzner.com and no response from ra.horus-it.com
then that's as close as you'll be able to get to where approximately the
blockage is.
Regards,
Alex
On 2025-02-12 18:34, John Griffiths via Postfix-users wrote:
Still not able to get to www.postfix.org [1]
(postfix-mirror.horus-it.com, 65.108.3.114) using traceroute or http.
Traceroute gets to the upstream router, but not to the host.
7 ae2.2.edge1.hel1.neo.colt.net (171.75.10.35) 152.755 ms 152.577
ms 152.565 ms
8 212.133.6.2 (212.133.6.2) 151.724 ms 151.480 ms 151.557 ms
9 core32.hel1.hetzner.com (213.239.224.26) 151.400 ms 151.029 ms
151.020 ms
10 ex9k1.dc6.hel1.hetzner.com (213.239.252.198) 151.203 ms 151.072
ms 151.492 ms
11 * * *
Glad the postfix.org MX is not on postfix-mirror.horus-it.com.
I'll check with my ISP, Frontier.com, to see if replies from
65.108.3.114 are being blocked.
After that, I'll try to pull a new DHCP IP. Ubiquity (Unifi) routers
have no way to release a DHCP IP from their supported GUI, so I will
have to use other means.
If that doesn't work, I'll update all my bookmarks to use a mirror.
Thanks all for trying.
John
On 2/12/25 12:03, Ralph Seichter via Postfix-users wrote:
* John Griffiths via Postfix-users:
Is my IP, 47.201.27.231, or the subnet(s) blocked in the firewall?
There are currently no existing blocks in the 47.201.0.0/16 subnet at
all. Unless you plan to attack the server hosting the Postfix website,
that server is not going to impose a block on your address. These
blocks
happen via automation, and it takes some effort to trigger them.
If (!) you are being blocked by a third party along the route, I have
no
knowledge of it, and no means of intervening either.
Links:
------
[1] http://www.postfix.org
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
