Closed yatesco closed 1 year ago
From AWS (us-east-1),
ping diffhtml.org -4
PING (97.107.132.235) 56(84) bytes of data.
64 bytes from aboutnerd.com (97.107.132.235): icmp_seq=1 ttl=43 time=7.09 ms
64 bytes from aboutnerd.com (97.107.132.235): icmp_seq=2 ttl=43 time=7.10 ms
64 bytes from aboutnerd.com (97.107.132.235): icmp_seq=3 ttl=43 time=7.13 ms
64 bytes from aboutnerd.com (97.107.132.235): icmp_seq=4 ttl=43 time=7.12 ms
64 bytes from aboutnerd.com (97.107.132.235): icmp_seq=5 ttl=43 time=7.20 ms
64 bytes from aboutnerd.com (97.107.132.235): icmp_seq=6 ttl=43 time=7.20 ms
^C
--- ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5009ms
rtt min/avg/max/mdev = 7.093/7.139/7.197/0.042 ms
ping diffhtml.org -6
PING diffhtml.org(2600:3c03::f03c:91ff:fe96:8e92 (2600:3c03::f03c:91ff:fe96:8e92)) 56 data bytes
^C
--- diffhtml.org ping statistics ---
37 packets transmitted, 0 received, 100% packet loss, time 36845ms
Visiting http://diffhtml.org from the UK/Leicestershire gives:
It sometimes gives a security warning, which if you ignore, consistently goes to the same page.
Back up, I think letsencrypt is misconfigured on the server which is knocking out nginx and not restoring it. I'll try and see if anything is in the logs. Thanks for letting me know it's down!
Actually looks like this was routine Linode outage, sorry about the inconvience.
This Linode’s physical host is currently undergoing maintenance. During this time, your Linode will be shut down and remain offline, then returned to its last state (running or powered off). Please refer to your Support tickets for more information.
Thanks buddy :-)Sent from my iPhoneOn 12 Jan 2023, at 17:33, Tim Branyen @.***> wrote: Actually looks like this was routine Linode outage, sorry about the inconvience.
This Linode’s physical host is currently undergoing maintenance. During this time, your Linode will be shut down and remain offline, then returned to its last state (running or powered off). Please refer to your Support tickets for more information.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>