Thanks, Cameron D, for the reply. I have attached two files with the results of the commands you suggested. Does this help explain what is going on?
On the positive side, the damn thing started working correctly and FTP seems to be working correctly. Since I was fiddling around with ports and keys I'm not sure what caused things to start properly. At the end of ssh -vv, it is asking for a password but I'm not sure which. There is no user pi on grattans.org. Now that* FTP is working again*, I'm going to try Vince's suggestion on switching to RSYNC. Much appreciated for everyone's help on this! Cheers, Bob On Thursday, May 14, 2026 at 2:58:20 AM UTC-4 Cameron D wrote: > Being able to ssh from a local windows pc but not the pi sounds like a > firewall problem. > What does > sudo traceroute -T -q 1 -p 22 grattans.org > tell you? > If it shows only one or two lines then your local system is blocking you. > > If it shows a reply from your remote host, that means the ssh server is > listening, so then try > ssh -vv grattans.org > You should see a pile of info about key exchanges > > By the way, to access remote ssh servers from home you do not need any > ports open on your router - that is only to permit remote access *into *your > home. If you don't need them then they should be closed. > On Thursday, 14 May 2026 at 6:42:01 am UTC+10 [email protected] wrote: > >> Ok, here is where I am so far today. >> >> I have checked with godaddy and they say everything is normal with my web >> site. I did this scan: >> >> grattans.org (107.180.54.252) >> - Port #22 (ssh): listening >> - Port #21 (ftp): listening >> - Port #25 (smtp): listening >> - Port #80 (http): listening >> - Port #110 (pop3): listening >> - Port #143 (imap): listening >> - Port #443 (https): listening >> - Port #993 (imaps): listening >> - Port #995 (pop3s): listening >> - Port #3306 (mysql): listening >> >> I did a port scan of my home address as I appear on the Inet: >> >> 100.70.65.73 (my home Inet address) >> - Port #20 (ftp-data): listening >> - Port #22 (ssh): listening >> - Port #21 (ftp): listening >> - Port #443 (https): listening >> >> On my LAN (192.168.1.x) I am able to ssh and ftp to my 3 win11 and 3 >> Linux machines, back and forth. >> >> I am able to run Filezilla on the LAN on win11 and Linux machines, back >> and forth. >> >> I am able to run Filezilla from win11 to grattans.org but NOT from the >> Linux machines. >> >> I can ssh to grattans.org from win11 but not from any of the Linux >> machines. >> >> For some reason unknown to me, grattans.org doesn't like ssh or ftp from >> Linux while it works from win11. >> >> Following Vince's good guide to RSYNC, I created the keys on my weewx >> server. Unable to ssh to grattans.org from that machine, >> I cut and pasted the following into grattans.org .ssh via win11 >> Filezilla. Not sure if this will work and haven't tried it yet. >> >> pi@rpi5trixie:~ $ ll .ssh >> total 16 >> -rw------- 1 pi pi 2602 May 12 14:04 id_rsa >> -rw-r--r-- 1 pi pi 567 May 12 14:04 id_rsa.pub >> -rw------- 1 pi pi 1120 May 12 17:17 known_hosts >> -rw-r--r-- 1 pi pi 142 Mar 7 16:57 known_hosts.old >> >> Hopefully this will make sense to someone as I am presently lost... >> Thanks in advance for any suggestions. >> >> Cheers, >> Bob >> >> >> >> On Tuesday, May 12, 2026 at 8:58:46 PM UTC-4 Jimi Lawson wrote: >> >>> >>> http is unreachable as well, from the UK I get >>> "The web page at *http://grattans.org/ <http://grattans.org/>* might be >>> temporarily down or it may have moved permanently to a new web address." >>> On Wednesday, 13 May 2026 at 01:43:16 UTC+1 [email protected] wrote: >>> >>>> It's time to have a beer (Stone IPA highly recommended). >>>> None of my Linux machines seem to want to ssh or ftp to each other >>>> (LAN) or outside (WAN) to grattans.org. Could it be some setting in >>>> the ASUS router? I haven't changed anything I'm aware of and it was >>>> working >>>> before. >>>> I will definitely try RSYNC tomorrow but I will need to be able to ssh >>>> to grattans.org to install a key. I'll sleep on it for now. >>>> Thanks everyone for the help so far. If you have any suggestions I'll >>>> try tomorrow. Much appreciated. >>>> Cheers, >>>> Bob >>>> >>>> >>>> On Tuesday, May 12, 2026 at 8:01:04 PM UTC-4 Vince Skahan wrote: >>>> >>>>> Bob it looks to me from here (US PNW) that your site 'is' responding >>>>> to ssh just fine. I of course don't have an account there so I can't log >>>>> in, but it looks like incoming ssh is ok FWIW. >>>>> >>>>> On Tuesday, May 12, 2026 at 4:53:30 PM UTC-7 John Smith wrote: >>>>> >>>>>> 20 is 'not' open from here >>>>>> >>>>>> >>>>>> It's been a few decades since I got rid of FTP but from memory it's >>>>>> only listened to once port 21 has been connected to and/or authenticated >>>>>> and there is a request to use it. >>>>>> >>>>>> On Wed, 13 May 2026 at 09:31, Vince Skahan <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> 20 is 'not' open from here, but it's been so many years since I had >>>>>>> to use ftp that I'm uncertain if it's needed or not. >>>>>>> >>>>>>> I see 22 (ssh) is open, so I'd still recommend trying to use the >>>>>>> RSYNC uploader. Hey - looks like there's a wiki article on how to do >>>>>>> that. >>>>>>> That wiki has a lot of stuff if you try to look for howtos there. >>>>>>> https://github.com/weewx/weewx/wiki/rsync-setup >>>>>>> >>>>>>> (big fan of the guy who wrote that page - big fan!) >>>>>>> >>>>>>> >>>>>>> On Tuesday, May 12, 2026 at 4:12:59 PM UTC-7 [email protected] wrote: >>>>>>> >>>>>>>> Didn't seem to help >>>>>>>> >>>>>>>> pi@rpi5trixie:~ $ sudo ufw status >>>>>>>> Status: active >>>>>>>> >>>>>>>> To Action From >>>>>>>> -- ------ ---- >>>>>>>> 22/tcp ALLOW Anywhere >>>>>>>> OpenSSH ALLOW Anywhere >>>>>>>> 21 ALLOW Anywhere >>>>>>>> 21/tcp ALLOW Anywhere >>>>>>>> 20/tcp ALLOW Anywhere >>>>>>>> >>>>>>>> 22/tcp (v6) ALLOW Anywhere (v6) >>>>>>>> OpenSSH (v6) ALLOW Anywhere (v6) >>>>>>>> 21 (v6) ALLOW Anywhere (v6) >>>>>>>> 21/tcp (v6) ALLOW Anywhere (v6) >>>>>>>> 20/tcp (v6) ALLOW Anywhere (v6) >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Tuesday, May 12, 2026 at 6:41:25 PM UTC-4 Vince Skahan wrote: >>>>>>>> >>>>>>>>> Try opening port 20 as a final test. >>>>>>>>> >>>>>>>>> >>>>>>>>> On Tuesday, May 12, 2026 at 3:31:45 PM UTC-7 [email protected] >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Well, so much for godaddy. They said their server checked out but >>>>>>>>>> they don't help with Linux problems. Not sure where to go. >>>>>>>>>> grattans.org should work with http:// no "https" >>>>>>>>>> >>>>>>>>>> I ran the following which might help: >>>>>>>>>> >>>>>>>>>> pi@rpi5trixie:~ $ sudo ufw status >>>>>>>>>> Status: active >>>>>>>>>> >>>>>>>>>> To Action From >>>>>>>>>> -- ------ ---- >>>>>>>>>> 22/tcp ALLOW Anywhere >>>>>>>>>> OpenSSH ALLOW Anywhere >>>>>>>>>> 21 ALLOW Anywhere >>>>>>>>>> 21/tcp ALLOW Anywhere >>>>>>>>>> 22/tcp (v6) ALLOW Anywhere (v6) >>>>>>>>>> OpenSSH (v6) ALLOW Anywhere (v6) >>>>>>>>>> 21 (v6) ALLOW Anywhere (v6) >>>>>>>>>> 21/tcp (v6) ALLOW Anywhere (v6) >>>>>>>>>> >>>>>>>>>> pi@rpi5trixie:~ $ nmap localhost -p 21 >>>>>>>>>> Starting Nmap 7.95 ( https://nmap.org ) at 2026-05-12 18:22 EDT >>>>>>>>>> Nmap scan report for localhost (127.0.0.1) >>>>>>>>>> Host is up (0.00012s latency). >>>>>>>>>> Other addresses for localhost (not scanned): ::1 >>>>>>>>>> >>>>>>>>>> PORT STATE SERVICE >>>>>>>>>> 21/tcp closed ftp >>>>>>>>>> >>>>>>>>>> Nmap done: 1 IP address (1 host up) scanned in 0.04 seconds >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Tuesday, May 12, 2026 at 4:10:37 PM UTC-4 Jimi Lawson wrote: >>>>>>>>>> >>>>>>>>>>> Your website https://www.grattans.org/ appears to be >>>>>>>>>>> unreachable by browser, (Chrome, Firefox & Opera) >>>>>>>>>>> Regards >>>>>>>>>>> Jimi >>>>>>>>>>> >>>>>>>>>>> On Tuesday, 12 May 2026 at 20:08:43 UTC+1 [email protected] wrote: >>>>>>>>>>> >>>>>>>>>>>> grattans.org is my web site hosted by godaddy. My weewx RPI5 >>>>>>>>>>>> uploaded the public_html files every 15 minutes. I'm going to call >>>>>>>>>>>> godaddy >>>>>>>>>>>> to see if they are blocking something. This has been working fine >>>>>>>>>>>> for over >>>>>>>>>>>> ten years. >>>>>>>>>>>> I'll get back once I talk with them. Thanks. >>>>>>>>>>>> >>>>>>>>>>>> On Tuesday, May 12, 2026 at 2:41:33 PM UTC-4 Vince Skahan wrote: >>>>>>>>>>>> >>>>>>>>>>>>> You're going to have to eventually describe your setup enough >>>>>>>>>>>>> for folks to help. What is 'grattans.org' ? Are you hosted >>>>>>>>>>>>> somewhere on Internet ? Where/by-whom ? Did your provider start >>>>>>>>>>>>> blocking >>>>>>>>>>>>> ftp ? >>>>>>>>>>>>> >>>>>>>>>>>>> Something ''there' is amiss. It's your ftp server side setup >>>>>>>>>>>>> definitely. >>>>>>>>>>>>> >>>>>>>>>>>>> On Tuesday, May 12, 2026 at 10:11:46 AM UTC-7 [email protected] >>>>>>>>>>>>> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Thanks for the reply, Karen. My Inet connection is ok and I >>>>>>>>>>>>>> can reach my site grattans.org using filezilla from other >>>>>>>>>>>>>> computers on my local network. From the weewx server I can ping >>>>>>>>>>>>>> grattans.org and I can use dig grattans.org to get the IP >>>>>>>>>>>>>> address. However on the weewx server when I enter FTP >>>>>>>>>>>>>> [email protected] it only hangs. Filezilla on the weewx >>>>>>>>>>>>>> server says it can't connect even though it connects from the >>>>>>>>>>>>>> other >>>>>>>>>>>>>> computers on the LAN. I'm not a programmer and can"t figure what >>>>>>>>>>>>>> is >>>>>>>>>>>>>> happening here. Weewx is working correctly except for FTP. >>>>>>>>>>>>>> Thanks >>>>>>>>>>>>>> Bob >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Tuesday, May 12, 2026 at 12:19:02 PM UTC-4 Karen K wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> The error message states "timeout". It happens during >>>>>>>>>>>>>>> connection initiation. So some possible reasons come into mind: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> - Internet access broken (Can you connect to servers in >>>>>>>>>>>>>>> the Internet?) >>>>>>>>>>>>>>> - DNS resolving broken (You can connect to servers by IP >>>>>>>>>>>>>>> but not by name.) >>>>>>>>>>>>>>> - passive/active FTP mode issues >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> First I would try to check the Internet connection. On the >>>>>>>>>>>>>>> console you could enter "ping www.ibm.com". You should get >>>>>>>>>>>>>>> answers from them. Then you can try the ftp command. If it >>>>>>>>>>>>>>> is not there, you can install it. Try then "ftp >>>>>>>>>>>>>>> your.webserver.com". Does that work? If not, it is not a >>>>>>>>>>>>>>> WeeWX but a system problem. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> [email protected] schrieb am Dienstag, 12. Mai 2026 um >>>>>>>>>>>>>>> 18:01:25 UTC+2: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I am running: weewx 5.3.1 on a Raspberry Pi 5 with >>>>>>>>>>>>>>>> Raspbian linux (Debian 13.x: Trixie), and Python version: >>>>>>>>>>>>>>>> 3.13.5. >>>>>>>>>>>>>>>> All was good but an OS update last night must have caused >>>>>>>>>>>>>>>> an FTP problem, maybe with a new version of python (?). Error >>>>>>>>>>>>>>>> from log file >>>>>>>>>>>>>>>> is attached. >>>>>>>>>>>>>>>> Davis VP2+ is running well but stopped FTPing to my website. >>>>>>>>>>>>>>>> Can anyone help with what is happening here? Thanks in >>>>>>>>>>>>>>>> advance. I can run with debug if needed. >>>>>>>>>>>>>>>> Bob >>>>>>>>>>>>>>>> grattans.org/wx >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -- >>>>>>> You received this message because you are subscribed to the Google >>>>>>> Groups "weewx-user" group. >>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>> send an email to [email protected]. >>>>>>> >>>>>> To view this discussion visit >>>>>>> https://groups.google.com/d/msgid/weewx-user/db9c1bde-c93a-42da-aaa1-a62b72dbc765n%40googlegroups.com >>>>>>> >>>>>>> <https://groups.google.com/d/msgid/weewx-user/db9c1bde-c93a-42da-aaa1-a62b72dbc765n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>> . >>>>>>> >>>>>> -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/weewx-user/1b193fd2-9e43-4942-9242-d6a119230210n%40googlegroups.com.
pi@rpi5trixie:~ $ sudo traceroute -T -q 1 -p 22 grattans.org traceroute to grattans.org (107.180.54.252), 30 hops max, 60 byte packets 1 192.168.1.1 (192.168.1.1) 0.326 ms 2 100.70.64.3 (100.70.64.3) 1.764 ms 3 10.70.128.226 (10.70.128.226) 2.244 ms 4 10.70.128.2 (10.70.128.2) 2.232 ms 5 10.70.128.6 (10.70.128.6) 5.226 ms 6 10.75.0.2 (10.75.0.2) 5.731 ms 7 10.75.0.6 (10.75.0.6) 8.202 ms 8 10.25.0.113 (10.25.0.113) 6.688 ms 9 eqix.dc.godaddy.com (206.126.236.43) 5.168 ms 10 eqix.dc.godaddy.com (206.126.236.43) 5.155 ms 11 ae20.phx3-ibrmb1205-02.bb.gdinf.net (148.72.36.115) 54.753 ms 12 ae2.phx3-pemc0215-01.bb.gdinf.net (148.72.32.67) 54.235 ms 13 * 14 * 15 * 16 * 17 * 18 * 19 * 20 * 21 * 22 * 23 252.54.180.107.host.secureserver.net (107.180.54.252) 54.574 ms
pi@rpi5trixie:~ $ ssh -vv grattans.org debug1: OpenSSH_10.0p2 Debian-7+deb13u2, OpenSSL 3.5.5 27 Jan 2026 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Reading configuration data /etc/ssh/ssh_config.d/20-systemd-ssh-proxy.conf debug1: /etc/ssh/ssh_config line 21: Applying options for * debug2: resolving "grattans.org" port 22 debug1: Connecting to grattans.org [107.180.54.252] port 22. debug1: Connection established. debug1: identity file /home/pi/.ssh/id_rsa type 0 debug1: identity file /home/pi/.ssh/id_rsa-cert type -1 debug1: identity file /home/pi/.ssh/id_ecdsa type -1 debug1: identity file /home/pi/.ssh/id_ecdsa-cert type -1 debug1: identity file /home/pi/.ssh/id_ecdsa_sk type -1 debug1: identity file /home/pi/.ssh/id_ecdsa_sk-cert type -1 debug1: identity file /home/pi/.ssh/id_ed25519 type -1 debug1: identity file /home/pi/.ssh/id_ed25519-cert type -1 debug1: identity file /home/pi/.ssh/id_ed25519_sk type -1 debug1: identity file /home/pi/.ssh/id_ed25519_sk-cert type -1 debug1: identity file /home/pi/.ssh/id_xmss type -1 debug1: identity file /home/pi/.ssh/id_xmss-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_10.0p2 Debian-7+deb13u2 debug1: Remote protocol version 2.0, remote software version OpenSSH_8.0 debug1: compat_banner: match: OpenSSH_8.0 pat OpenSSH* compat 0x04000000 debug2: fd 3 setting O_NONBLOCK debug1: Authenticating to grattans.org:22 as 'pi' debug1: load_hostkeys: fopen /home/pi/.ssh/known_hosts2: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug2: local client KEXINIT proposal debug2: KEX algorithms: mlkem768x25519-sha256,sntrup761x25519-sha512,[email protected],curve25519-sha256,[email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,ext-info-c,[email protected] debug2: host key algorithms: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,[email protected],[email protected],rsa-sha2-512,rsa-sha2-256 debug2: ciphers ctos: [email protected],[email protected],[email protected],aes128-ctr,aes192-ctr,aes256-ctr debug2: ciphers stoc: [email protected],[email protected],[email protected],aes128-ctr,aes192-ctr,aes256-ctr debug2: MACs ctos: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: MACs stoc: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: compression ctos: none,[email protected] debug2: compression stoc: none,[email protected] debug2: languages ctos: debug2: languages stoc: debug2: first_kex_follows 0 debug2: reserved 0 debug2: peer server KEXINIT proposal debug2: KEX algorithms: curve25519-sha256,[email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,[email protected] debug2: host key algorithms: rsa-sha2-512,rsa-sha2-256,ssh-rsa,[email protected],[email protected],[email protected],ecdsa-sha2-nistp256,[email protected],ssh-ed25519,[email protected] debug2: ciphers ctos: [email protected],[email protected],aes256-ctr,aes256-cbc,[email protected],aes128-ctr,aes128-cbc debug2: ciphers stoc: [email protected],[email protected],aes256-ctr,aes256-cbc,[email protected],aes128-ctr,aes128-cbc debug2: MACs ctos: [email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha1,[email protected],hmac-sha2-512 debug2: MACs stoc: [email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha1,[email protected],hmac-sha2-512 debug2: compression ctos: none,[email protected] debug2: compression stoc: none,[email protected] debug2: languages ctos: debug2: languages stoc: debug2: first_kex_follows 0 debug2: reserved 0 debug1: kex: algorithm: curve25519-sha256 debug1: kex: host key algorithm: [email protected] debug1: kex: server->client cipher: [email protected] MAC: <implicit> compression: none debug1: kex: client->server cipher: [email protected] MAC: <implicit> compression: none debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: SSH2_MSG_KEX_ECDH_REPLY received debug1: Server host certificate: [email protected] SHA256:zR0XfDOlCNCHOO2uGu8SePlxm3DLZ2FmBIljj5iqKEo, serial 0 ID "p3plzcpnl505867.prod.phx3.secureserver.net" CA ssh-rsa SHA256:/rQIvLr7xvz+/zIt0O2xP7rRFMu+0lLV1w1FJNQZRco valid forever debug2: Server host certificate hostname: 107.180.119.207 debug2: Server host certificate hostname: 107.180.57.39 debug2: Server host certificate hostname: 107.180.57.38 debug2: Server host certificate hostname: 107.180.54.252 debug2: Server host certificate hostname: p3plzcpnl505867 debug2: Server host certificate hostname: p3plzcpnl505867.prod.phx3.secureserver.net debug1: load_hostkeys: fopen /home/pi/.ssh/known_hosts2: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory debug1: No matching CA found. Retry with plain key debug1: Host 'grattans.org' is known and matches the ED25519 host key. debug1: Found key in /home/pi/.ssh/known_hosts:5 debug1: ssh_packet_send2_wrapped: resetting send seqnr 3 debug2: ssh_set_newkeys: mode 1 debug1: rekey out after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: ssh_packet_read_poll2: resetting read seqnr 3 debug1: SSH2_MSG_NEWKEYS received debug2: ssh_set_newkeys: mode 0 debug1: rekey in after 134217728 blocks debug2: KEX algorithms: mlkem768x25519-sha256,sntrup761x25519-sha512,[email protected],curve25519-sha256,[email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,ext-info-c,[email protected] debug2: host key algorithms: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,[email protected],[email protected],rsa-sha2-512,rsa-sha2-256 debug2: ciphers ctos: [email protected],[email protected],[email protected],aes128-ctr,aes192-ctr,aes256-ctr debug2: ciphers stoc: [email protected],[email protected],[email protected],aes128-ctr,aes192-ctr,aes256-ctr debug2: MACs ctos: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: MACs stoc: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: compression ctos: none,[email protected] debug2: compression stoc: none,[email protected] debug2: languages ctos: debug2: languages stoc: debug2: first_kex_follows 0 debug2: reserved 0 debug1: SSH2_MSG_EXT_INFO received debug1: kex_ext_info_client_parse: server-sig-algs=<ssh-ed25519,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521> debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,password debug1: Next authentication method: publickey debug1: Will attempt key: /home/pi/.ssh/id_rsa RSA SHA256:3BQDFx0H8FU0NM2vUxUL1/zSISLtI7xsKdIlNJcMRLE debug1: Will attempt key: /home/pi/.ssh/id_ecdsa debug1: Will attempt key: /home/pi/.ssh/id_ecdsa_sk debug1: Will attempt key: /home/pi/.ssh/id_ed25519 debug1: Will attempt key: /home/pi/.ssh/id_ed25519_sk debug1: Will attempt key: /home/pi/.ssh/id_xmss debug2: pubkey_prepare: done debug1: Offering public key: /home/pi/.ssh/id_rsa RSA SHA256:3BQDFx0H8FU0NM2vUxUL1/zSISLtI7xsKdIlNJcMRLE debug2: we sent a publickey packet, wait for reply debug1: Authentications that can continue: publickey,password debug1: Trying private key: /home/pi/.ssh/id_ecdsa debug1: Trying private key: /home/pi/.ssh/id_ecdsa_sk debug1: Trying private key: /home/pi/.ssh/id_ed25519 debug1: Trying private key: /home/pi/.ssh/id_ed25519_sk debug1: Trying private key: /home/pi/.ssh/id_xmss debug2: we did not send a packet, disable method debug1: Next authentication method: password [email protected]'s password:
