[03:01:47] !log admin restarting eqiad1 openstack services in response to some fullstack failures [03:01:53] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Admin/SAL [09:26:53] https://pastebin.com/AzttBacy (re @jeremy_b: use a pastebin, add -v to ssh) [11:27:31] I have lost my toolforge account name username etc [11:46:20] if you cannot remember anything at all, then what to do, what to do? [13:10:08] Please I am tying to deploy a tool api and FE, for some reason the build works but the service seems not to be available on the web, can anyone help me out. Tool link https://wdtmcollab-api.toolforge.org/ [13:10:09] Using this documentation (https://wikitech.wikimedia.org/wiki/Help:Toolforge/Building_container_images) [13:13:15] hm, `kubectl logs wdtmcollab-api-597484645b-69lp6` says “Express is listening at http://127.0.0.1:8000” [13:13:21] but `kubectl get events` says e.g. “Startup probe failed: dial tcp 192.168.182.5:8000: connect: connection refused” [13:13:30] I wonder if your Express is listening on the wrong host? localhost instead of all hosts? [13:13:41] but maybe k8s is also mangling the IPs in some way. I’m not sure [13:41:49] I am also not sure why it does't work, I had this running 3 months ago, updated the code and want to make it available [14:13:58] as Lucas says, the server needs to listen on all interfaces (0.0.0.0) instead of on localhost only (127.0.0.1) [18:49:02] !log lucaswerkmeister@tools-bastion-15 tools.quickcategories deployed 68012a14ac (upgrade dependencies) [18:49:05] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.quickcategories/SAL [19:47:39] !log lucaswerkmeister@tools-bastion-15 tools.quickcategories deployed 7719b7b594 (refactor: kw-only param) [19:47:41] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.quickcategories/SAL [23:17:51] Hi! I haven't connected to the Toolforge servers in a while. I vaguely remember setting up SSH keys and all that back in December, then I made a Powershell path to connect with one click, but that has stopped working since a couple months ago. When I tried to connect today, the command line told me "WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!" [23:17:51] and told me to correct a "host key". I checked and the keys I have configured at toolsadmin still match the ones on my computer. Does someone have any idea what I could do to troubleshoot this? Thanks. [23:23:01] you can see the right host key at https://wikitech.wikimedia.org/wiki/Help:SSH_Fingerprints/login.toolforge.org [23:24:37] and the error message hopefully includes instructions for what to do if the host key genuinely changed (on a Linux system I think it says something like “delete line X from your ~/.ssh/known_hosts” but idk about windows / powershell) [23:25:35] (and maybe just use the path/get the donation from some trusted place like your bookmarks or just type `wikitech:` in Wikipedia search box. and then check to make sure page is protected.) (re @lucaswerkmeister: you can see the right host key at https://wikitech.wikimedia.org/wiki/Help:SSH_Fingerprints/login.toolforge.org) [23:26:40] Yeah, it did say that there was a problem with my "known_hosts", so I deleted that, and now it isn't giving me that dramatic an error. I tried to connect and it said. My publickey file does match what's on toolsadmin, so I don't know what's up. [23:26:41] The authenticity of host 'login.toolforge.org (2a02:ec80:a000:1::1c5)' can't be established. [23:26:41] ED25519 key fingerprint is SHA256:0i1eqK9uOYmCjOe5a0oAWTmnEPUh0b7h2Flm1IDl0sg. [23:26:42] This key is not known by any other names. [23:26:42] Are you sure you want to continue connecting (yes/no/[fingerprint])? yes [23:26:43] Warning: Permanently added 'login.toolforge.org' (ED25519) to the list of known hosts. [23:26:43] PolomoBrasil@login.toolforge.org: Permission denied (publickey). [23:27:47] is the username in your last message correct? [23:27:58] capitalisation is word [23:28:08] weird* [23:28:36] Right, it's been a while and I guess I misread the help page. using lowercase made it connect, lol. [23:29:10] I guess that was it. Everything's working as it did before, now. Thank you both.