I disagree, you'll have your backups, so even if everything breaks you will have a failsafe. If you get compromised it's still not an issue: Everything server side is encrypted, the safety is in the clients and your master password length.
So, I see no particular differences with other services. Considering I hear of some issues with bitwarden servers that are constantly under attack, selfhosting could even increase the availability.
Next time
Sorry, it's the built-in console of Google Cloud. But there are so many monitoring solution around that you can probably find one of your liking. Look on awesome-selfhosted for "monitoring"
Well nothing compared to rest of the infrastructure, we are talking of 0.05$ per month per machine at standard egress rates of major cloud providers. Still, why having them?
In all the cases for me is sufficient to backup the folder which host the volume for persistent data of each container. I typically do not care to stop and reload containers but nothing prevents you to do so in the backup script. Indeed if a database is concerned the best way is to create a dump and backup that one file. Considering tools, Borg and restic are both great. I am moving progressively from Borg to restic+rclone to exploit free cloud services.
So it seems. Do you think this was from the detected user activity? A colleague reported it was using it and it stopped working from one second to the next. Maybe some of his traffic looked suspicious? I am opening a ticket in any case today.
Now it's pretty clear, I am mistaken for a malicious site (probably because many different computers in the lab started to exchange data with this obscure freedns subdomain) by this software from Palo Alto Networks https://www.gavstech.com/palo-alto-firewall-dns-sinkhole/ which rewrites the DNS response
Nice, I am routed to sinkhole.paloaltonetworks.com I am a malicious domain apparently.
What does it mean?
nslookup my.domain.com
Server: dns.google
Address: 8.8.8.8
Non-authoritative answer:
Name: my.domain.com
Addresses: ::1
xx.x.xx.xxx (wrong IPV4 address from the other side of the world)
If I use 8.8.8.8 at home addresses is first of all "address" and is correct.
I think this is exactly the case, they have some issues with the DNS server and, as some other comments indicate it is possible, they reset my settings for DNS servers at router level. So nor cloudflare or others can help, only the line in etc/hosts works
Interesting, thanks. I think this is what it is happening. Feels like I can put whatever DNS server and still end up with an internal one.
ssh -p 12345 would leave your boxes accessible from anywhere too. Other blocks of IPs receive 10 times or more requests, as scanners can focus on blocks of ips from major providers.