Re: Problem with project link

On Thu, Dec 26, 2024 at 6:39 PM Jon Boone [email protected]
<https://mailto:[email protected]> wrote:

Yes, that's a strong indication that you have a DNS issue at play.  What
> does /etc/resolv.conf look like on your machine?
>
It says:

nameserver 127.0.0.53
options edns0 trust-ad
search lan


I don’t know why. I’ve never touched that file myself. However, the last
change to that file was Dec 26, 15:13.

But I can now reach gitlab with my browsers. Still can’t ssh into
gitlab.common-lisp.net (port 22 or 4022). No problems getting to
common-lisp.net on port 22.

Repo is apparently still read-only because I merge button isn’t merging for
https://gitlab.common-lisp.net/cmucl/cmucl/-/merge_requests/259


> —jon
>
>
> On Thu, Dec 26, 2024 at 9:31 PM Raymond Toy <[email protected]> wrote:
>
>>
>>
>> On Thu, Dec 26, 2024 at 6:12 PM Raymond Toy <[email protected]>
>> wrote:
>>
>>>
>>>
>>> On Thu, Dec 26, 2024 at 6:03 PM Jon Boone <[email protected]>
>>> wrote:
>>>
>>>> Ray,
>>>>
>>>>   Can you add the following to /etc/hosts, then quit & re-launch your
>>>> browsers to see if that corrects it temporarily?
>>>>
>>>
>>> Hey, that worked!  And I didn't even need to relaunch my browser.  I
>>> guess that means DNS is messed up somewhere?
>>>
>>
>> Ok, on a different machine (was using my laptop mostly before), I can now
>> navigate to gitlab.common-lisp.net.  I haven't changed anything on this
>> machine but I did reboot my wifi router again.
>>
>> On a different note now that I can access gitlab again, I tried to merge
>> a request.  It said the repo (cmucl) was read-only and to try again later.
>>
>>
>>
>>>> 65.108.13.229 gitlab.common-lisp.net
>>>>
>>>>
>>>>
>>>> —jon
>>>>
>>>>
>>>> On Thu, Dec 26, 2024 at 6:31 PM Raymond Toy <[email protected]>
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Thu, Dec 26, 2024 at 3:04 PM Jon Boone <[email protected]>
>>>>> wrote:
>>>>>
>>>>>> Ray,
>>>>>>
>>>>>>   Your ping is definitely using the correct IPv4 address
>>>>>> (65.108.13.229) for gitlab.common-lisp.net.  Note, that
>>>>>> www.common-lisp.net is still on the old host (148.251.208.23).
>>>>>> Unless your browsers are configured with DNS-over-HTTPS, you should be able
>>>>>> to properly navigate to gitlab.common-lisp.net at this point without
>>>>>> rebooting or clearing your DNS cache.  Can you try again?
>>>>>>
>>>>> I checked and I don't have dns-over-https enabled in either firefox or
>>>>> chrome.
>>>>>
>>>>> Still can't reach gitlab.common-lisp.net.
>>>>>
>>>>> I rebooted my wifi router too as that's apparently the only way to
>>>>> clear the DNS cache there.  (A Nest wifi).
>>>>>
>>>>>>
>>>>>> —jon
>>>>>>
>>>>>>
>>>>>> On Thu, Dec 26, 2024 at 5:41 PM Raymond Toy <[email protected]>
>>>>>> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Dec 26, 2024 at 12:53 PM David Cooper <
>>>>>>> [email protected]> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> Note that the DNS for gitlab.common-lisp.net switched over to a
>>>>>>>> new IP address (a new Hetzner host) Christmas eve.
>>>>>>>>
>>>>>>>
>>>>>>> What is the correct IP address?  Clearing the OS and browser DNS
>>>>>>> cache didn't seem to make a difference.  I can ping
>>>>>>> gitlab.common-lisp.net just fine:
>>>>>>> ```
>>>>>>> 64 bytes from future.common-lisp.net (65.108.13.229)
>>>>>>> ```
>>>>>>>
>>>>>>>>
>>>>>>>> So you may need to clear your DNS caches (browsers and OS).
>>>>>>>>
>>>>>>>> The toplevel common-lisp.net still resolves to the old host for
>>>>>>>> now, so ssh'ing there will get you to the legacy host.  But the plan is to
>>>>>>>> move that to the new host in due course as well.  I assume you'll need a
>>>>>>>> shell login for the new host? The new host is reachable via
>>>>>>>> future.common-lisp.net or gitlab.common-lisp.net, and i believe
>>>>>>>> your shell login account has been replicated on the new host
>>>>>>>>
>>>>>>> Yes, I'd like a shell login.  I still need to access it to upload
>>>>>>> cmucl release tarballs and such.
>>>>>>>
>>>>>>> Thanks for your help.  I think I should reboot my modem and wifi
>>>>>>> once again.  I think that's the only way to clear the DNS cache on my wifi
>>>>>>> router connected to my cable modem.
>>>>>>>
>>>>>>>> already.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Dave Cooper
>>>>>>>>
>>>>>>>> P.S. these mailing lists are still going through the legacy host.
>>>>>>>>
>>>>>>>>
>>>>>>>> ---- On Thu, 26 Dec 2024 13:45:50 -0500 * [email protected]
>>>>>>>> <[email protected]> * wrote ----
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, Dec 26, 2024 at 8:54 AM Jon Boone <[email protected]>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> I have no problems reaching it via Safari (Version 18.2
>>>>>>>> (20620.1.16.11.8))  or Chrome (Version 131.0.6778.205 (Official
>>>>>>>> Build) (arm64)) on macOS 15.2 (24C101) as of 2024-12-26 11:55 EST.
>>>>>>>>
>>>>>>>>
>>>>>>>> Ok, it must be me.  I can't reach it on any of my computers, even
>>>>>>>> after rebooting my modem and wifi point.  But I can over cellular with my
>>>>>>>> phone.  But every other site I try works fine over my home wifi.  I can
>>>>>>>> even ssh into common-lisp.net.
>>>>>>>>
>>>>>>>> Not sure what's going on.  I didn't update anything or add a proxy
>>>>>>>> or anything like that.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> —jon
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, Dec 26, 2024 at 11:26 AM Raymond Toy <[email protected]>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> On 12/25/24 12:28 PM, Georgiy Tugai wrote:
>>>>>>>>
>>>>>>>> I believe that the links should be working again now.
>>>>>>>>
>>>>>>>> FWIW, I can’t reach gitlab.common-lisp.net at all. Firefox says
>>>>>>>> it’s unable to connect. Chrome says it can’t be reached. I think this
>>>>>>>> started a couple of days ago, maybe?
>>>>>>>>
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Georgiy
>>>>>>>>
>>>>>>>> On 25/12/2024 21:02, Robert Goldman wrote:
>>>>>>>>
>>>>>>>> I was trying to follow a link from the projects hub,
>>>>>>>> https://common-lisp.net/phub for usocket, and got a 404.
>>>>>>>>
>>>>>>>> I've tried clicking some other links and they all 404 also, so
>>>>>>>> maybe there's some rewrite or redirect logic that's busted?
>>>>>>>>
>>>>>>>> Happy Holidays,
>>>>>>>> R
>>>>>>>>
>>>>>>>>
>>>>>>>> &#8203;
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Ray
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Ray
>>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> Ray
>>>>>
>>>>
>>>
>>> --
>>> Ray
>>>
>>
>>
>> --
>> Ray
>>
> --
Ray