I joined Lemmy back in 2020 and have been using it as qaz@lemmy.ml until somewhere in 2023 when I switched to lemmy.world. I’m interested in systemd/Linux, FOSS, and Selfhosting.

  • 35 Posts
  • 311 Comments
Joined 2 years ago
cake
Cake day: June 10th, 2023

help-circle


  • qaz@lemmy.worldOPtoSelfhosted@lemmy.worldIt was DNS, but how?
    link
    fedilink
    English
    arrow-up
    1
    ·
    4 days ago

    Thanks for the advice. I also use a cheap domain with a wildcard, but use nginx instead. I just tried using Adguard and although it’s fascinating to see the insights of all the DNS requests, it didn’t really help fix the issue. However, since using DoH with Cloudflare in combination with setting it to the specific IP instead of my local device name and have 100% uptime now (since the last 10 minutes that is).



  • qaz@lemmy.worldOPtoSelfhosted@lemmy.worldIt was DNS, but how?
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    4 days ago

    Uptime Kuma seems to use nscd for caching internally and the default system DNS resolver. I’ve added a custom DNS resolvers to Uptime Kuma, and apparently it can get the records from Cloudflare (1.1.1.1) but it can’t get it from the OpenWRT router (192.168.1.1). 🤔

    I’ve enabled a proxy on the router to force the use of DoH, maybe that will help if the ISP’s modem is at fault.









  • Yes, but if you care about power efficiency then they really aren’t a great option. Most professional server hardware that you can get for a decent price uses significantly more power than an old mini computer or a cheap N100 PC. I own a proliant but rarely power it on due to the fact that I could rent an similarly performant VPS for 2x the power bill. Besides that many server CPU’s don’t have integrated GPU’s and will require additional hardware if you want to run something like Jellyfin.



  • It’s further than you think. I spoke to someone today about and he told me it produced a basic SaaS app for him. He said that it looked surprisingly okay and the basic functionalities actually worked too. He did note that it kept using deprecated code, consistently made a few basic mistakes despite being told how to avoid it, and failed to produce nontrivial functionalies.

    He did say that it used very common libraries and we hypothesized that it functioned well because a lot of relevant code could be found on GitHub and that it might function significantly worse when encountering less popular frameworks.

    Still it’s quite impressive, although not surprising considering it was a matter of time before people would start to feed the feedback of an IDE back into it.