Help talk:Access to Toolforge instances with PuTTY and WinSCP

Please review my edit

I just added a warning about file ownership when logged to Labs by WinSCP, it has been the cause of a personal newbye headhache. Please review my edit and convert it into a formally better statement if needed. --Alex brollo (talk) 11:30, 3 March 2014 (UTC)

Using keyboard-interactive authentication

how can i fix this problem, i can't login my account, any help?--Jarallah II (talk) 14:13, 1 August 2016 (UTC)

SFTP-Server setting does not work

seems sudo -u tools.PROJECT-NAME /usr/lib/sftp-server does not work and it gives "sudo: /user/lib/sftp-server: command not found". Setting "Standard" look good. — Preceding unsigned comment added by Xqt (talk • contribs) 13:54, 5 January 2022 (UTC)

@Xqt Looks like you have a typo in there? It should be /usr/lib/sftp-server, not /user/lib/sftp-server. Majavah (talk!) 14:02, 5 January 2022 (UTC)

Thanks for reply. I had /usr/lib/sftp-server and it failed. But it works after "Standard" access and replacing that line again the after the first connection.  @xqt 15:32, 5 January 2022 (UTC)

Bastion hosts

Portal:Toolforge/About Toolforge#How is Toolforge structured? says:

You can log in to Toolforge through a bastion host. There are two bastion hosts to choose from:

login.toolforge.org

user login to access tools interactively

dev.toolforge.org

functionally identical, please use this for heavy processing such as compiles

But Help:Access to Toolforge instances with PuTTY and WinSCP#How to set up PuTTY for direct access to your Toolforge account says to specify host names:

tools-login.wmflabs.org

tools-dev.wmflabs.org

Are these the same servers under their former brand names? Should I specify the new names login.toolforge.org and dev.toolforge.org instead? Will the old names still work? Does it matter? Thanks, Wbm1058 (talk) 17:06, 15 May 2022 (UTC)

Thanks Samtar for updating this. Wbm1058 (talk) 12:03, 15 September 2022 (UTC)