[06:05:36] HTTPS__AMC__117.23083238:3000/#5957359842539s/local_port=1.1.1w:2025-08-12T:05:07:29 [06:07:50] -connect:98e4d1229d869d73/kiwiirc.org [10:43:19] !log taavi@tools-bastion-14 tools.wikibugs toolforge jobs restart gerrit [10:43:24] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.wikibugs/SAL [11:45:14] !log tools update nfs-tools.wmcloud.org and nfs.svc.toolforge.org proxied to point to tools-nfs-3 [11:45:17] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL [12:30:21] !log lucaswerkmeister@tools-bastion-15 tools.phab-ban webservice restart # tool was seemingly down since yesterday because an error "Failed to resolve 'wikitech.wikimedia.org' ([Errno -3] Temporary failure in name resolution)" prevented the app from starting up [12:30:24] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.phab-ban/SAL [13:01:39] !log lucaswerkmeister-wmde@tools-bastion-15 tools.wdmm deployed 62ff80623d (more Commons village pumps) [13:01:40] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.wdmm/SAL [13:30:25] -connect__wikimedia.org/commons:main_page/wikibook_ZYGNET'CORE [13:32:08] !kb Guest53 [13:45:04] (did that permanently ban anyone who subsequently gets assigned Guest53 by libera’s web frontend or how does that work?) [13:45:41] it seems to be filtering by ip (though it's magic to me) [13:46:32] lucaswerkmeister: the ban is based on the real client ip, and I set that to expire in a week (via litharge) [14:06:16] I see, thanks! [15:31:27] i myself am not on windows but i have a colleague who is and he uses putty to connect to cloud instances. the change today to disable agent forwarding broke his workflow. what is the modern setup on windows, as mentioned in taavi's email? https://wikitech.wikimedia.org/wiki/Help:Accessing_Cloud_VPS_instances#Windows mentiones ssh agents, is that also forwarding? is there a way to use it without [15:31:33] forwarding? is there a way to use putty without forwarding? [15:36:37] Do toolforge web services support websockets? ingress-nginx will if it's new enough, but what about the HAProxy layer and the current timeouts or does implementing a (public) service with long lived connections require a WMCS instance? [15:39:30] gifti: the page you linked to has the instructions. it references running an agent on the local machine, which is a different thing than agent forwarding [15:39:40] Damianz: yes, should be supported [15:40:19] great, that makes things a lot simpler while un-tangling existing things [15:41:42] ah [15:57:14] i also found this: https://superuser.com/questions/1448180/how-to-setup-proxy-jump-with-putty [15:57:28] thx and bye! [23:36:20] looks like maybe https://openstack-browser.toolforge.org could use a restart or something? or there expected downtime right now? [23:47:27] AFAICT it’s basically working, just some views are slow. and AFAIK that’s normal [23:47:39] I don’t think restarting it (and probably wiping whichever caches it has) would help [23:47:56] it's working fine now :) Thanks!