On fresh droplet if i execute next commands:
hex@pcname:~$ ssh -i /home/hex/.ssh/id_rsa_2023digitalocean root@0.0.0.0
root@ubuntu-s-1vcpu-1gb-fra1-01:~# sudo apt update
root@ubuntu-s-1vcpu-1gb-fra1-01:~#
root@ubuntu-s-1vcpu-1gb-fra1-01:~# sudo ufw app list
Available applications:
Nginx Full
Nginx HTTP
Nginx HTTPS
OpenSSH
root@ubuntu-s-1vcpu-1gb-fra1-01:~# sudo ufw allow 'Nginx HTTP'
Rules updated
Rules updated (v6)
root@ubuntu-s-1vcpu-1gb-fra1-01:~# sudo ufw status
Status: inactive
root@ubuntu-s-1vcpu-1gb-fra1-01:~# sudo ufw enable
Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
Firewall is active and enabled on system startup
root@ubuntu-s-1vcpu-1gb-fra1-01:~# sudo reboot
it is impossible to ssh -i /home/hex/.ssh/id_rsa root@0.0.0.0
back into my droplet, why? throws connection timed out
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Enter your email to get $200 in credit for your first 60 days with DigitalOcean.
New accounts only. By submitting your email you agree to our Privacy Policy.
Hey @829d98972d174aa580234614f3,
Your Firewall is not allowing access on port 22 which is your SSH. You’ll need to use the Recovery Console and allow connections on port 22 as well.
The Recovery Console provides out-of-band access and is available regardless of your network settings. It emulates the access you would have if you were sitting down with a keyboard and monitor attached to the actual server. You can use this feature to log in and revert bad settings to regain normal access.
More on that here:
https://docs.digitalocean.com/products/droplets/how-to/recovery/recovery-console/