Have a look at https://forwardemail.net/. It’s a service that handles accepting (and optionally sending) email on your domain, and forwarding any received mail to other backend services, like a gmail account. All you need to do is set some DNS records, like MX and their servers will handle everything. It works fine with domains hosted on cloudflare, and has excellent howto’s to get everything set up and running.

Edit: The great thing about this service, imho, is their guides. They don’t just have a static howto, they template in your information into the exact string you need to copy/paste into the service provider’s web interface. Want to encrypt your plaintext TXT records? There’s a button for that on the guide. Want to learn how to get around a port 25 ISP block, they have a guide for that. Want to set up proper Send-As from Gmail using their SMTP server? There’s a guide for that. :-)

No. USB is not designed to be reliable. It’s designed to be plug and play. Don’t plug and play with your data.

I have always preferred TightVNC over the various other VNC flavours. It does only one thing, but does it well, with minimal setup and network requirements.

I have tried RustDesk recently, and the performance when it worked was nice. But I found it too complex to set up across more than a few machines, and ultimately unreliable, with connections failing without any useful error message, an unresponsive relay, weird certificate errors, etc… It needs a couple of years to mature.

I would suggest looking into using WireGuard to wire your various networks and computers together. It works very well most platforms. You can easily give laptops a road-warrior connection, so they always phone home. Then it doesn’t matter where they are.

KeePass. Putting your passwords on someone else’s webserver is just asking for trouble.

Various different ways for various different types of files.

Anything important is shared between my desktop PC’s, servers and my phone through Syncthing. Those syncthing folders are all also shared with two separate servers (in two separate locations) with hourly, daily, weekly, monthly volume snapshotting. Think your financial administration, work files, anything you produce, write, your main music collection, etc… It’s also a great way to keep your music in sync between your desktop PC and your phone.

Servers have their configuration files, /etc, /var/log, /root, etc… rsynced every 15 minutes to the same two backup servers, also to snapshotted volumes. That way, should any one server burn down, I can rebuild it in a trivial amount of time. This also goes for user profiles, document directories, ProgramData, and anything non-synced on windows PC’s.

Specific data sets, like database backups, repositories and such are also generally rsynced regularly, some to snapshotted volumes, some to regulars, depending on the size and volatility of the data.

Bigger file shares, like movies, tv-shows, etc… I don’t backup, but they’re stored on a distributed GlusterFS, so if any one server goes down, that doesn’t lose me everything just yet.

Hardware will fail, sooner or later. You should see any one device as essentially disposable, and have anything of worth synced and archived automatically.

I would suggest having a look at podman. It’s a drop-in replacement for docker, except it doesn’t require a constantly running daemon, it comes in the main package repositories, so you don’t have to do the key and repository stuff, and cockpit has a plugin to help manage podman containers.

Everyone else.

I wouldn’t try to run an i2p node on a machine that frequently disconnects from the internet. For laptop access, I would run the i2p node in a virtual machine somewhere, and use a VPN to connect the laptop to the node.