You might try it again on 4022, because I've been messing it randomly over the past couple hours and you might have happened to try while I had it switched to 22 (and i was getting the same apparent hangs as you describe for 22 while it was switched to that).

There should definitely be connectivity on port 4022 - if you do for example

telnet gitlab.common-lisp.net 4022

you will get a connection and can type `GET /` (it will say "invalid ssh identification string" but this should prove that the basic connectivity is there).

Dave Cooper

---- On Thu, 26 Dec 2024 20:57:51 -0500 Raymond Toy <toy.raymond@gmail.com> wrote ---

On Thu, Dec 26, 2024 at 3:57 PM David Cooper <david.cooper@genworks.com> wrote:

I see three rsa and one dsa in your authorized_hosts, no ed25519.

I'll put your ed25519 one in if you can send it.
Weird. I just did `ssh-copy-id ~/.ssh/id_ed25519.pub rtoy@common-lisp.net ` and that said that all keys were skipped because they already exist. I don't know why but my ed25519.pub key starts with "ssh-rsa".

Also, maybe you need to update your .ssh/config with the name gitlab.common-lisp.net because previously you were logging in to the toplevel name (that will work for the new host as well when migration is complete, but in the interim you'll have to ssh to it as gitlab.common-lisp.net or its IP address).

I can't ssh to gitlab.common-lisp.net on either port 22 or 4022. Port 4022 says connection refused. Port 22 just seems to hang.

Haven't updated .ssh/config yet.

Dave Cooper