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
I believe that the links should be working again now.
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
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
​
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.
—jon
On Thu, Dec 26, 2024 at 11:26 AM Raymond Toy toy.raymond@gmail.com 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
​
On Thu, Dec 26, 2024 at 8:54 AM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com 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
​
Note that the DNS for gitlab.common-lisp.net switched over to a new IP address (a new Hetzner host) Christmas eve.
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 already.
Dave Cooper
P.S. these mailing lists are still going through the legacy host.
---- On Thu, 26 Dec 2024 13:45:50 -0500 toy.raymond@gmail.com wrote ----
On Thu, Dec 26, 2024 at 8:54 AM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com 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
​
--
Ray
On Thu, Dec 26, 2024 at 12:53 PM David Cooper david.cooper@genworks.com 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 * toy.raymond@gmail.com toy.raymond@gmail.com * wrote ----
On Thu, Dec 26, 2024 at 8:54 AM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com 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
​
-- Ray
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?
—jon
On Thu, Dec 26, 2024 at 5:41 PM Raymond Toy toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 12:53 PM David Cooper david.cooper@genworks.com 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 * toy.raymond@gmail.com toy.raymond@gmail.com * wrote ----
On Thu, Dec 26, 2024 at 8:54 AM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com 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
​
-- Ray
-- Ray
On Thu, Dec 26, 2024 at 3:04 PM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 12:53 PM David Cooper david.cooper@genworks.com 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 * toy.raymond@gmail.com toy.raymond@gmail.com * wrote ----
On Thu, Dec 26, 2024 at 8:54 AM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com 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
​
-- Ray
-- Ray
Ray,
Can you add the following to /etc/hosts, then quit & re-launch your browsers to see if that corrects it temporarily?
65.108.13.229 gitlab.common-lisp.net
—jon
On Thu, Dec 26, 2024 at 6:31 PM Raymond Toy toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 3:04 PM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 12:53 PM David Cooper david.cooper@genworks.com 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 * toy.raymond@gmail.com toy.raymond@gmail.com * wrote ----
On Thu, Dec 26, 2024 at 8:54 AM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com 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
​
-- Ray
-- Ray
-- Ray
On Thu, Dec 26, 2024 at 6:03 PM Jon Boone ipmonger@delamancha.org 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?
65.108.13.229 gitlab.common-lisp.net
—jon
On Thu, Dec 26, 2024 at 6:31 PM Raymond Toy toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 3:04 PM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 12:53 PM David Cooper < david.cooper@genworks.com> 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 * toy.raymond@gmail.com toy.raymond@gmail.com * wrote ----
On Thu, Dec 26, 2024 at 8:54 AM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com 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
​
-- Ray
-- Ray
-- Ray
On Thu, Dec 26, 2024 at 6:12 PM Raymond Toy toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 6:03 PM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 3:04 PM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 12:53 PM David Cooper < david.cooper@genworks.com> 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 * toy.raymond@gmail.com toy.raymond@gmail.com * wrote ----
On Thu, Dec 26, 2024 at 8:54 AM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com 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
​
-- Ray
-- Ray
-- Ray
-- Ray
Yes, that's a strong indication that you have a DNS issue at play. What does /etc/resolv.conf look like on your machine?
—jon
On Thu, Dec 26, 2024 at 9:31 PM Raymond Toy toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 6:12 PM Raymond Toy toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 6:03 PM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 3:04 PM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 12:53 PM David Cooper < david.cooper@genworks.com> 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 * toy.raymond@gmail.com > toy.raymond@gmail.com * wrote ---- > > > > On Thu, Dec 26, 2024 at 8:54 AM Jon Boone ipmonger@delamancha.org > 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 toy.raymond@gmail.com > 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 > > > ​ > > > > -- > Ray > > >
-- Ray
-- Ray
-- Ray
-- Ray
On Thu, Dec 26, 2024 at 6:39 PM Jon Boone ipmonger@delamancha.org https://mailto:ipmonger@delamancha.org 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 toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 6:12 PM Raymond Toy toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 6:03 PM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 3:04 PM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com wrote:
> > > On Thu, Dec 26, 2024 at 12:53 PM David Cooper < > david.cooper@genworks.com> 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 * toy.raymond@gmail.com >> toy.raymond@gmail.com * wrote ---- >> >> >> >> On Thu, Dec 26, 2024 at 8:54 AM Jon Boone ipmonger@delamancha.org >> 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 toy.raymond@gmail.com >> 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 >> >> >> ​ >> >> >> >> -- >> Ray >> >> >> > > -- > Ray >
-- Ray
-- Ray
-- Ray
--
Ray
The nameserver entry (127.0.0.53) indicates that you have some kind of internal process on the machine that should be providing your dns resolution. What OS and version are you running?
—jon
On Fri, Dec 27, 2024 at 11:01 AM Raymond Toy toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 6:39 PM Jon Boone ipmonger@delamancha.org https://mailto:ipmonger@delamancha.org 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 toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 6:12 PM Raymond Toy toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 6:03 PM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 3:04 PM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com > wrote: > >> >> >> On Thu, Dec 26, 2024 at 12:53 PM David Cooper < >> david.cooper@genworks.com> 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 * toy.raymond@gmail.com >>> toy.raymond@gmail.com * wrote ---- >>> >>> >>> >>> On Thu, Dec 26, 2024 at 8:54 AM Jon Boone ipmonger@delamancha.org >>> 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 < >>> toy.raymond@gmail.com> 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 >>> >>> >>> ​ >>> >>> >>> >>> -- >>> Ray >>> >>> >>> >> >> -- >> Ray >> >
-- Ray
-- Ray
-- Ray
--
Ray
Fedora 41. Just recently upgraded my laptop. But my desktop running Fedora 40 has the same thing. But it also had problems connecting.
On Fri, Dec 27, 2024, 8:55 AM Jon Boone ipmonger@delamancha.org wrote:
The nameserver entry (127.0.0.53) indicates that you have some kind of internal process on the machine that should be providing your dns resolution. What OS and version are you running?
—jon
On Fri, Dec 27, 2024 at 11:01 AM Raymond Toy toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 6:39 PM Jon Boone ipmonger@delamancha.org https://mailto:ipmonger@delamancha.org 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 toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 6:12 PM Raymond Toy toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 6:03 PM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com wrote:
> > > On Thu, Dec 26, 2024 at 3:04 PM Jon Boone ipmonger@delamancha.org > 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 toy.raymond@gmail.com >> wrote: >> >>> >>> >>> On Thu, Dec 26, 2024 at 12:53 PM David Cooper < >>> david.cooper@genworks.com> 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 * toy.raymond@gmail.com >>>> toy.raymond@gmail.com * wrote ---- >>>> >>>> >>>> >>>> On Thu, Dec 26, 2024 at 8:54 AM Jon Boone < >>>> ipmonger@delamancha.org> 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 < >>>> toy.raymond@gmail.com> 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 >>>> >>>> >>>> ​ >>>> >>>> >>>> >>>> -- >>>> Ray >>>> >>>> >>>> >>> >>> -- >>> Ray >>> >> > > -- > Ray >
-- Ray
-- Ray
--
Ray
Hi Raymond,
Thanks for your continuing patience. The "repo read only" vibe you're experiencing may well be caused by the same issue as your inability to ssh to the host, since it might be true that gitlab is using normal ssh behind the scenes to do a merge even if said merge is being triggered through the web ui.
If someone with sydo on the new machine could get to it before me and feels like it, please check the /home/rtoy/.ssh/ for correct ownerships, permissions, and authorized_keys contents. Assuming this is not still a basic connectivity issue (maybe try ssh -v[v] to confirm that).
Otherwise, I should be able to get on this within the next couple hours.
Dave Cooper
---- On Fri, 27 Dec 2024 11:58:24 -0500 toy.raymond@gmail.com wrote ----
Fedora 41. Just recently upgraded my laptop. But my desktop running Fedora 40 has the same thing. But it also had problems connecting.
On Fri, Dec 27, 2024, 8:55 AM Jon Boone ipmonger@delamancha.org wrote:
The nameserver entry (127.0.0.53) indicates that you have some kind of internal process on the machine that should be providing your dns resolution. What OS and version are you running?
—jon
On Fri, Dec 27, 2024 at 11:01 AM Raymond Toy toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 6:39 PM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 6:12 PM Raymond Toy toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 6:03 PM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 3:04 PM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 12:53 PM David Cooper david.cooper@genworks.com 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 wil ...
I can work with Ray on this. I already corrected the permissions on his authorized_keys file on future....
—jon
On Fri, Dec 27, 2024 at 12:17 PM David Cooper david.cooper@genworks.com wrote:
Hi Raymond,
Thanks for your continuing patience. The "repo read only" vibe you're experiencing may well be caused by the same issue as your inability to ssh to the host, since it might be true that gitlab is using normal ssh behind the scenes to do a merge even if said merge is being triggered through the web ui.
If someone with sydo on the new machine could get to it before me and feels like it, please check the /home/rtoy/.ssh/ for correct ownerships, permissions, and authorized_keys contents. Assuming this is not still a basic connectivity issue (maybe try ssh -v[v] to confirm that).
Otherwise, I should be able to get on this within the next couple hours.
Dave Cooper
---- On Fri, 27 Dec 2024 11:58:24 -0500 * toy.raymond@gmail.com toy.raymond@gmail.com * wrote ----
Fedora 41. Just recently upgraded my laptop. But my desktop running Fedora 40 has the same thing. But it also had problems connecting.
On Fri, Dec 27, 2024, 8:55 AM Jon Boone ipmonger@delamancha.org wrote:
The nameserver entry (127.0.0.53) indicates that you have some kind of internal process on the machine that should be providing your dns resolution. What OS and version are you running?
—jon
On Fri, Dec 27, 2024 at 11:01 AM Raymond Toy toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 6:39 PM Jon Boone ipmonger@delamancha.org https://mailto:ipmonger@delamancha.org 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 toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 6:12 PM Raymond Toy toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 6:03 PM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 3:04 PM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 12:53 PM David Cooper david.cooper@genworks.com 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 * toy.raymond@gmail.com toy.raymond@gmail.com * wrote ----
On Thu, Dec 26, 2024 at 8:54 AM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com 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
​
-- Ray
-- Ray
-- Ray
-- Ray
-- Ray
-- Ray
I think I was able to configure future.common-lisp.net so Ray can login. Do we have a wiki or other notes location that I can add to so we can keep track of these changes for future reference?
—jon
On Fri, Dec 27, 2024 at 12:42 PM Jon Boone ipmonger@delamancha.org wrote:
I can work with Ray on this. I already corrected the permissions on his authorized_keys file on future....
—jon
On Fri, Dec 27, 2024 at 12:17 PM David Cooper david.cooper@genworks.com wrote:
Hi Raymond,
Thanks for your continuing patience. The "repo read only" vibe you're experiencing may well be caused by the same issue as your inability to ssh to the host, since it might be true that gitlab is using normal ssh behind the scenes to do a merge even if said merge is being triggered through the web ui.
If someone with sydo on the new machine could get to it before me and feels like it, please check the /home/rtoy/.ssh/ for correct ownerships, permissions, and authorized_keys contents. Assuming this is not still a basic connectivity issue (maybe try ssh -v[v] to confirm that).
Otherwise, I should be able to get on this within the next couple hours.
Dave Cooper
---- On Fri, 27 Dec 2024 11:58:24 -0500 * toy.raymond@gmail.com toy.raymond@gmail.com * wrote ----
Fedora 41. Just recently upgraded my laptop. But my desktop running Fedora 40 has the same thing. But it also had problems connecting.
On Fri, Dec 27, 2024, 8:55 AM Jon Boone ipmonger@delamancha.org wrote:
The nameserver entry (127.0.0.53) indicates that you have some kind of internal process on the machine that should be providing your dns resolution. What OS and version are you running?
—jon
On Fri, Dec 27, 2024 at 11:01 AM Raymond Toy toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 6:39 PM Jon Boone ipmonger@delamancha.org https://mailto:ipmonger@delamancha.org 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 toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 6:12 PM Raymond Toy toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 6:03 PM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 3:04 PM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 12:53 PM David Cooper david.cooper@genworks.com 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 * toy.raymond@gmail.com toy.raymond@gmail.com * wrote ----
On Thu, Dec 26, 2024 at 8:54 AM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com 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
​
-- Ray
-- Ray
-- Ray
-- Ray
-- Ray
-- Ray
https://cryptpad.fr/pad/#/2/pad/edit/IYetddW5zzchwJOR-ivI8e08
On Fri, Dec 27, 2024, 14:44 Jon Boone ipmonger@delamancha.org wrote:
I think I was able to configure future.common-lisp.net so Ray can login. Do we have a wiki or other notes location that I can add to so we can keep track of these changes for future reference?
—jon
On Fri, Dec 27, 2024 at 12:42 PM Jon Boone ipmonger@delamancha.org wrote:
I can work with Ray on this. I already corrected the permissions on his authorized_keys file on future....
—jon
On Fri, Dec 27, 2024 at 12:17 PM David Cooper david.cooper@genworks.com wrote:
Hi Raymond,
Thanks for your continuing patience. The "repo read only" vibe you're experiencing may well be caused by the same issue as your inability to ssh to the host, since it might be true that gitlab is using normal ssh behind the scenes to do a merge even if said merge is being triggered through the web ui.
If someone with sydo on the new machine could get to it before me and feels like it, please check the /home/rtoy/.ssh/ for correct ownerships, permissions, and authorized_keys contents. Assuming this is not still a basic connectivity issue (maybe try ssh -v[v] to confirm that).
Otherwise, I should be able to get on this within the next couple hours.
Dave Cooper
---- On Fri, 27 Dec 2024 11:58:24 -0500 * toy.raymond@gmail.com toy.raymond@gmail.com * wrote ----
Fedora 41. Just recently upgraded my laptop. But my desktop running Fedora 40 has the same thing. But it also had problems connecting.
On Fri, Dec 27, 2024, 8:55 AM Jon Boone ipmonger@delamancha.org wrote:
The nameserver entry (127.0.0.53) indicates that you have some kind of internal process on the machine that should be providing your dns resolution. What OS and version are you running?
—jon
On Fri, Dec 27, 2024 at 11:01 AM Raymond Toy toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 6:39 PM Jon Boone ipmonger@delamancha.org https://mailto:ipmonger@delamancha.org 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 toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 6:12 PM Raymond Toy toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 6:03 PM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 3:04 PM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com wrote:
On Thu, Dec 26, 2024 at 12:53 PM David Cooper david.cooper@genworks.com 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 * toy.raymond@gmail.com toy.raymond@gmail.com * wrote ----
On Thu, Dec 26, 2024 at 8:54 AM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com 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
​
-- Ray
-- Ray
-- Ray
-- Ray
-- Ray
-- Ray
On 12/27/24 11:44 AM, Jon Boone wrote:
I think I was able to configure future.common-lisp.net http://future.common-lisp.net so Ray can login. Do we have a wiki or other notes location that I can add to so we can keep track of these changes for future reference?
Just to let everyone know, I can now ssh to gitlab.common-lisp.net. Both port 22 and 4022 work.
Thanks for all your help in getting this fixed.
However, I still have problems accessing the cmucl repo. The merge button says the repo is read-only. And I just tried to push a commit to the repo. git says it’s read-only and there’s a fatal error that it can’t read the repo and to check if I have the correct access rights.
—jon
On Fri, Dec 27, 2024 at 12:42 PM Jon Boone ipmonger@delamancha.org wrote:
I can work with Ray on this. I already corrected the permissions on his authorized_keys file on future.... —jon On Fri, Dec 27, 2024 at 12:17 PM David Cooper <david.cooper@genworks.com> wrote: Hi Raymond, Thanks for your continuing patience. The "repo read only" vibe you're experiencing may well be caused by the same issue as your inability to ssh to the host, since it might be true that gitlab is using normal ssh behind the scenes to do a merge even if said merge is being triggered through the web ui. If someone with sydo on the new machine could get to it before me and feels like it, please check the /home/rtoy/.ssh/ for correct ownerships, permissions, and authorized_keys contents. Assuming this is not still a basic connectivity issue (maybe try ssh -v[v] to confirm that). Otherwise, I should be able to get on this within the next couple hours. Dave Cooper ---- On Fri, 27 Dec 2024 11:58:24 -0500 *toy.raymond@gmail.com * wrote ---- Fedora 41. Just recently upgraded my laptop. But my desktop running Fedora 40 has the same thing. But it also had problems connecting. On Fri, Dec 27, 2024, 8:55 AM Jon Boone <ipmonger@delamancha.org> wrote: The nameserver entry (127.0.0.53) indicates that you have some kind of internal process on the machine that should be providing your dns resolution. What OS and version are you running? —jon On Fri, Dec 27, 2024 at 11:01 AM Raymond Toy <toy.raymond@gmail.com> wrote: On Thu, Dec 26, 2024 at 6:39 PM Jon Boone ipmonger@delamancha.org <https://mailto:ipmonger@delamancha.org> 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 <http://gitlab.common-lisp.net> (port 22 or 4022). No problems getting to common-lisp.net <http://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 <toy.raymond@gmail.com> wrote: On Thu, Dec 26, 2024 at 6:12 PM Raymond Toy <toy.raymond@gmail.com> wrote: On Thu, Dec 26, 2024 at 6:03 PM Jon Boone <ipmonger@delamancha.org> 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 <http://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 <http://gitlab.common-lisp.net> —jon On Thu, Dec 26, 2024 at 6:31 PM Raymond Toy <toy.raymond@gmail.com> wrote: On Thu, Dec 26, 2024 at 3:04 PM Jon Boone <ipmonger@delamancha.org> wrote: Ray, Your ping is definitely using the correct IPv4 address (65.108.13.229) for gitlab.common-lisp.net <http://gitlab.common-lisp.net>. Note, that www.common-lisp.net <http://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 <http://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 <http://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 <toy.raymond@gmail.com> wrote: On Thu, Dec 26, 2024 at 12:53 PM David Cooper <david.cooper@genworks.com> wrote: Note that the DNS for gitlab.common-lisp.net <http://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 <http://gitlab.common-lisp.net> just fine: ``` 64 bytes from future.common-lisp.net <http://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 <http://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 <http://future.common-lisp.net> or gitlab.common-lisp.net <http://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 *toy.raymond@gmail.com * wrote ---- On Thu, Dec 26, 2024 at 8:54 AM Jon Boone <ipmonger@delamancha.org> 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 <http://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 <toy.raymond@gmail.com> 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 <http://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 ​ -- Ray -- Ray -- Ray -- Ray -- Ray -- Ray
​
---- On Fri, 27 Dec 2024 14:44:18 -0500 ipmonger@delamancha.org wrote ----
I think I was able to configure future.common-lisp.net so Ray can login. Do we have a wiki or other notes location that I can add to so we can keep track of these changes for future reference?
—jon
https://cryptpad.fr/pad/#/2/pad/edit/IYetddW5zzchwJOR-ivI8e08
P.S. we need to start pruning accumulated back-content from these list emails, or they will raise flags with content filters.
Ok, I pruned the history from this response, as I was already getting the feedback that the responses were queued for approval by the list moderators.
I updated the cryptpad with the details, but for Ray's information, I had to update the permissions on the ~rtoy/.ssh/authorized_keys file to be 0600 and then also get the /etc/shadow and /etc/gshadow files updated by using pwconv and grpconv. After that, he was able to login via ssh.
How do we figure out the repo being read-only (which I'm guessing has to do with some ownership issues in the gitlab config)?
—jon
Hi Raymond,
You might need to add your ed25519 public key to here: https://gitlab.common-lisp.net/-/user_settings/ssh_keys
Make sure the same one which is in your .ssh/authorized_keys and which you know is the one letting you ssh in, is also added to that list in the gitlab UI. I think your "rtoy" gitlab user and your "rtoy" shell login account are treated as two different things so the requisite public key has to be in both places.
The stronger key (ed25519) may be a requirement which came into play with a recent gitlab update. I also had to add an ed25519 key for my pushes/pulls to start working. A recent gitlab update, or a setting we have somehow imposed upon this new instance. In either case, I don't mind pushing for everyone to review their keys and add new stronger ones if needed.
Please advise, Thanks,
Dave
---- On Fri, 27 Dec 2024 16:30:32 -0500 Jon Boone ipmonger@delamancha.org wrote ---...
How do we figure out the repo being read-only (which I'm guessing has to do with some ownership issues in the gitlab config)?
David,
I'm wondering if this is perhaps also related:
I tried to pull the latest updates from the cmucl/cmucl repo and received this message:
remote: You (@jboone) must accept the Terms of Service in order to perform this action. To accept these terms, please access GitLab from a web browser at https://gitlab.common-lisp.net.
But, when I navigate to https://gitlab.common-lisp.net in my web browser and login, I don't see any prompts to accept the Terms of Service as outstanding....
--jon
—jon
On Fri, Dec 27, 2024 at 5:30 PM David Cooper david.cooper@genworks.com wrote:
Hi Raymond,
You might need to add your ed25519 public key to here: SSH Keys · User Settings · GitLab https://gitlab.common-lisp.net/-/user_settings/ssh_keys
Make sure the same one which is in your .ssh/authorized_keys and which you know is the one letting you ssh in, is also added to that list in the gitlab UI. I think your "rtoy" gitlab user and your "rtoy" shell login account are treated as two different things so the requisite public key has to be in both places.
The stronger key (ed25519) may be a requirement which came into play with a recent gitlab update. I also had to add an ed25519 key for my pushes/pulls to start working. A recent gitlab update, or a setting we have somehow imposed upon this new instance. In either case, I don't mind pushing for everyone to review their keys and add new stronger ones if needed.
Please advise, Thanks,
Dave
---- On Fri, 27 Dec 2024 16:30:32 -0500 *Jon Boone <ipmonger@delamancha.org ipmonger@delamancha.org>* wrote ---...
How do we figure out the repo being read-only (which I'm guessing has to do with some ownership issues in the gitlab config)?
---- On Fri, 27 Dec 2024 17:50:41 -0500 Jon Boone mailto:ipmonger@delamancha.org wrote ---
David,
I'm wondering if this is perhaps also related:
I tried to pull the latest updates from the cmucl/cmucl repo and received this message:
remote: You (@jboone) must accept the Terms of Service in order to perform this action. To accept these terms, please access GitLab from a web browser at https://gitlab.common-lisp.net.
But, when I navigate to https://gitlab.common-lisp.net in my web browser and login, I don't see any prompts to accept the Terms of Service as outstanding....
I just temporarily turned off the requirement to accept T&S - please see if that makes a difference (for you and/or Raymond).
Not for me - same error message.
—jon
On Fri, Dec 27, 2024 at 6:18 PM David Cooper david.cooper@genworks.com wrote:
---- On Fri, 27 Dec 2024 17:50:41 -0500 *Jon Boone <ipmonger@delamancha.org ipmonger@delamancha.org>* wrote ---
David,
I'm wondering if this is perhaps also related:
I tried to pull the latest updates from the cmucl/cmucl repo and received this message:
remote: You (@jboone) must accept the Terms of Service in order to perform this action. To accept these terms, please access GitLab from a web browser at https://gitlab.common-lisp.net.
But, when I navigate to https://gitlab.common-lisp.net in my web browser and login, I don't see any prompts to accept the Terms of Service as outstanding....
I just temporarily turned off the requirement to accept T&S - please see if that makes a difference (for you and/or Raymond).
Just did a `sudo gitlab-ctl reconfigure` and rebooted the host.
Please try again in a few minutes.
Dave Cooper
---- On Fri, 27 Dec 2024 18:20:40 -0500 Jon Boone ipmonger@delamancha.org wrote ---
Not for me - same error message.
—jon
On Fri, Dec 27, 2024 at 6:18 PM David Cooper mailto:david.cooper@genworks.com wrote:
---- On Fri, 27 Dec 2024 17:50:41 -0500 Jon Boone mailto:ipmonger@delamancha.org wrote ---
David,
I'm wondering if this is perhaps also related:
I tried to pull the latest updates from the cmucl/cmucl repo and received this message:
remote: You (@jboone) must accept the Terms of Service in order to perform this action. To accept these terms, please access GitLab from a web browser at https://gitlab.common-lisp.net.
But, when I navigate to https://gitlab.common-lisp.net in my web browser and login, I don't see any prompts to accept the Terms of Service as outstanding....
I just temporarily turned off the requirement to accept T&S - please see if that makes a difference (for you and/or Raymond).
And maybe sign out & sign back in to the web UI (the signing page now simply states that "by signing in your accept the T of S and privacy policy..." )
Dave Cooper
---- On Fri, 27 Dec 2024 18:23:29 -0500 David Cooper david.cooper@genworks.com wrote ---
Just did a `sudo gitlab-ctl reconfigure` and rebooted the host.
Please try again in a few minutes.
Dave Cooper
---- On Fri, 27 Dec 2024 18:20:40 -0500 Jon Boone mailto:ipmonger@delamancha.org wrote ---
Not for me - same error message.
Jon,
Your gitlab user jboone has just been elevated to Administrator status, in case you'd like to fiddle around with any settings. I may be away from keyboard for the next couple hours.
Dave Cooper
Just noticed that the port 22 rule went missing from the nftables inputRules chain.
I guess whatever I did failed to make it persistent.
Just edited /etc/nftables.conf and rebooted, let's see what happens. Port 22 being blocked certainly would explain inablity to push/pull...
Dave Cooper
---- On Fri, 27 Dec 2024 18:42:55 -0500 David Cooper david.cooper@genworks.com wrote ---
Jon,
Your gitlab user jboone has just been elevated to Administrator status, in case you'd like to fiddle around with any settings. I may be away from keyboard for the next couple hours.
Dave Cooper
I am able to pull, but i'm replicating the "The repository is temporarily read-only. Please try again later."
This may be a setting which was done on the old host before final backup and got carried into the new host through the restore. Looking into it...
Dave Cooper
---- On Fri, 27 Dec 2024 18:55:07 -0500 David Cooper david.cooper@genworks.com wrote ---
Just noticed that the port 22 rule went missing from the nftables inputRules chain.
I guess whatever I did failed to make it persistent.
Just edited /etc/nftables.conf and rebooted, let's see what happens. Port 22 being blocked certainly would explain inablity to push/pull...
Dave Cooper
Indeed all the repos had been set to read-only and were still stuck that way after restore.
I've just reverted them to read_only: false, so please try again.
Dave Cooper
---- On Fri, 27 Dec 2024 18:58:11 -0500 David Cooper david.cooper@genworks.com wrote ---
I am able to pull, but i'm replicating the "The repository is temporarily read-only. Please try again later."
This may be a setting which was done on the old host before final backup and got carried into the new host through the restore. Looking into it...
Dave Cooper
---- On Fri, 27 Dec 2024 18:55:07 -0500 David Cooper mailto:david.cooper@genworks.com wrote ---
Just noticed that the port 22 rule went missing from the nftables inputRules chain.
I guess whatever I did failed to make it persistent.
Just edited /etc/nftables.conf and rebooted, let's see what happens. Port 22 being blocked certainly would explain inablity to push/pull...
Dave Cooper
On Fri, Dec 27, 2024 at 4:04 PM David Cooper david.cooper@genworks.com wrote:
Indeed all the repos had been set to read-only and were still stuck that way after restore.
I've just reverted them to read_only: false, so please try again.
I can pull, but can't push. And now I can't reach gitlab.c-l.net anymore; I'm unable to connect again.
Dave Cooper
---- On Fri, 27 Dec 2024 18:58:11 -0500 *David Cooper <david.cooper@genworks.com david.cooper@genworks.com>* wrote ---
I am able to pull, but i'm replicating the "The repository is temporarily read-only. Please try again later."
This may be a setting which was done on the old host before final backup and got carried into the new host through the restore. Looking into it...
Dave Cooper
---- On Fri, 27 Dec 2024 18:55:07 -0500 *David Cooper <david.cooper@genworks.com david.cooper@genworks.com>* wrote ---
Just noticed that the port 22 rule went missing from the nftables inputRules chain.
I guess whatever I did failed to make it persistent.
Just edited /etc/nftables.conf and rebooted, let's see what happens. Port 22 being blocked certainly would explain inablity to push/pull...
Dave Cooper
On Fri, Dec 27, 2024 at 2:30 PM David Cooper david.cooper@genworks.com wrote:
Hi Raymond,
You might need to add your ed25519 public key to here: SSH Keys · User Settings · GitLab https://gitlab.common-lisp.net/-/user_settings/ssh_keys
Make sure the same one which is in your .ssh/authorized_keys and which you know is the one letting you ssh in, is also added to that list in the gitlab UI. I think your "rtoy" gitlab user and your "rtoy" shell login account are treated as two different things so the requisite public key has to be in both places.
I checked and they match. Perhaps the issue is that the key starts with
ssh-rsa but is really ed25519?
I'm pretty sure I didn't edit that and ssh-keygen long ago did that. But it was a long time ago.
Dave Cooper
---- On Thu, 26 Dec 2024 17:41:05 -0500 toy.raymond@gmail.com wrote ----
Can you ssh to gitlab.common-lisp.net ?
It might not accept older rsa keys, i.e.you might need to generate new stronger e.g. ed25519 keys (I'm not gonna go snooping around your .ssh directory unless I need to). If so, send me your new public key and I'll add it to your .ssh/authorized_keys on the new host.
On Thu, Dec 26, 2024 at 12:53 PM David Cooper david.cooper@genworks.com 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 toy.raymond@gmail.com wrote ----
On Thu, Dec 26, 2024 at 8:54 AM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com 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
​
--
Ray
--
Ray
On Thu, Dec 26, 2024 at 3:19 PM David Cooper david.cooper@genworks.com wrote:
Dave Cooper
---- On Thu, 26 Dec 2024 17:41:05 -0500 * toy.raymond@gmail.com toy.raymond@gmail.com * wrote ----
Can you ssh to gitlab.common-lisp.net ?
It might not accept older rsa keys, i.e.you might need to generate new stronger e.g. ed25519 keys (I'm not gonna go snooping around your .ssh directory unless I need to). If so, send me your new public key and I'll add it to your .ssh/authorized_keys on the new host.
Hmm. I can't ssh to gitlab.common-lisp.net. I don't think I've ever tried that before. I still have my old rsa key, but I also switched to ed25519 keys quite a while ago and that's what I use for ssh now.
On Thu, Dec 26, 2024 at 12:53 PM David Cooper david.cooper@genworks.com 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 * toy.raymond@gmail.com toy.raymond@gmail.com * wrote ----
On Thu, Dec 26, 2024 at 8:54 AM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com 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
​
-- Ray
-- Ray
Hi again Raymond,
Sorry for your frustrations, and this next one is on us for sure: as a security measure, we had updated the ssh port from the standard port 22 to the arbitrary 4022. I'm changing it back to standard 22 now.
And as you have both a shell login account and Gitlab account, you probably have to add your ed25519 public key both in the .ssh/ directory and .ssh/authorized_keys file, as we ll as pasting into your Gitlab profile through the gitlab web ui (after you can access that), to enable both shell login and git push/pull. Presumably you already have your ed25519 public key pasted into gitlab, but you can confirm that as soon as you can access the website.
As an example, here is my .ssh/config for the new host:
```
Host future future.common-lisp.net gitlab.common-lisp.net git.common-lisp.net gi\
tlab-future.common-lisp.net
Hostname gitlab.common-lisp.net
AddKeysToAgent yes
IdentityFile ~/.ssh/id_ed_github
User dcooper
PubkeyAcceptedKeyTypes=ssh-ed25519
```
Please wait a few minutes while I change the port back to the standard 22.
Dave Cooper
---- On Thu, 26 Dec 2024 18:34:32 -0500 Raymond Toy toy.raymond@gmail.com wrote ---
On Thu, Dec 26, 2024 at 3:19 PM David Cooper mailto:david.cooper@genworks.com wrote:
Dave Cooper
---- On Thu, 26 Dec 2024 17:41:05 -0500 mailto:toy.raymond@gmail.com wrote ----
Can you ssh to http://gitlab.common-lisp.net ?
It might not accept older rsa keys, i.e.you might need to generate new stronger e.g. ed25519 keys (I'm not gonna go snooping around your .ssh directory unless I need to). If so, send me your new public key and I'll add it to your .ssh/authorized_keys on the new host.
Hmm. I can't ssh to http://gitlab.common-lisp.net.%C2%A0 I don't think I've ever tried that before. I still have my old rsa key, but I also switched to ed25519 keys quite a while ago and that's what I use for ssh now.
On Thu, Dec 26, 2024 at 12:53 PM David Cooper mailto:david.cooper@genworks.com wrote:
Note that the DNS for http://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 http://gitlab.common-lisp.net just fine:
```
64 bytes from http://future.common-lisp.net (65.108.13.229)
```
So you may need to clear your DNS caches (browsers and OS).
The toplevel http://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 http://future.common-lisp.net or http://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 mailto:toy.raymond@gmail.com wrote ----
On Thu, Dec 26, 2024 at 8:54 AM Jon Boone mailto:ipmonger@delamancha.org 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 http://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 mailto:toy.raymond@gmail.com 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 reachhttp://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
Dear Raymond (and all concerned),
I'm having trouble switching the sshd service back to port 22, and I have to give up on it for a little while.
If anyone is available to help with this let me know.
In the meantime the sshd is on port 4022 and your .ssh/config will need to be configured accordingly. Here is mind for example:
``` Host future future.common-lisp.net gitlab.common-lisp.net git.common-lisp.net gi\
tlab-future.common-lisp.net
Hostname gitlab.common-lisp.net
AddKeysToAgent yes
IdentityFile ~/.ssh/id_ed_github
User dcooper Port 4022 PubkeyAcceptedKeyTypes=ssh-ed25519
```
What I tried on the server:
1. Added ACCEPT rule to the firewall (nftables with iptables frontend) for port 22.
2. Edited /etc/ssh/sshd_config.d/local.conf and changed Port to 22
3. Confirmed with `sudo netstat -tulpn | grep 22` that sshd was listening on port 22
4. Updated my home .ssh/config to comment out the Port 4022
5. Tried ssh from home - did not work (timed out).
For fear of locking myself out of the server, I set it back to 4022 for now, confirmed I could log in, then rebooted the machine to make sure the firewall and fail2ban are active again.
Dave Cooper
---- On Thu, 26 Dec 2024 19:48:45 -0500 David Cooper david.cooper@genworks.com wrote ---
Hi again Raymond,
Sorry for your frustrations, and this next one is on us for sure: as a security measure, we had updated the ssh port from the standard port 22 to the arbitrary 4022. I'm changing it back to standard 22 now.
And as you have both a shell login account and Gitlab account, you probably have to add your ed25519 public key both in the .ssh/ directory and .ssh/authorized_keys file, as we ll as pasting into your Gitlab profile through the gitlab web ui (after you can access that), to enable both shell login and git push/pull. Presumably you already have your ed25519 public key pasted into gitlab, but you can confirm that as soon as you can access the website.
As an example, here is my .ssh/config for the new host:
```
Host future future.common-lisp.net gitlab.common-lisp.net git.common-lisp.net gi\
tlab-future.common-lisp.net
Hostname gitlab.common-lisp.net
AddKeysToAgent yes
IdentityFile ~/.ssh/id_ed_github
User dcooper
PubkeyAcceptedKeyTypes=ssh-ed25519
```
Please wait a few minutes while I change the port back to the standard 22.
Dave Cooper
---- On Thu, 26 Dec 2024 18:34:32 -0500 Raymond Toy mailto:toy.raymond@gmail.com wrote ---
On Thu, Dec 26, 2024 at 3:19 PM David Cooper mailto:david.cooper@genworks.com wrote:
Dave Cooper
---- On Thu, 26 Dec 2024 17:41:05 -0500 mailto:toy.raymond@gmail.com wrote ----
Can you ssh to http://gitlab.common-lisp.net ?
It might not accept older rsa keys, i.e.you might need to generate new stronger e.g. ed25519 keys (I'm not gonna go snooping around your .ssh directory unless I need to). If so, send me your new public key and I'll add it to your .ssh/authorized_keys on the new host.
Hmm. I can't ssh to http://gitlab.common-lisp.net.%C2%A0 I don't think I've ever tried that before. I still have my old rsa key, but I also switched to ed25519 keys quite a while ago and that's what I use for ssh now.
On Thu, Dec 26, 2024 at 12:53 PM David Cooper mailto:david.cooper@genworks.com wrote:
Note that the DNS for http://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 http://gitlab.common-lisp.net just fine:
```
64 bytes from http://future.common-lisp.net (65.108.13.229)
```
So you may need to clear your DNS caches (browsers and OS).
The toplevel http://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 http://future.common-lisp.net or http://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 mailto:toy.raymond@gmail.com wrote ----
On Thu, Dec 26, 2024 at 8:54 AM Jon Boone mailto:ipmonger@delamancha.org 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 http://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 mailto:toy.raymond@gmail.com 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 reachhttp://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
David,
I can try to assist you if you want to continue working on this tonight or tomorrow. Here's my public key for user jboone@gitlab.common-lisp.net
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIBqwjwchMCU4S9OrgbkbJuZh7i6ObH31LO0poUaCd4h6
but I don't think I have an ssh login setup.
—jon
On Thu, Dec 26, 2024 at 8:25 PM David Cooper david.cooper@genworks.com wrote:
Dear Raymond (and all concerned),
I'm having trouble switching the sshd service back to port 22, and I have to give up on it for a little while.
If anyone is available to help with this let me know.
In the meantime the sshd is on port 4022 and your .ssh/config will need to be configured accordingly. Here is mind for example:
Host future future.common-lisp.net gitlab.common-lisp.net git.common-lisp.net gi\ tlab-future.common-lisp.net Hostname gitlab.common-lisp.net AddKeysToAgent yes IdentityFile ~/.ssh/id_ed_github User dcooper Port 4022 PubkeyAcceptedKeyTypes=ssh-ed25519What I tried on the server:
- Added ACCEPT rule to the firewall (nftables with iptables frontend)
for port 22.
Edited /etc/ssh/sshd_config.d/local.conf and changed Port to 22
Confirmed with `sudo netstat -tulpn | grep 22` that sshd was
listening on port 22
Updated my home .ssh/config to comment out the Port 4022
Tried ssh from home - did not work (timed out).
For fear of locking myself out of the server, I set it back to 4022 for now, confirmed I could log in, then rebooted the machine to make sure the firewall and fail2ban are active again.
Dave Cooper
---- On Thu, 26 Dec 2024 19:48:45 -0500 *David Cooper <david.cooper@genworks.com david.cooper@genworks.com>* wrote ---
Hi again Raymond,
Sorry for your frustrations, and this next one is on us for sure: as a security measure, we had updated the ssh port from the standard port 22 to the arbitrary 4022. I'm changing it back to standard 22 now.
And as you have both a shell login account and Gitlab account, you probably have to add your ed25519 public key both in the .ssh/ directory and .ssh/authorized_keys file, as we ll as pasting into your Gitlab profile through the gitlab web ui (after you can access that), to enable both shell login and git push/pull. Presumably you already have your ed25519 public key pasted into gitlab, but you can confirm that as soon as you can access the website.
As an example, here is my .ssh/config for the new host:
Host future future.common-lisp.net gitlab.common-lisp.net git.common-lisp.net gi\ tlab-future.common-lisp.net Hostname gitlab.common-lisp.net AddKeysToAgent yes IdentityFile ~/.ssh/id_ed_github User dcooper PubkeyAcceptedKeyTypes=ssh-ed25519Please wait a few minutes while I change the port back to the standard 22.
Dave Cooper
---- On Thu, 26 Dec 2024 18:34:32 -0500 *Raymond Toy <toy.raymond@gmail.com toy.raymond@gmail.com>* wrote ---
On Thu, Dec 26, 2024 at 3:19 PM David Cooper david.cooper@genworks.com wrote:
Dave Cooper
---- On Thu, 26 Dec 2024 17:41:05 -0500* toy.raymond@gmail.com toy.raymond@gmail.com * wrote ----
Can you ssh to gitlab.common-lisp.net ?
It might not accept older rsa keys, i.e.you might need to generate new stronger e.g. ed25519 keys (I'm not gonna go snooping around your .ssh directory unless I need to). If so, send me your new public key and I'll add it to your .ssh/authorized_keys on the new host.
Hmm. I can't ssh to gitlab.common-lisp.net. I don't think I've ever tried that before. I still have my old rsa key, but I also switched to ed25519 keys quite a while ago and that's what I use for ssh now.
On Thu, Dec 26, 2024 at 12:53 PM David Cooper david.cooper@genworks.com 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* toy.raymond@gmail.com toy.raymond@gmail.com * wrote ----
On Thu, Dec 26, 2024 at 8:54 AM Jon Boone ipmonger@delamancha.org 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 toy.raymond@gmail.com 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 reachgitlab.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
​
--
Ray
--
Ray
--
Ray
Hi Jon,
Ok, i'll make you an account on the new host with sudo. Give me a few minutes.
Dave Cooper
---- On Thu, 26 Dec 2024 21:12:40 -0500 Jon Boone ipmonger@delamancha.org wrote ---
David,
I can try to assist you if you want to continue working on this tonight or tomorrow. Here's my public key for user mailto:jboone@gitlab.common-lisp.net
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIBqwjwchMCU4S9OrgbkbJuZh7i6ObH31LO0poUaCd4h6
but I don't think I have an ssh login setup.
—jon
On Thu, Dec 26, 2024 at 8:25 PM David Cooper mailto:david.cooper@genworks.com wrote:
Dear Raymond (and all concerned),
I'm having trouble switching the sshd service back to port 22, and I have to give up on it for a little while.
If anyone is available to help with this let me know.
In the meantime the sshd is on port 4022 and your .ssh/config will need to be configured accordingly. Here is mind for example:
```
Host future http://future.common-lisp.net http://gitlab.common-lisp.net http://git.common-lisp.net gi\
http://tlab-future.common-lisp.net
Hostname http://gitlab.common-lisp.net
AddKeysToAgent yes
IdentityFile ~/.ssh/id_ed_github
User dcooper Port 4022 PubkeyAcceptedKeyTypes=ssh-ed25519
```
What I tried on the server:
1. Added ACCEPT rule to the firewall (nftables with iptables frontend) for port 22.
2. Edited /etc/ssh/sshd_config.d/local.conf and changed Port to 22
3. Confirmed with `sudo netstat -tulpn | grep 22` that sshd was listening on port 22
4. Updated my home .ssh/config to comment out the Port 4022
5. Tried ssh from home - did not work (timed out).
For fear of locking myself out of the server, I set it back to 4022 for now, confirmed I could log in, then rebooted the machine to make sure the firewall and fail2ban are active again.
Dave Cooper
---- On Thu, 26 Dec 2024 19:48:45 -0500 David Cooper mailto:david.cooper@genworks.com wrote ---
Hi again Raymond,
Sorry for your frustrations, and this next one is on us for sure: as a security measure, we had updated the ssh port from the standard port 22 to the arbitrary 4022. I'm changing it back to standard 22 now.
And as you have both a shell login account and Gitlab account, you probably have to add your ed25519 public key both in the .ssh/ directory and .ssh/authorized_keys file, as we ll as pasting into your Gitlab profile through the gitlab web ui (after you can access that), to enable both shell login and git push/pull. Presumably you already have your ed25519 public key pasted into gitlab, but you can confirm that as soon as you can access the website.
As an example, here is my .ssh/config for the new host:
```
Host future http://future.common-lisp.net http://gitlab.common-lisp.net http://git.common-lisp.net gi\
http://tlab-future.common-lisp.net
Hostname http://gitlab.common-lisp.net
AddKeysToAgent yes
IdentityFile ~/.ssh/id_ed_github
User dcooper
PubkeyAcceptedKeyTypes=ssh-ed25519
```
Please wait a few minutes while I change the port back to the standard 22.
Dave Cooper
---- On Thu, 26 Dec 2024 18:34:32 -0500 Raymond Toy mailto:toy.raymond@gmail.com wrote ---
On Thu, Dec 26, 2024 at 3:19 PM David Cooper mailto:david.cooper@genworks.com wrote:
Dave Cooper
---- On Thu, 26 Dec 2024 17:41:05 -0500 mailto:toy.raymond@gmail.com wrote ----
Can you ssh to http://gitlab.common-lisp.net ?
It might not accept older rsa keys, i.e.you might need to generate new stronger e.g. ed25519 keys (I'm not gonna go snooping around your .ssh directory unless I need to). If so, send me your new public key and I'll add it to your .ssh/authorized_keys on the new host.
Hmm. I can't ssh to http://gitlab.common-lisp.net.%C2%A0 I don't think I've ever tried that before. I still have my old rsa key, but I also switched to ed25519 keys quite a while ago and that's what I use for ssh now.
On Thu, Dec 26, 2024 at 12:53 PM David Cooper mailto:david.cooper@genworks.com wrote:
Note that the DNS for http://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 http://gitlab.common-lisp.net just fine:
```
64 bytes from http://future.common-lisp.net (65.108.13.229)
```
So you may need to clear your DNS caches (browsers and OS).
The toplevel http://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 http://future.common-lisp.net or http://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 mailto:toy.raymond@gmail.com wrote ----
On Thu, Dec 26, 2024 at 8:54 AM Jon Boone mailto:ipmonger@delamancha.org 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 http://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 mailto:toy.raymond@gmail.com 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 reachhttp://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
-
Dave Cooper -
David Cooper -
Georgiy Tugai -
Jon Boone -
Raymond Toy -
Robert Goldman