Protect Server

[Vladimir7i]

on my private server in log I can see a lot of income spam connections and most of them have state [Accepted connection]
how to hide server from them?

log looking like this:

2022-10-16 14:34:13.316876+02:00 [info] <0.542.0>@ejabberd_listener:accept/7:273 (<0.7472.3>) Accepted connection [::ffff:87.236.176.89]:58639 -> [::ffff:MYIP]:5443 2022-10-16 14:34:16.598207+02:00 [info] <0.542.0>@ejabberd_listener:accept/7:273 (<0.7473.3>) Accepted connection [::ffff:87.236.176.27]:57313 -> [::ffff:MYIP]:5443 2022-10-16 14:34:19.660483+02:00 [info] <0.542.0>@ejabberd_listener:accept/7:273 (<0.7474.3>) Accepted connection [::ffff:87.236.176.151]:54447 -> [::ffff:MYIP]:5443 2022-10-16 14:34:22.718103+02:00 [info] <0.542.0>@ejabberd_listener:accept/7:273 (<0.7475.3>) Accepted connection [::ffff:87.236.176.21]:44081 -> [::ffff:MYIP]:5443 2022-10-16 14:34:25.827295+02:00 [info] <0.542.0>@ejabberd_listener:accept/7:273 (none) Accepted connection [::ffff:87.236.176.21]:43185 -> [::ffff:MYIP]:5443 2022-10-16 14:34:25.889556+02:00 [info] <0.542.0>@ejabberd_listener:accept/7:273 (<0.7477.3>) Accepted connection [::ffff:87.236.176.17]:49653 -> [::ffff:MYIP]:5443 2022-10-16 14:34:28.917290+02:00 [info] <0.542.0>@ejabberd_listener:accept/7:273 (<0.7478.3>) Accepted connection [::ffff:87.236.176.145]:33695 -> [::ffff:MYIP]:5443 2022-10-16 14:34:37.997000+02:00 [info] <0.542.0>@ejabberd_listener:accept/7:273 (<0.7479.3>) Accepted connection [::ffff:87.236.176.145]:58225 -> [::ffff:MYIP]:5443 2022-10-16 14:34:41.100977+02:00 [info] <0.542.0>@ejabberd_listener:accept/7:273 (<0.7480.3>) Accepted connection [::ffff:87.236.176.30]:33801 -> [::ffff:MYIP]:5443 2022-10-16 14:34:48.380883+02:00 [info] <0.542.0>@ejabberd_listener:accept/7:273 (<0.7482.3>) Accepted connection [::ffff:87.236.176.205]:49755 -> [::ffff:MYIP]:5443 2022-10-16 14:34:48.575557+02:00 [info] <0.542.0>@ejabberd_listener:accept/7:273 (<0.7483.3>) Accepted connection [::ffff:87.236.176.108]:41555 -> [::ffff:MYIP]:5443 2022-10-16 14:34:48.771315+02:00 [info] <0.542.0>@ejabberd_listener:accept/7:273 (<0.7484.3>) Accepted connection [::ffff:87.236.176.176]:55619 -> [::ffff:MYIP]:5443 2022-10-16 14:34:48.968766+02:00 [info] <0.542.0>@ejabberd_listener:accept/7:273 (<0.7485.3>) Accepted connection [::ffff:87.236.176.233]:46435 -> [::ffff:MYIP]:5443 2022-10-16 14:34:49.152452+02:00 [info] <0.542.0>@ejabberd_listener:accept/7:273 (<0.7486.3>) Accepted connection [::ffff:87.236.176.183]:49805 -> [::ffff:MYIP]:5443 2022-10-16 14:34:49.334203+02:00 [info] <0.542.0>@ejabberd_listener:accept/7:273 (<0.7487.3>) Accepted connection [::ffff:87.236.176.109]:56431 -> [::ffff:MYIP]:5443 2022-10-16 14:34:49.512785+02:00 [info] <0.542.0>@ejabberd_listener:accept/7:273 (<0.7488.3>) Accepted connection [::ffff:87.236.176.126]:44253 -> [::ffff:MYIP]:5443 2022-10-16 14:34:49.702006+02:00 [info] <0.542.0>@ejabberd_listener:accept/7:273 (<0.7489.3>) Accepted connection [::ffff:87.236.176.93]:55337 -> [::ffff:MYIP]:5443 2022-10-16 14:34:49.890456+02:00 [info] <0.542.0>@ejabberd_listener:accept/7:273 (<0.7490.3>) Accepted connection [::ffff:87.236.176.208]:50049 -> [::ffff:MYIP]:5443 2022-10-16 14:34:50.081506+02:00 [info] <0.542.0>@ejabberd_listener:accept/7:273 (<0.7491.3>) Accepted connection [::ffff:87.236.176.253]:46973 -> [::ffff:MYIP]:5443 2022-10-16 15:14:28.373464+02:00 [info] <0.540.0>@ejabberd_listener:accept/7:273 (<0.7564.3>) Accepted connection [::ffff:192.241.206.21]:35704 -> [::ffff:MYIP]:5223 2022-10-16 15:59:24.718469+02:00 [info] <0.539.0>@ejabberd_listener:accept/7:273 (<0.7647.3>) Accepted connection [::ffff:192.241.218.150]:37596 -> [::ffff:MYIP]:5222 2022-10-16 16:05:16.559470+02:00 [info] <0.539.0>@ejabberd_listener:accept/7:273 (<0.7659.3>) Accepted connection [::ffff:192.241.215.232]:60572 -> [::ffff:MYIP]:5222 2022-10-16 16:12:39.515553+02:00 [info] <0.541.0>@ejabberd_listener:accept/7:273 (<0.7673.3>) Accepted connection [::ffff:192.241.218.126]:42842 -> [::ffff:MYIP]:5269

[badlop]

You could try setting s2s_access by IP network, but I'm not sure it will block connections even before they are attempted, and maybe logs are still produced.

It may be preferable to setup this IP filtering at the firewall.