On 12/28/24 5:46 AM, David Cooper wrote:

To clarify: we can forget port 4022 for now in any remote urls or client configs. There had been a dangling 4022 in the new gitlab config for ssh urls, but that is fixed now. So now, we are on the standard port 22, which does not need to be specified.

I’m back, and everything seems to be working fine again. I didn’t change anything after coming back, but the merge button works, I can push changes and ssh to gitlab.common-lisp.net on port 22.

And my VirtualBox runners are running.

Thanks to everyone for their hardwork in resolving this issue. And may the New Year be an uneventful year for all of the hard working people at c-l.net!