I have a “prep script” that takes care of everything.
It takes less than 2 minutes to run on a fresh install and does all kind of fun things.
I have a “prep script” that takes care of everything.
It takes less than 2 minutes to run on a fresh install and does all kind of fun things.
I still see posts from there from 4hrs ago on my instance.
It’s probably a DNS error.
Don’t use the built in crap.
Get a Raspberry or other tiny computer and set it up as a “smart TV box”.
You say you can’t invest in a solution. But this problem require you to throw money at it to go away.
Why not both?
Wireguard doesn’t answer unless you hand shake with a valid package.
There are three 512 bit keys.
And you can put ssh behind it with ssh keys.
The extra later of defence is quite significant.
No “actual user” is blocked by fail2ban. They auth with keys, can’t really fail.
Blocking after three fail is very reasonable and effective. It also keeps the logs noise down.
In the summer, I’m dumping it outside.
In the winter, I’m heating my garage with it.
Has worked great for many years now.
English isn’t my first, or second, language. Maybe something got lost in translation.
I’m sorry if I sound like a dick head.
I thought the “I’m alone there” covered it.
Donations are usually volontary so if you run a very large instance, income isn’t guaranteed.
Donations is the way forward.
A dollar or two should be enough per month.
I run mine for free, self hosted, and I’m alone there. Server cost is absorbed by my hobby expenses. Maybe $20 per month.
I run a home server, it’s federated.
That’s a horrible installation. Send them the picture and ask them to remedy ASAP.
Jellyfin
Or just a file share and mount it in Windows as a network drive. Then view the content with VLC.
Check the cables for damages, or tight bends, that could cause a lot of packet loss.