• 0 Posts
  • 7 Comments
Joined 8 months ago
cake
Cake day: July 24th, 2024

help-circle




  • Not sure how technitium works but just from my selfhosting experience are you sure your not hitting dns-rebinding protection somwhere.

    In short DNS rebinding stops domains from being resolved to private IP ranges so you don’t end up back in your Network when you seem to be resolving a public domain.

    I have to set up any domains that resolve locally in my router (which also does DNS and DHCP) but not sure if that’s necessary with technitium


  • Nextcloud.

    I was hosting nextcloud at home for years. Then when I worked in a Datacenter I got to host some servers there from free so I set up a two-node proxmox with nextcloud and some other stuff. Now I don’t work there anymore and I really felt the hole nextcloud left, no more notes syncing for notes, tasks, calendar, podcasts no more place to upload my photos from my phone … So now I’m hosting nextcloud at home again.

    I also host jellyfin which is nice but if I don’t have it doesn’t actively hamper my workflow.


  • Worked as a sysadmin for years dealing with all kinds of certificates. Liek others have said if you can’t automate the process a paid certificate buys you 12 months at a time in validity. Also wildcard certificates are more difficult to do automated with let’s encrypt. If you want EV certificates (where the cert company actually calls you up and verifies you’re the company you claim to be) you also need to go the paid route

    In my experience trustworthyness of certs is not an issue with LE. I sometimes check websites certs and of I see they’re LE I’m more like “Good for them”