The translation is temporarily closed for contributions due to maintenance, please come back later.
English
you may have too many different ssh keys in your personal ssh configuration directory. Since the image does not have your key, try connecting with a password first using:
View the default firewall configuration:
Verify that `sshd` is running:
Verify Network Configuration
The sample above requires name resolution and a route to the internet. If your device is located on an isolated network, ping another host on your network.
The released images are configured to run an SSH server and accept outside connections. The default configuration allows root login if a password is set. This is a good reason to leave the root account locked. The default configuration also allows standard users to login and the user can then sudo if they were made an administrator as a member of the wheel group.
Received disconnect from 11.22.33.44 port 22:2: Too many authentication failures
Ping a known host:
Once the initial setup is complete, the serial console or HDMI monitor and USB keyboard are no longer required to access the device. The device can be left in a headless state and accessed remotely.
Network Access
More information on managing accounts, keys, and remote access can be found in the xref:user-guide.adoc[User Guide].
Information on adding support for specific devices can be found in the xref:user-guide.adoc[User Guide].
If this works, you can customize your ssh configuration to specify either this option or options to use a specific key once you have added your keys.
If receive a "Too many authentication failures" message such as:
Determine your IP address:
Configure Remote Access
Check that you have a default gateway:
Before removing the serial console or HDMI monitor and USB keyboard, verify network connectivity. The provided images default to obtaining network settings from a DHCP server.
Authentication Failures
$ systemctl is-active sshd