Is there something wrong with using Synology’s built-in reverse proxy?
Is there something wrong with using Synology’s built-in reverse proxy?
You don’t have wordfence and auto-updates turned on?
Here’s what I think happened: Everything you see is something you did.
The subdomain you host points to your IP … or at least it did. Your ADSL IP address has changed and your domain is now pointing at someone else’s IP as their ADSL has claimed it.
Ping the subdomain and see the IP address. Now go to https://whatismyipaddress.com/ and see what your IP address is. They’re different now, right?
Getting an obscure domain name doesn’t matter as attackers go straight to the IP address. If you have a certificate on your secret domain name, they have your domain the moment they hit port 443.
Don’t use “security through obscurity”; instead just secure your services or host a VPN.
Wildcard certificates and HAProxy on pfSense is how I do it.
Loads of us run Ubuntu VMs on Proxmox.
Why not just run VMware on Mac OS?
I use HAProxy on pfSense with wildcard LetsEncrypt certs and a firewall rule only to allow connections from the WAN IP Address.
It’s really easy and requires no certificates on the target servers.
If you use the same AppleID, you get to keep all the apps you bought.
I have six (?) Macs/phones all using the same ID.