Featured AI Products
Compute
Build, deploy, and scale cloud compute resources
Containers and Images
Safely store and manage containers and backups
Managed Databases
Fully managed resources running popular database engines
Management and Dev Tools
Control infrastructure and gather insights
Networking
Secure and control traffic to apps
Security
Help protect your account and resources with these security features
Storage
Store and access any amount of data reliably in the cloud
Browse all products
AI/ML
CMS
Data and IoT
Developer Tools
Gaming and Media
Hosting
Security and Networking
Startups and SMBs
Web and App Platforms
See all solutions
Community
Documentation
Developer Tools
Get Involved
Utilities and Help
Become a Partner
Marketplace
Pricing

- Community
- DigitalOcean
- Community
- DigitalOcean

I got over 3k fail2ban emails

Posted on June 8, 2016

Please advice on what to do next? all the attempting IPs are from different . Should I just keep watching or what can i do to kill their attempts?

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.

Jayvicson

June 12, 2016

@jschwenn thanks for the tip. I m still learning linux command.I have tried changing it on /etc/ssh/sshd_config but , many request like apache2 came up with error. likewise i dont know how many services do require that port. i had to turn off my ufw because eachtim its on, the website goes offline. is there something I am actually supposed to watch for?

Jon Schwenn

June 9, 2016

Well, fail2ban is killing their attempts. CSF would similarly block them as well.

For the sake of reducing log entires and emails, you may want to have SSH listen on a port other than 22.

You could edit your /etc/ssh/sshd_config file and change the Port line to be a different port, say like 9022. Most importantly, you’ll need to make sure your software firewall has this port open. Then you’ll want to restart the ssh process.

This will not make you more secure or make it impossible for someone to attempt to log into your server. It’s going to reduce the attempts making it easier to read through logs and email alerts.

The developer cloud

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

View all products

Start building today

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