Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

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!
If use
setcap 'cap_net_bind_service=+ep' /usr/local/bin/endlessh
You get
Failed to set capabilities on file `/usr/local/bin/endlessh' (Invalid argument)
The value of the capability argument is not permitted for a file. Or the file is not a regular (non-symlink) file
Use it.
setcap 'cap_net_bind_service=+ep' /usr/local/bin/endlessh/endlessh
Excellent tutorial, I will suggest to add one and link it to a fail2ban as a great compliment for this one. Thank you again for the great proof of work ^^
Some other suggestions you can look at.
Many attackers specifically target port 22 for SSH brute force attacks. You can configure Endlessh to run on another port (e.g., 2222, 2223, 8080) to make it less obvious.
/etc/endlessh/configPORT=2222
If you already have a web server like Nginx or Apache, you can use it as a reverse proxy to filter out obvious bad actors before they reach Endlessh.
server {
listen 2222;
location / {
proxy_pass http://127.0.0.1:2223;
}
}
This can provide an additional layer of filtering and logging.
Additionally, instead of running Endlessh on your main production droplet, consider using a cheap, disposable Droplet to act as a decoy.