smiletolerantly

TBH, it sounds like you have nothing to worry about then! Open ports aren't really an issue in-and-on itself, they are problematic because the software listening on them might be vulnerable, and the (standard-) ports can provide knowledge about the nature pf the application, making it easier to target specific software with an exploit.

Since a bot has no way of finding out what services you are running, they could only attack caddy - which I'd put down as a negligible danger.

My ISP blocks incoming data to common ports unless you get a business account.

Oof, sorry, that sucks. I think you could still go the route I described though: For your domain example.com and example service myservice, listen on port :12345 and drop everything that isn't requesting myservice.example.com:12345. Then forward the matching requests to your service's actual port, e.g. 23456, which is closed to the internet.

Edit: and just to clarify, for service otherservice, you do not need to open a second port; stick with the one, but in addition to myservice.example.com:12345, also accept requests for otherservice.example.com:12345, but proxy that to the (again, closed-to-the-internet) port :34567.

The advantage here is that bots cannot guess from your ports what software you are running, and since caddy (or any of the mature reverse proxies) can be expected to be reasonably secure, I would not worry about bots being able to exploit the reverse proxy's port. Bots also no longer have a direct line of communication to your services. In short, the routine of "let's scan ports; ah, port x is open indicating use of service y; try automated exploit z" gets prevented.

I am scratching my head here: why open up ports at all? It it just to avoid having to pay for a domain? The usual way to go about this is to only proxy 443 traffic to the intended host/vm/port based on the (sub) domain, and just drop everything else, including requests on 443 that do not match your subdomains.

Granted, there are some services actually requiring open ports, but the majority don't (and you mention a webserver, where we're definitely back to: why open anything beyond 443?).

Client side, under advanced:

❤️

Link?

That's a setting

Re: Spain: the headline was bullshit. If you are arrested and then investigated and it turns out you use Graphene, they'll go "huh, I wonder why. We've seen a lot of drug dealers use Graphene. Let's investigate in that direction as well".

Noone is being arrested or targeted FOR having GOS.

InfCloud. Works well with Radicale, and does contacts, too.

It's not pretty, but works very well for the 5/100 times I want to check through a browser instead of Calendar app / Thunderbird.

Yes. Using simple-nixos-mailserver as the foundation.

Really great experience, and have had no deliverability issues.

I hope forgejo's federation efforts come along. Being able to host projects on my own instance, yet receive contributions without having to allow people to register on my instance, would give me the push to completely abandon Github.

This is about as useful as the assholes going "It's not Pedophilia, it's Hebephilia!".