

Because you either need an announce URL or publishing your torrent to the DHT for your friends to be able to peer with you.
Seeding copyrighted material using a public announce URL or the DHT will get you in trouble in most western countries.
Because you either need an announce URL or publishing your torrent to the DHT for your friends to be able to peer with you.
Seeding copyrighted material using a public announce URL or the DHT will get you in trouble in most western countries.
Enabling multi DC redundancy is really easy though. The other providers you mentioned may have it by default, but they’re also a lot more expensive.
I love that they let me pick my own redundancy strategy, without forcing me to pay for theirs
ENS stands for Ethereum Name Service
I’m personally using Docker MailServer. It’s been working great for over a year now, but mailu seems to have some interesting features (I’m especially interested in the admin panel)
You’re probably behind a CGNAT, check out the other comments
Glad I could help :)
Your ISP might make you go through another layer of NAT. Can you find the WAN IP address of your router and compare it to your public IP address from a website such as ipinfo.io ?
If they do not match, you’re probably out of luck and will need to forward your port from an actually public IP in order to achieve what you want
More details : CGNAT (Carrier Grade Network Address Translation) is basically a second router between your router and the public internet. This second router is configured in the same way as your personal one, the main difference being that your ISP fully manages it. From the viewpoint of this second router, your WAN IP is a private IP, and you share one actual public IP with several other customers (the same way all devices on you LAN share one single WAN IP)
Performing port forwarding from the public internet to your LAN, when behind a CGNAT, would require you to be able to configure a forwarding rule in the ISP’s NAT, which you usually cannot do.
KOReader is by far better than the crappy stock firmware from Kobo. While the interface is not the prettiest, it still has a lot of advantages :
While I really hate Kobo’s stock UI, I still recommend getting one if you like truly owning your hardware. It’s really easy to enable ssh access and then it’s just regular Linux. It’s even possible to run an X server and launch Linux graphical apps on the e-ink display (not quite usable though)
I can recommend some stuff I’ve been using myself :
I design, deploy and maintain such infrastructures for my own customers, so feel free to DM me with more details about your business if you need help with this
Alternatively, if your databases are on a filesystem that supports snapshots (LVM, btrfs or ZFS for instance), you can make a snapshot of the filesystem, mount the snapshot and backup thame database from it. This will ensure the backup is consistent with itself (the backed up directory was not written to between the beginning and the end of the backup)