On 27/03/2022 02:42, Jack Craig wrote:
On Sat, Mar 26, 2022 at 1:57 AM Ed Greshko <ed.greshko@xxxxxxxxxxx> wrote:
On 26/03/2022 16:33, Peter Boy wrote:
>
>> Am 26.03.2022 um 08:55 schrieb Ed Greshko <ed.greshko@xxxxxxxxxxx>:
>>
>> ws.linuxlighthouse.com <http://ws.linuxlighthouse.com> has address 108.220.213.121
>>
>> Now try connecting to http://ws.linuxlighthouse.com/
> Not surprisingly, the server is unavailable. After all, this is the OP's network mystery.
>
> Question is, can the OP log in to the server anyway? That would be a good start to get the mystery resolved.
Yes, that is a qood question. Can the server be accessed on the internal network.
Also, I wonder if the OP has rebooted the network equipment.
rebooted yes
I suggest you call AT&T support as they supplied the replacement equipment and it should have been configured to
pass 108.220.213.X traffic. That appears to be nott the case.
FWIW, It seems the Fedora mailing list was "stuck". All the mail just flooded in on Sunday late morning my time.
--
Did 황준호 die?
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
