Issue from cubie/a7z/system-config/ssh-remote

[Infilux]

URL: https://docs.radxa.com/cubie/a7z/system-config/ssh-remote

Time: 1/12/2026, 3:46:38 PM

Cant able to establish SSH Connection between PC and Radxa Cubie A7Z. i followed step to create profile and also when i open ssh connection profile, it asks for password , when i put password "radxa", it shows authentication rejected. i tried different format too, but still same error.

[xzl01]

1. Please try to log in directly on the host using the username and password to confirm if it can bypass the SSH authentication issue.

2. Use the ip -a command to determine if the SBC's IP address is correct.

3. If SSH still cannot log in, please provide relevant log information.

[Infilux]

1. i have done login using serial port i.e using UART (USB-to-TTL module) and and create a serial port profile according to documentation and it's working properly. i am able to login into device. i think i password is changed from my side that i can't able to remember. can we somehow retrieve password?

C:\Users\PJ>ssh radxa@192.168.1.31
The authenticity of host '192.168.1.31 (192.168.1.31)' can't be established.
ED25519 key fingerprint is SHA256:r4GvDzLETU9XuBamTlLZWRSR2tnfg/AZRx00rtfXJNg.
This key is not known by any other names.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '192.168.1.31' (ED25519) to the list of known hosts.
radxa@192.168.1.31's password: 
Permission denied, please try again.
radxa@192.168.1.31's password: 
Permission denied, please try again.
radxa@192.168.1.31's password: 
radxa@192.168.1.31: Permission denied (publickey,password).

C:\Users\PJ>ssh radxa@192.168.1.31
radxa@192.168.1.31's password: 
Permission denied, please try again.
radxa@192.168.1.31's password: 
Permission denied, please try again.
radxa@192.168.1.31's password: 
radxa@192.168.1.31: Permission denied (publickey,password).

2. As i am using windows , there is command i am using "arp -a " to find ip address

C:\Users\PJ>arp -a
Interface: 192.168.1.18 --- 0xd
  Internet Address      Physical Address      Type
  192.168.1.1           6c-4f-89-b7-28-49     dynamic   
  192.168.1.10          ea-24-e7-0e-db-6f     dynamic   
  192.168.1.14          ac-f2-3c-63-0f-d3     dynamic   
  192.168.1.21          14-85-7f-b1-79-cf     dynamic   
  192.168.1.26          3e-ed-c9-dc-e1-d0     dynamic   
  192.168.1.31          a0-a4-c5-8a-79-a1     dynamic   <------ this 
  192.168.1.255         ff-ff-ff-ff-ff-ff     static    
  224.0.0.2             01-00-5e-00-00-02     static    
  224.0.0.22            01-00-5e-00-00-16     static    
  224.0.0.251           01-00-5e-00-00-fb     static    
  224.0.0.252           01-00-5e-00-00-fc     static    
  239.255.255.250       01-00-5e-7f-ff-fa     static    
  255.255.255.255       ff-ff-ff-ff-ff-ff     static    

Interface: 172.27.48.1 --- 0x3a
  Internet Address      Physical Address      Type
  172.27.63.255         ff-ff-ff-ff-ff-ff     static    
  224.0.0.2             01-00-5e-00-00-02     static    
  224.0.0.22            01-00-5e-00-00-16     static    
  224.0.0.251           01-00-5e-00-00-fb     static    
  239.255.255.250       01-00-5e-7f-ff-fa     static

[Infilux]

this is what i am getting when i put username : radxa and password : radxa

[xzl01]

Sorry, I couldn't reproduce your issue either. Since you can log in via USB-TTL, I suggest trying to log in with SSH keys. Run ssh-keygen on your computer to generate a key, then add the public key (the content of ~/.ssh/id_rsa.pub) to the device's ~/.ssh/authorized_keys, and try logging in without a password.

[Infilux]

i tried as per you share but it's still same issue. i add public key from pc ("C:\Users\PJ.ssh\id_ed25519.pub") to the device's ~/.ssh/authorized_keys

radxa@radxa:~$ ls -a /home/radxa/
.              .bashrc  Documents  Music     .ssh         .xsession-errors
..             .cache   Downloads  Pictures  Templates
.bash_history  .config  .kde       .profile  Videos
.bash_logout   Desktop  .local     Public    .Xauthority

radxa@radxa:~$ ls -a /home/radxa/.ssh/
.  ..  authorized_keys

[Infilux]

error.txt

these are logs while ssh

[Infilux]

Anyone?

[xzl01]

Perhaps you need to reset the SSH-related settings on the SBC or consider reinstalling the system. Something might be wrong, but based on the logs, I cannot obtain any useful information; it's just that SSH authentication was rejected.

[xzl01]

It's quite strange, I couldn't reproduce this issue on my device. Have you checked the logs for ssh.service on the SBC?

[Infilux]

It's quite strange, I couldn't reproduce this issue on my device. Have you checked the logs for ssh.service on the SBC?

radxa@radxa-cubie-a7z:~$ sudo systemctl status ssh
[sudo] password for radxa:

● ssh.service - OpenBSD Secure Shell server
     Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: e>
     Active: active (running) since Tue 2026-01-20 07:17:34 UTC; 1h 42min ago
       Docs: man:sshd(8)
             man:sshd_config(5)
    Process: 380 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS)
   Main PID: 403 (sshd)
      Tasks: 1 (limit: 1116)
     Memory: 3.7M
        CPU: 68ms
     CGroup: /system.slice/ssh.service
             └─403 sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups

Jan 20 07:17:34 radxa-cubie-a7z systemd[1]: Starting OpenBSD Secure Shell serve>
Jan 20 07:17:34 radxa-cubie-a7z sshd[403]: Server listening on 0.0.0.0 port 22.
Jan 20 07:17:34 radxa-cubie-a7z sshd[403]: Server listening on :: port 22.
Jan 20 07:17:34 radxa-cubie-a7z systemd[1]: Started OpenBSD Secure Shell server.

radxa@radxa-cubie-a7z:~$ sudo journalctl -u ssh
-- Journal begins at Thu 2025-06-26 00:44:53 UTC, ends at Tue 2026-01-20 09:00:>
Jun 26 00:45:19 radxa-cubie-a7z systemd[1]: Starting OpenBSD Secure Shell serve>
Jun 26 00:45:19 radxa-cubie-a7z sshd[1943]: Server listening on 0.0.0.0 port 22.
Jun 26 00:45:19 radxa-cubie-a7z sshd[1943]: Server listening on :: port 22.
Jun 26 00:45:19 radxa-cubie-a7z systemd[1]: Started OpenBSD Secure Shell server.
Jan 20 07:15:04 radxa-cubie-a7z systemd[1]: Stopping OpenBSD Secure Shell serve>
Jan 20 07:15:04 radxa-cubie-a7z systemd[1]: ssh.service: Succeeded.
Jan 20 07:15:04 radxa-cubie-a7z systemd[1]: Stopped OpenBSD Secure Shell server.
-- Boot 16a8f1b2912e40c889fc7d4823c3d7f0 --
Jan 20 07:15:27 radxa-cubie-a7z systemd[1]: Starting OpenBSD Secure Shell serve>
Jan 20 07:15:27 radxa-cubie-a7z sshd[410]: Server listening on 0.0.0.0 port 22.
Jan 20 07:15:27 radxa-cubie-a7z sshd[410]: Server listening on :: port 22.
Jan 20 07:15:27 radxa-cubie-a7z systemd[1]: Started OpenBSD Secure Shell server.
-- Boot 2fe5c5a0e0c44a158875934001d72681 --
Jan 20 07:17:34 radxa-cubie-a7z systemd[1]: Starting OpenBSD Secure Shell serve>
Jan 20 07:17:34 radxa-cubie-a7z sshd[403]: Server listening on 0.0.0.0 port 22.
Jan 20 07:17:34 radxa-cubie-a7z sshd[403]: Server listening on :: port 22.
Jan 20 07:17:34 radxa-cubie-a7z systemd[1]: Started OpenBSD Secure Shell server.

radxa@radxa-cubie-a7z:~$ sudo journalctl -u ssh -b
-- Journal begins at Thu 2025-06-26 00:44:53 UTC, ends at Tue 2026-01-20 09:00:>
Jan 20 07:17:34 radxa-cubie-a7z systemd[1]: Starting OpenBSD Secure Shell serve>
Jan 20 07:17:34 radxa-cubie-a7z sshd[403]: Server listening on 0.0.0.0 port 22.
Jan 20 07:17:34 radxa-cubie-a7z sshd[403]: Server listening on :: port 22.
Jan 20 07:17:34 radxa-cubie-a7z systemd[1]: Started OpenBSD Secure Shell server.

radxa@radxa-cubie-a7z:~$ sudo journalctl -u ssh -f
-- Journal begins at Thu 2025-06-26 00:44:53 UTC. --
Jan 20 07:15:04 radxa-cubie-a7z systemd[1]: ssh.service: Succeeded.
Jan 20 07:15:04 radxa-cubie-a7z systemd[1]: Stopped OpenBSD Secure Shell server.
-- Boot 16a8f1b2912e40c889fc7d4823c3d7f0 --
Jan 20 07:15:27 radxa-cubie-a7z systemd[1]: Starting OpenBSD Secure Shell server...
Jan 20 07:15:27 radxa-cubie-a7z sshd[410]: Server listening on 0.0.0.0 port 22.
Jan 20 07:15:27 radxa-cubie-a7z sshd[410]: Server listening on :: port 22.
Jan 20 07:15:27 radxa-cubie-a7z systemd[1]: Started OpenBSD Secure Shell server.
-- Boot 2fe5c5a0e0c44a158875934001d72681 --
Jan 20 07:17:34 radxa-cubie-a7z systemd[1]: Starting OpenBSD Secure Shell server...
Jan 20 07:17:34 radxa-cubie-a7z sshd[403]: Server listening on 0.0.0.0 port 22.
Jan 20 07:17:34 radxa-cubie-a7z sshd[403]: Server listening on :: port 22.
Jan 20 07:17:34 radxa-cubie-a7z systemd[1]: Started OpenBSD Secure Shell server.
^C

radxa@radxa-cubie-a7z:~$ sudo systemctl is-enabled ssh
sudo systemctl is-active ssh
enabled
active

[Infilux]

Perhaps you need to reset the SSH-related settings on the SBC or consider reinstalling the system. Something might be wrong, but based on the logs, I cannot obtain any useful information; it's just that SSH authentication was rejected.

i tried 3-4 times installing os on SD card but still go same issue... how can we reset SSH-related setting?

[Infilux]

i tried latest release from (https://github.com/radxa-build/radxa-a733/releases) still same issue. Also tried SSH new pair key but same o/p

[xzl01]

If you have tried multiple times, perhaps your Windows-side SSH is experiencing issues. Alternatively, you could try using WSL SSH to connect to the SBC?

[Infilux]

this is what i got when i try using WSL

pj@LAPTOP-BVD31Q97:~$ ssh radxa@192.168.1.31
The authenticity of host '192.168.1.31 (192.168.1.31)' can't be established.
ED25519 key fingerprint is SHA256:r4GvDzL..............
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])? y
Please type 'yes', 'no' or the fingerprint: yes
Warning: Permanently added '192.168.1.31' (ED25519) to the list of known hosts.
radxa@192.168.1.31's password:
Permission denied, please try again.
radxa@192.168.1.31's password:
Permission denied, please try again.
radxa@192.168.1.31's password:
radxa@192.168.1.31: Permission denied (publickey,password).

[xzl01]

Confirm whether your SBC's IP is correct and try using the ip -a command to check. If the IP address is correct, the issue might be elsewhere.