mbh can't login to Toolforge
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	MBH
	Mar 22 2025, 3:40 AM

Description

I'm using my key since 2015, but now can't log in. Error message (in Russian):

Протокол авторизации (подробности см. в журнале соединения:
Использую имя пользователя "mbh".
Аутентификация публичным ключом "rsa-key-20150704".
Аутентификация не пройдена.

error message (en auto translation)

Authorization protocol (see connection log for details):
I use the username "mbh".
Authentication with public key "rsa-key-20150704".
Authentication failed.

LDAP account Maxbiohazard (one of https://toolsadmin.wikimedia.org/tools/id/rv maintainers)

Related Objects

Mentioned Here: T389733: Increase RAM quota for mbh tool
T389717: dev.toolforge.org unreachable

Event Timeline

MBH created this task.Mar 22 2025, 3:40 AM

Restricted Application added a project: cloud-services-team. · View Herald TranscriptMar 22 2025, 3:40 AM

Restricted Application added subscribers: Base, Aklapper. · View Herald Transcript

Wellverywell subscribed.Mar 22 2025, 3:42 AM

Peachey88 updated the task description. (Show Details)Mar 22 2025, 4:35 AM

I also can't login from my phone, using TotalCommander with SFTP plugin, it worked correctly before.

Screenshot_20250322-113252_Total Commander.jpg (2×1 px, 196 KB)

MBH renamed this task from I can't login to Toolforge using WinSCP to mbh can't login to Toolforge.Mar 22 2025, 4:37 AM

When was the last time you were able to successfully signed in? I believe some of the older key signing types were removed a couple of months ago from memory.

Yesterday.

I assumed that problem may be in old key. I have generated a new RSA key using PuttyGEN and uploaded a public key to https://toolsadmin.wikimedia.org/profile/settings/ssh-keys/. I tried to log in using new key file and the problem persists.

Works now with an old keyfile. I'm not closing this task because maybe someone could explain what was this?

It could have been a temporary LDAP lookup failure. In Cloud VPS and by extension Toolforge the ssh public key information used to decide if your login was successful is stored in a OpenLDAP directory that is queried in real-time as you attempt to login via sshd. There were other LDAP issues seen in T389717: dev.toolforge.org unreachable a bit later in the same day.

I found some log messages that I think corroborate the temporary LDAP lookup failure theory:

root@tools-bastion-12:/var/log# zgrep -E '(Accepted|Failed) publickey for mbh' auth.log.3.gz
2025-03-22T01:25:31.926824+00:00 tools-bastion-12 sshd[1781555]: Accepted publickey for mbh from REDACTED_IP port 14604 ssh2: RSA SHA256:/CUr1MD2IX5gze3T4SL7FgKKwDyyNRVwPAaraoyFsjU
2025-03-22T02:50:26.380381+00:00 tools-bastion-12 sshd[1786152]: Failed publickey for mbh from REDACTED_IP port 50770 ssh2: RSA SHA256:/CUr1MD2IX5gze3T4SL7FgKKwDyyNRVwPAaraoyFsjU
2025-03-22T03:34:23.854893+00:00 tools-bastion-12 sshd[1787902]: Failed publickey for mbh from REDACTED_IP port 60140 ssh2: RSA SHA256:/CUr1MD2IX5gze3T4SL7FgKKwDyyNRVwPAaraoyFsjU
2025-03-22T03:34:41.046456+00:00 tools-bastion-12 sshd[1787908]: Failed publickey for mbh from REDACTED_IP port 34144 ssh2: RSA SHA256:/CUr1MD2IX5gze3T4SL7FgKKwDyyNRVwPAaraoyFsjU
2025-03-22T03:35:04.472018+00:00 tools-bastion-12 sshd[1787917]: Failed publickey for mbh from REDACTED_IP port 3715 ssh2: RSA SHA256:/CUr1MD2IX5gze3T4SL7FgKKwDyyNRVwPAaraoyFsjU
2025-03-22T03:36:20.043414+00:00 tools-bastion-12 sshd[1787956]: Failed publickey for mbh from REDACTED_IP port 3746 ssh2: RSA SHA256:/CUr1MD2IX5gze3T4SL7FgKKwDyyNRVwPAaraoyFsjU
2025-03-22T03:40:19.811249+00:00 tools-bastion-12 sshd[1788021]: Failed publickey for mbh from REDACTED_IP port 14322 ssh2: RSA SHA256:/CUr1MD2IX5gze3T4SL7FgKKwDyyNRVwPAaraoyFsjU
2025-03-22T04:32:46.091625+00:00 tools-bastion-12 sshd[1790963]: Failed publickey for mbh from REDACTED_IP port 36698 ssh2: RSA SHA256:/CUr1MD2IX5gze3T4SL7FgKKwDyyNRVwPAaraoyFsjU
2025-03-22T04:33:11.241658+00:00 tools-bastion-12 sshd[1790973]: Failed publickey for mbh from REDACTED_IP port 36702 ssh2: RSA SHA256:/CUr1MD2IX5gze3T4SL7FgKKwDyyNRVwPAaraoyFsjU
2025-03-22T05:25:33.232140+00:00 tools-bastion-12 sshd[1793443]: Failed publickey for mbh from REDACTED_IP port 54053 ssh2: RSA SHA256:/CUr1MD2IX5gze3T4SL7FgKKwDyyNRVwPAaraoyFsjU
2025-03-22T05:26:00.651948+00:00 tools-bastion-12 sshd[1793448]: Failed publickey for mbh from REDACTED_IP port 38488 ssh2: RSA SHA256:/CUr1MD2IX5gze3T4SL7FgKKwDyyNRVwPAaraoyFsjU
2025-03-22T08:29:10.350110+00:00 tools-bastion-12 sshd[1800890]: Failed publickey for mbh from REDACTED_IP port 1369 ssh2: RSA SHA256:CPpDD7yLckT04gPvJxg7aecNXznQ27yQ4F/FRWe9W1s
2025-03-22T14:48:45.410020+00:00 tools-bastion-12 sshd[1822368]: Accepted publickey for mbh from REDACTED_IP port 14726 ssh2: RSA SHA256:/CUr1MD2IX5gze3T4SL7FgKKwDyyNRVwPAaraoyFsjU

There were some (extra) issues with ldap during the weekend yep, I think it's very likely related, I'd say we can close this and reopen if you see any new issues, or leave it open for a bit and close if you don't see any new issues. Whatever you prefer @MBH

We could close this, no problem.

Could you also see T389733?

This happens again, with the same error message.

Works now, but could it be fixed at all?

Please open another ticket in case of additional problems.

	F58893440: Screenshot_20250322-113252_Total Commander.jpg
	Mar 22 2025, 4:35 AM

mbh can't login to ToolforgeClosed, ResolvedPublicActions

Description

Related Objects

Event Timeline

mbh can't login to Toolforge
Closed, ResolvedPublic
Actions