This one will be a bit trickier because of federation. Maybe it is even impossible. But for git hosting, website hosting, email, your cloud, various chats software or torrents it should just work.
I don’t know, maybe ?
But I recommand strongly to have your own domain name.
As long as you do nothing illegal, when you own a domain name, you have legal recourse to keep it. It’s not the case for an email service mail like gmail, which can ban you for no reason tomorrow, and you have no recourse to get back your email address back.
It’s a few euro per year, plus you can mutualize the cost with your family, take a domain name with your last name, this will allow your whole family to have firstname@lastname.yourcountrytld.
I just looked for my lastname, it’s around $10 per year.
I’ll repeat this again, but it means you will own this domain name, you have legal ressources and big companies won’t be able to take your mail address from you.
Else, use duckdns if you really don’t want to pay anything.
You just made a mistake into saying what domain name you will take, someone may buy it before you in order to extort money from you.
It probably won’t happen but…
That reminds me of my Linux server teacher in university. We were to buy a domain name from Namecheap or Gandi during class with some free credits, and the teacher was recommending lastname[dot]com if that was available.
I happened to say aloud “yep, mylastname[dot]com is available” and he quickly sushed me as if I had named Voldemort aloud in Hogwarts, telling me that saying it is a really bad move… lol
I don’t want to be rude but if you can’t afford a domain you probably shouldn’t be hosting a fediverse server.
Honestly do you even need to expose services to the internet? Internet exposure is dangerous and is not necessary for 95% of things. You can use a mesh VPN like netbird or Tailscale if you need remote access.
This isn’t me trying to offend you I just think it would be wise to reduce the scope of you projects.
Not an expert, but AFAICT email self hosting is not considered a good idea, as the maintenance of an email server requires a lot of work. An alternative could be using Cloudflare for the DNS and set up email routing (for free).
Assuming that you mean that you are using the domain name to point to services which are at a residential, dynamic IP address, you will need to set up a Dynamic DNS service.
While I normally agree on #2, it doesnt really apply to Tailscale. Tailscale isn’t completely free, they have a free tier to generate business but it’s limited to 3 users per tailnet. Also its cryptographically impossible for them to snoop on your traffic.
I was referring to OP’s use of IPQuick. This isn’t a service I’m familiar with and it doesn’t seem to be affiliated with any organization that I’m familiar with either.
In a normal domain/DNS scenario, you need to make sure your domain points to the correct IP. Most registrars have websites where you can manage which domain points to which domain in the DNS records.
didn’t have money for an external hard drive or anything like that growing up, so a lot of stuff got lost over the years. but when i upgrade my NAS’ hard drive i will buy an enclosure and scrape all of the important stuff together. like recovery codes for my 3ds collection, old photos of my late cat. that kinda stuff. then i’ll see how frequently i’m gonna update the data.
Se if you can get a DVD or Blu-ray writer and backup stuff to DVD or Blu-ray discs. If you keep the discs in individual jewel cases or in a disc wallet they keep very well.
When you use deduplication on the backup side you can do backups every minute without needing much storage. When the backup programm looks at the filesystem to determine which file has changed, the CPU only need to process the changed files.
For my personal devices i do daily backups. There is not enough change every day.
not only hosting lots of sleazebags, but also having tons of compromised mail machines, so their machines were, according to what I’d read there, the source of much of the world’s spam, and they wouldn’t fix things.
EasyDNS was recommended by one of the SysAdmin reporters on The Register, a few years ago.
He also recommended Linode & Vultr, back then, too.
This stuff in this comment is just my opinion, and my memory of what trustworthy people were reporting a few years ago.
There is a security risk of using your first name and last name in your email. It’s very easy for malicious people to send you emails specifically addressing you. I have realized it now and I take the extra steps to set up good spam blocking in my email.
I’m using Headscale for something similar. I have a VPS and a server at home. Both are on the same Headscale network. On the home server I set up a Matrix server. On the VPS I set up Caddy as a reverse proxy for the home server with its Headscale IP. It works nicely.
Personal and business are extremely different. In personal, you backup to defend against your own screwups, ransomware and hardware failure. You are much more likely to predict what is changing most and what is most important so it’s easier to know exactly what needs hourly backups and what needs monthly backups. In business you protect against everything in personal + other people’s screwups and malicious users.
If you had to setup backups for business without any further details: 7 daily, 4 weekly, 12 monthly (or as many as you can). You really should discuss this with the affected people though.
If you had to setup backups for personal (and not more than a few users): 7 daily, 1 monthly, 1 yearly.
Keep as much as you can handle if you already paid for backups (on-site hardware and fixed cost remote backups). No point having several terabytes of free backup space but this will be more wear on the hardware.
How much time are you willing to lose? If you lost 1 hour of game saves or the office’s work and therefore 1 hour of labour for you or the whole office would it be OK? The “whole office” part is quite unlikely especially if you set up permissions to reduce the amount of damage people can do. It’s most likely to be 1 file or folder.
You generally don’t need to keep hourly snapshots for more than a couple days since if it’s important enough to need the last hours copy, it will probably be noticed within 2 days. Hourly snapshots can also be very expensive.
You almost always want daily snapshots for a week. If you can hold them for longer, then do it since they are useful to restoring screwups that went unnoticed for a while and are very useful for auditing. However, keeping a lot of daily snapshots in a high-churn environment gets expensive quickly especially when backing up Windows VMs.
Weekly and monthly snapshots largely cover auditing and malicious users where something was deleted or changed and nobody noticed for a long time. Prioritise keeping daily snapshots over weekly snapshots, and weekly snapshots over monthly snapshots.
Yearly snapshots are more for archival and restoring that folder which nobody touched forever and was deleted to save space.
The numbers above assume a backup system which keeps anything older than 1 month in full and maybe even a week in full (a total duplicate). This is generally done in case of corruption. Keeping daily snapshots for 1 year as increments is very cheap but you risk losing everything due to bitrot. If you are depending on incrementals for long periods of time, you need regular scrubs and redundancy.
When referring to snapshots I am referring to snapshots stored on the backup storage, not production. Snapshots on the same storage as your production are only useful for non-hardware issues and some ransomware issues. You snapshots must exist on a seperate server and storage. Your snapshots must also be replicated off-site minus hourly snapshots unless you absolutely cannot afford to lose the last hour (billing/transaction details).
selfhosted
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.