endlessh VS docker-swag

You can reduce the noise a lot by moving ssh to a non standard port. Security through obscurity isn't actually security, but it will reduce the number of attempts you receive. Another thing I like to do is put Endlessh on the standard port 22. That way as bots go by they will get stuck or at least slow down on that connection.

Even this requires you to successfully guess the username and password correctly, and if it's just not the default most people won't bother brute forcing further. Sidenote: you can use endlessh on a computer and port forward port 22 to trap scanners that scan the entire internet for open ssh ports to exploit.

The fun way is moving your ssh port somewhere else and installing endlessh to f the bots.

Such as endlessh

But, as a prank to Chinese hackers, what I did on my system was to run endless ssh. It keeps the ssh client busy as it slowly sends the ssh banner. I modified the code to send strings like:

Install https://github.com/skeeto/endlessh to run on eg. port 22233 (in /etc/endlessh.conf)

this'll help

I have port 22 open on my home server, but I have this running on that port: https://github.com/skeeto/endlessh. It's quite wild seeing the amount of connection attempts for this.

https://docs.linuxserver.io/general/swag makes the setup of Authelia very simple.

If you're issuing certs, you might as well centralize with a reverse proxy etc etc. -- take a look at something like a combination of Duckdns and SWAG from linuxserver.io (https://docs.linuxserver.io/general/swag), which does a lot of the heavy lifting for integrations with Lets Encrypt.

Linuxserver.io maintains a reverse proxy (SWAG) and they have a github repo of all the configs they support, nextcloud being one of them (ofc to do it on your own you have to merge a few of the includes they have ssl.conf, proxy.conf, etc).

I have a domain through Cloudflare and I use a Cloudflare tunnel to expose my services on my domain. Geoblocking helps filter a lot of erroneous traffic. Cloudflare also has some useful features to help with blocking malicious attacks and bots. For my reverse proxy, I use SWAG

Long-time amateur here. I tried a bunch of different methods for reverse proxies, and in the end, I used the SWAG docker container from Linuxserver.io, which simplifies it a great deal, and helped me understand the proper syntax.

This is what I used: https://docs.linuxserver.io/general/swag

It's all in their repo https://github.com/linuxserver/docker-swag and docs https://docs.linuxserver.io/general/swag