Mar 18 10:38:24 ewelt sshd[3639]: Invalid user cvsadmin from 212.64.88.97 port 53374
Mar 18 10:38:26 ewelt sshd[3639]: Failed password for invalid user cvsadmin from 212.64.88.97 port 53374 ssh2
Mar 18 10:41:20 ewelt sshd[4029]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.64.88.97  user=root
Mar 18 10:41:22 ewelt sshd[4029]: Failed password for root from 212.64.88.97 port 58358 ssh2
...

2020-03-18 01:34:34,716 fail2ban.actions        [518]: NOTICE  [wordpress-beatrice-main] Ban 62.210.29.142
2020-03-18 05:51:20,452 fail2ban.actions        [518]: NOTICE  [wordpress-beatrice-main] Ban 62.210.29.142
2020-03-18 12:15:50,173 fail2ban.actions        [518]: NOTICE  [wordpress-beatrice-main] Ban 62.210.29.142
...

$f2bV_matches

2020-03-18T11:35:49.561934vps773228.ovh.net sshd[26030]: Failed password for root from 218.92.0.173 port 4432 ssh2
2020-03-18T11:35:53.356381vps773228.ovh.net sshd[26030]: Failed password for root from 218.92.0.173 port 4432 ssh2
2020-03-18T11:35:56.698953vps773228.ovh.net sshd[26030]: Failed password for root from 218.92.0.173 port 4432 ssh2
2020-03-18T11:35:56.699990vps773228.ovh.net sshd[26030]: error: maximum authentication attempts exceeded for root from 218.92.0.173 port 4432 ssh2 [preauth]
2020-03-18T11:35:56.700012vps773228.ovh.net sshd[26030]: Disconnecting: Too many authentication failures [preauth]
...

Invalid user master from 49.235.86.177 port 40346

2020-03-18T08:56:45.972251abusebot-8.cloudsearch.cf sshd[1250]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip252.ip-167-114-230.eu  user=root
2020-03-18T08:56:48.374526abusebot-8.cloudsearch.cf sshd[1250]: Failed password for root from 167.114.230.252 port 50238 ssh2
2020-03-18T09:02:05.138125abusebot-8.cloudsearch.cf sshd[1671]: Invalid user vnc from 167.114.230.252 port 60480
2020-03-18T09:02:05.145291abusebot-8.cloudsearch.cf sshd[1671]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip252.ip-167-114-230.eu
2020-03-18T09:02:05.138125abusebot-8.cloudsearch.cf sshd[1671]: Invalid user vnc from 167.114.230.252 port 60480
2020-03-18T09:02:06.477363abusebot-8.cloudsearch.cf sshd[1671]: Failed password for invalid user vnc from 167.114.230.252 port 60480 ssh2
2020-03-18T09:06:01.067960abusebot-8.cloudsearch.cf sshd[1873]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= r
...

2020-03-18T10:00:49.196252abusebot-3.cloudsearch.cf sshd[26173]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.227.96.190  user=root
2020-03-18T10:00:50.640845abusebot-3.cloudsearch.cf sshd[26173]: Failed password for root from 165.227.96.190 port 33722 ssh2
2020-03-18T10:04:38.472510abusebot-3.cloudsearch.cf sshd[26461]: Invalid user irc from 165.227.96.190 port 45346
2020-03-18T10:04:38.478419abusebot-3.cloudsearch.cf sshd[26461]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.227.96.190
2020-03-18T10:04:38.472510abusebot-3.cloudsearch.cf sshd[26461]: Invalid user irc from 165.227.96.190 port 45346
2020-03-18T10:04:41.031500abusebot-3.cloudsearch.cf sshd[26461]: Failed password for invalid user irc from 165.227.96.190 port 45346 ssh2
2020-03-18T10:06:39.566673abusebot-3.cloudsearch.cf sshd[26697]: Invalid user testing from 165.227.96.190 port 56832
...

(From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question…

My name’s Eric, I found drericnye.com after doing a quick search – you showed up near the top of the rankings, so whatever you’re doing for SEO, looks like it’s working well.

So here’s my question – what happens AFTER someone lands on your site?  Anything?

Research tells us at least 70% of the people who find your site, after a quick once-over, they disappear… forever.

That means that all the work and effort you put into getting them to show up, goes down the tubes.

Why would you want all that good work – and the great site you’ve built – go to waste?

Because the odds are they’ll just skip over calling or even grabbing their phone, leaving you high and dry.

But here’s a thought… what if you could make it super-simple for someone to raise their hand, say, “okay, let’s talk” without requiring them to even pull their cell phone from their pocket?
  
You can – thanks to revolutionary new software that can

Mar 18 04:47:20  sshd\[5282\]: User root from 122.152.195.84 not allowed because not listed in AllowUsersMar 18 04:47:22  sshd\[5282\]: Failed password for invalid user root from 122.152.195.84 port 47954 ssh2
...

Mar 17 19:50:02 web1 sshd\[17530\]: Invalid user server-pilotuser from 144.34.248.219
Mar 17 19:50:02 web1 sshd\[17530\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.34.248.219
Mar 17 19:50:04 web1 sshd\[17530\]: Failed password for invalid user server-pilotuser from 144.34.248.219 port 56654 ssh2
Mar 17 19:54:27 web1 sshd\[17965\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.34.248.219  user=root
Mar 17 19:54:28 web1 sshd\[17965\]: Failed password for root from 144.34.248.219 port 45366 ssh2

Mar 18 11:12:39 vps647732 sshd[10141]: Failed password for root from 142.93.235.47 port 36408 ssh2
...

Mar 18 06:15:43 cloud sshd[1012]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.218.85.122 
Mar 18 06:15:45 cloud sshd[1012]: Failed password for invalid user miner from 46.218.85.122 port 57921 ssh2

Chat Spam

20/3/17@23:47:28: FAIL: Alarm-Network address from=36.237.51.233
20/3/17@23:47:29: FAIL: Alarm-Network address from=36.237.51.233
...

(pop3d) Failed POP3 login from 114.113.146.57 (CN/China/-): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: Mar 18 07:17:56 ir1 dovecot[4133960]: pop3-login: Aborted login (auth failed, 1 attempts in 2 secs): user=, method=PLAIN, rip=114.113.146.57, lip=5.63.12.44, session=