Hi, I recommend you read the book “Run Your Own Mail Server”. The fact that a book exists for this topic is all the proof you need to not do this decision. But if you absolutely must, this is the way.
Hi, I recommend you read the book “Run Your Own Mail Server”. The fact that a book exists for this topic is all the proof you need to not do this decision. But if you absolutely must, this is the way.
Only I rely on my services and if they break I’ll fix them myself.
I don’t run Immich specifically but all other software I run is on :latest tags and unattended-upgrades on Debian. It works so, why bother?
Docker Engine is open source. They could’ve easily contributed patches to it which just further proves that it is a NIH syndrome response.
I use Docker exclusively. Podman is the NIH syndrome response to an industry standard. It has its benefits but Docker just works.
I remember researching the topic a while back. SimpleMDM seems to do it, but it requires paying Apple $300 a year. Luckily, Mosyle allows up to 30 devices for free.
Yeah… the company that runs the gTLD thinks they struck gold and charge a premium for it. I wanted to purchase cloud.sucks but at $16k a year… nah I’ll pass.
https://en.m.wikipedia.org/wiki/.sucks_(registry)
I’m gonna leave this here, go wild. Do note that most of big tech already bought their .sucks domains.
I just read some their other comments on this thread… lmao… don’t think I’d ever seen such entitlement in this community.
Basically once you have WG set up, you will have an additional interface with it’s own IP in “ifconfig”. At that point all the ports are available and you can just point your reverse proxy to them (sorry I’m an NGINX user, I have no idea how Traefik works).
Additionally don’t forget to add keep-alive in your WG config so that the service doesn’t shut off once traffic stops going between both servers.
CF free tier specifies in their ToS it’s not for media so likely yeah, you’re getting some sort of rate limitation.
Actually I did.
No you didn’t. You said that you had set up TrueNAS, that means it’s working. I inferred from a different comment that you’re actually experiencing problems with TrueNAS and even left a reply to hopefully help you.
Logs of…what, exactly?
It was an example. I did not expect you to take it literally. If things aren’t working, then we need to know which things aren’t working. Screenshots, logs, even “I can’t connect to my own server” is better.
I did
I had to infer from other comments that you’re having trouble with TrueNAS. Perhaps it’s because English is my 3rd language, but clearly the point didn’t get across to others in this thread either.
SSH - secure shell. It is a way to connect to your remote machine. On server distributions it is usually open by default. If you’re running Windows on your main computer, you can connect with either the included OpenSSH client (terrible experience) or download a utility like PuTTY. Detailed explanation here: https://bitlaunch.io/blog/how-to-connect-to-ssh-with-putty/
Web shell - Likely refers to the admin control panel of the software. I don’t run TrueNAS so I can only assume. Likely if you open a browser tab and type in your server’s IP and the specified port in the documentation you’ll be able to access it (i.e http://192.168.50.2:8080)
“go to system --> advanced” where!? - Likely in the admin panel. Again, don’t run the software personally.
Link aggregations - This is more on the advanced side and likely not necessary for you at this stage. The idea is to allow you to connect more interfaces and increase bandwidth, likely not necessary for a home set up, would advise you keep it for later.
VLAN - Virtual Local Area Network. In the past before VLANs we had switches/hubs that when you connected a cable to them they would automatically become a member of the same network. VLAN allows you to split one physical network into many virtual networks. This is good because you can them limit access inbetween VLANs or block traffic for your server VLANs (if for example, you don’t want it to collect telemetry and phone home. I personally do it on the IoT VLAN).
Default Gateway - It is the IP address of your router in most cases. If you are on the 192.168.10.0 - 192.168.10.255 network and you’re trying to send packets inside that network then your clients will not contact the default gateway, they will instead just reach each other directly. The default gateway is necessary to send packets outside of your network.
Don’t worry, the Microsoft support forums don’t lack self righteous answers either. I won’t talk about about desktop Linux because that has nothing to do with this thread and has a plethora of other issues as to why it won’t take off but specifically self hosting won’t take off because it never meant to. We will never get to a point in our lives where 100% (or hell, even 10%) of the population are proficient enough in how a computer works to self host their own software stack, and that is okay. If you self-host services make them available to your friends and family. Never thought that self-host was a movement of some sort where we’re trying to convert people who rely on centralized products into self hosting gurus, guess that’s a first for me.
I didn’t read the other comments, only the main post in which I do not see what you define as “detailed account of my situation”. You said that you have an issue with some software (you did not even bother to specify which) and that you want people to hop on Jitsi to duke it out with you. Had it been me, I would’ve posted logs, posted what I’m trying to achieve and why I’m unable to do it so far or where I would appreciate additional explanation. You want people to help you but you do not make it any easy for them to do.
But that’s okay, stay arrogant and we’ll see how far it gets you.
Not to be a dick, but to explain why forming the question the way you did will not get you any assistance or responses for that matter.
The truth is, not a single person here went to self-hosting school, we got to where we are because of our love for the craft. I hope this doesn’t discourage you from trying. The high you’ll get from finally solving that one error you’ve been trying to resolve for hours is one I love experiencing over and over again which is why I self-host.
You’ll have to wait until they ping home and ask to renew the DHCP lease, on most home routers it’s once every 30 minutes or so.
Hi!
I don’t know which router equipment you’re using so I can’t advise further, however, In your DHCP server settings you need to set the DNS server to your AdGuard DNS and then release/renew your leases on your client devices. (This can be a command like ipconfig /release on your Win machines, or reconnecting your wifi on mobile devices).
Not a pantry or a chemical lab, but I’m planning to spin up a container later tonight because this is going to make things so much easier.
Thank you.
For the license to be changed every team member needs to submit a written agreement that he agrees to the change, otherwise their contributions must be removed as they were written under a different license, the only exception is usually permissive licenses such as MIT/BSD 3 clause.
Usually, to rugpull FOSS contributors, companies who maintain FOSS software ask contributors to sign a CLA which waives their rights and lets the control their contributions. Immich isn’t doing any of that, and it will likely remain AGPL forever because changing the license will be a big hassle for them with the amount of contributors.