I first ran into this error after installing Solaris 10 on a Sun Ultra 60 that I had a while back, but I’ve recently ran into it again installing Solaris 10 on Proxmox:
Unable to negotiate with 192.168.1.95 port 22: no matching key exchange method found. Their offer: gss-group1-sha1-toWM5Slw5Ew8Mqkay+al2g==,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
The solution to configure my Mac to be able to use older key algorithms was a combination from here and answers on this post.
I edited my ~/.ssh/config and added a Host entry for the ip of my Solaris 10 instance, adding:
And now I can just ssh in as normal (no need for any additional params as shown in the first post, as the required options are configured in my .ssh/config.
I just installed and configured a GitLab Runner on a separate Ubuntu 22.04 server. Following tips here and here, I’ve started the runner with ‘sudo gitlab-runner start’ and I’ve verified the config with ‘sudo gitlab-runner verify’, but the GitLab server is still showing the ‘never contacted this instance’ error:
Following the troubleshooting steps here, I used journalctl to view the logs:
Oct 19 14:36:24 proxmox-ubuntu2204-server systemd[1]: Started GitLab Runner. Oct 19 14:36:25 proxmox-ubuntu2204-server gitlab-runner[1264]: FATAL: failed to get user home dir: $HOME is not defined Oct 19 14:36:25 proxmox-ubuntu2204-server systemd[1]: gitlab-runner.service: Main process exited, code=exited, status=1/FAILURE Oct 19 14:36:25 proxmox-ubuntu2204-server systemd[1]: gitlab-runner.service: Failed with result 'exit-code'.
To set a home dir for the gitlab-runner user, I checked /etc/passwd, found the line for gitlab-runner and it has an entry towards the end of the line for /home/gitlab-runner, so that seems ok.
Following tips here, I edited the service config with:
sudo systemctl edit gitlab-runner
which edits /etc/systemd/system/gitlab-runner.service.d/override.conf and added this section:
[Service] Environment="HOME=/home/gitlab-runner"
Restarted the service with:
sudo systemctl restart gitlab-runner
checked the logs again with jornalctl and now we’re up and running, and the runner is reported as available on the Runners page. Done!
Oct 19 14:51:48 proxmox-ubuntu2204-server gitlab-runner[1400]: Runtime platform arch=amd64 os=linux pid=1400 revision=66a723c3 version=17.5.0 Oct 19 14:51:48 proxmox-ubuntu2204-server gitlab-runner[1400]: Starting multi-runner from /etc/gitlab-runner/config.toml... builds=0 max_builds=0 Oct 19 14:51:48 proxmox-ubuntu2204-server gitlab-runner[1400]: Running in system-mode. Oct 19 14:51:48 proxmox-ubuntu2204-server gitlab-runner[1400]: Oct 19 14:51:48 proxmox-ubuntu2204-server gitlab-runner[1400]: Configuration loaded builds=0 max_builds=1
After setting up a self-hosted GitLab instance in a Proxmox LXC container using the Debian Turnkey GitLab template, the initial root user password didn’t seem to be what I set it to during install.
Assuming you can ssh into the instance, change the password of any user with: