🇨🇦

  • 11 Posts
  • 213 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle
  • Thanks. That seems to be a similar, but slightly different error. I think the below may apply though.

    I believe I’ve tracked down more of my issue, but fixing it is going to be a hassle:

    When cloudflare proxying is enabled, there are 3 DNS records involved; A record with cloudflares ipv4, AAAA record with cloudflares IPV6, and the key to this puzzle: an HTTPS record with cloudflares ech/https config.

    With pihole I can set DNS records for A/AAAA, but I have no way of blocking/setting the HTTPS record so it gets through from cloudflare.

    The LAN A/AAAA records don’t match the HTTPS record from cloudflare, so browsers freak out.

    Once I disabled cloudflares proxying, I no longer get HTTPS records returned and all works as intended.

    I’ll either have to keep cloudflare proxying disabled, or switch pihole out for a more comprehensive DNS solution so I can set/block HTTPS records :(

    Thank you @bobslaede@feddit.dk for pointing me in the right direction.


  • That unfortunately did not work. I am only getting the ipv4 address now, but I still get the same ECH error in chrome 1/5 tries.

    Firefox now changed errors from ‘invalid certificate’ to ‘connection is insecure but this site has HSTS’ (true). Still wont show the cert or provide any further info. (forgot to grab a screenshot before the below ‘solution’)

    I’m really annoyed at this point and have just disabled cloudflare proxying for this service. That seems to have sorted it for all browsers. I may look further later, I may just say fuck it and leave it like this. Gotta walk away for a bit.





  • I do have external acces to Ombi via cloudflare; but the device I’m seeing this problem on is permanently connected to a VPN hosted from the same server machine as ombi/nginx with ‘block all connections without VPN’ enabled. And this testing has been done from within the same LAN.

    It should never see/reach cloudflare for this service.

    /edit; I’ve also disabled ‘use secure DNS’ in chrome. I host a local DNS within that lan/vpn network.






  • I tend to just use FolderSync myself. To avoid battery issues, I have a schedule for most folders; but my DCIM/Pictures folders sync immediately upon changes. I then have a widget on my homepage that triggers a ‘sync all’. Anytime I need files synced immediately, it’s easy enough to click that button.


  • Darkassassin07@lemmy.catoSelfhosted@lemmy.worldServer monitor android widget
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    edit-2
    9 days ago

    Just this week, I setup Homepage to monitor my server and its various docker containers at a glance, including cpu/ram/network usage and a whole bunch of information pulled from their APIs (such as how many itemes are actively downloading via sonarr+sabnzbd, or how many queries were blocked by pihole today).

    That in turn lead me too Glances, both as various widgets in Homepage as well as a stand alone tool.

    Note: Homepage doesn’t come with authentication. You’ll have to handle that yourself via a reverse proxy or vpn. Glances has an optional login page you can enable, but I haven’t explored that. I access services like these by connecting to my network through OpenVPN.


  • Find a problem they are experiencing and introduce them to a solution they can self-host to fix it. Expand from there.

    I began my self-hosting journey 7ish years ago with media piracy and a desire to watch/access my files wherever I was. Learned of Plex, then Emby, Reverse Proxies, Domains, SSL, and on and on…

    Today I’m running 24+ docker containers and some miscellaneous stuff, across 3 systems; that’s always accessible via my domain/vpn.


  • what does not work:

    • i can not ping server.local (- for testing i have to stop the systemd-resolved.service to run the dnsmasq server, or else there are port collisions, but that should not be the problem i guess. I am happy to hear your solution :))
    • i can also not use ssh to log in to server.local, ip address works

    Have you added “server.local” as a DNS record in your dnsmasq container, pointing to your servers LAN IP? Sounds like dnsmasq isn’t resolving that name, which would lead to both of these ‘failures’.




  • Darkassassin07@lemmy.catoSelfhosted@lemmy.worldDNS?
    link
    fedilink
    English
    arrow-up
    13
    ·
    15 days ago

    Why not both?

    My primary DNS is pihole on a rpi dedicated to the task; but I run a second instance of pihole via my main docker stack for redundancy. Should one or the other be unavailable, there’s a second one to pick up the slack.

    I just provide both DNS IPs to LAN clients via DHCP.

    Gravity Sync is a great tool to keep both piholes settings/records/lists in sync.



  • I work warehousing; no IT background, I just like to tinker with whatever. Have since I started breathing.

    I was a fairly casual pirate, grabbing movies/shows I couldn’t find elsewhere (or just couldn’t afford). Got into Plex/Emby for my first real exploration into self-hosting (if you don’t count SRCDS and/or Minecraft Server at like 13yo); and expanded my knowledge from there. Reverse Proxys, the ‘arrs’, DNS, Docker, VPNs, etc.

    Now a days, I’ve got 20+ services that I mostly access via a VPN I host, and I’m always interested in messing with new things :)