• 2 Posts
  • 14 Comments
Joined 6M ago
cake
Cake day: Mar 03, 2024

help-circle
rss

I’m referring to docker bridge networks. old_main is in the 10.2.1.0/24 subnet and i’m trying to move everything to a new bridge network on a subnet of 10.0.0.0/24. sorry, i’m not exactly sure what other info would be useful


Docker network internet access
Hey all! I'm having an issue that's probably simple but I can't seem to work it out. For some history (just in case it matters): I have a simple server running docker and all services being defined in docker-compose files. Probably doesn't matter, but I've switched between a few management UIs (Portainer, Dokemon, currently Dockge). Initially, I set everything up in Portainer (including the main network) and migrated everything over to Dockge. I was using Traefik labels but was getting a bit annoying since I tend to tinker on a tablet. I wanted something a bit more UI-focused so I switched to NPM. Now I'm going through all of my compose files and cleaning up a bunch of things like Traefik labels, homepage labels, etc... but I'm also trying to clean up my Docker network situation. My containers are all on the same network, and I want to slice things up a little better, e.g. I have the Cloudflared container and want to be selective about what containers it has access to network-wise. So, the meat of my issue is that my original network (call it `old_main`) seems to be the only one that can access the internet outbound. I added a new network called `cloudflared` and put just my Cloudflared container and another service on it and I get the `1033 ARGO Tunnel` error when accessing the service and Cloudflare says the tunnel is down. Same thing for other containers I try to move from `old_main`, SearXNG can't connect, Audiobookshelf can't search for author info, etc... I can connect to these services but they can't reach anything on the web. I have my docker daemon.json set to use my Pi-hole for DNS and I only see my services like `audiobookshelf.old_main` coming through. I also see the IP address of the `old_main` gateway coming into Pi-hole as `docker-host`. My goal is to add all of my services to new, more-specific networks then remove `old_main` but I don't want to drop the only network that seems to be able to communicate with the web until I have another that can. I'm not sure what else to look for, any suggestions? Let me know if you need more info.
fedilink

That makes sense, except Google kinda does the same thing. Everything they have is technically just a “free tier” of the Google One subscription, right? I guess I’m saying that “free tier of paid product” doesn’t automatically qualify a company as trustworthy for me. Is there something else that sets Cloudflare apart?


Why does Cloudflare get a pass on the “if it’s free, you’re the product” mantra of the self-hosting community? Honest question. They seem to provide a lot for free, so…


I’m doing something similar (with a lot less data), and I’m intending on syncing locally the first time to avoid this exact scenario.


I’ve been looking around for notes apps with similar criteria with the addition of a portable format (markdown prferably) and, ideally, the ability to add images directly from the camera. I landed on GitJournal and backed it with a self-hosted Forgejo server, but this can be any git server. This has the benefit of requiring an ssh key pair for access


If you have NextCloud, you can try Deck. I moved off from NextCloud and Deck was, oddly enough, one of the harder apps to replace. I ended up with Vikunja. They have an android app in alpha but it feels pretty polished


When I turn off Wi-Fi, I’m not on the same network as my server, it’s my carrier network so all the internet hops are expected.

The way it’s working now is I have a domain (example.com) that is set up on cloudflare DNS. I added a tunnel in cloudflare zero trust, which generates certificates you add to your server to encrypt traffic from your server to cloudflare. I have added these to traefik to be served with my service url (service.example.com). Then, I added a route in cloudflare for service.example.com.

This works fine. But, what I’ve also done is add a local DNS entry for service.example.com so when I’m on my LAN, I access it without going out to the internet and back (seems like a waste). However, this is serving the origin server certs from cloudflare, which causes trust issues

I’m using docker for everything: traefik, cloudflared tunnel, and my services on the same hardware. The tunnel just runs, and it’s configured on cloudflare zero trust to talk directly to the container:port over the docker network.


That’s what I’m settling on. However, it’s not just about trust, some of the services I’m exposing deal with moving files and I’m mostly interested in higher speeds associated with local transfers as well as not using up my internet data cap.


You’re right, I’m using the cloudflare DNS challenge to get let’s encrypt certs. I’m definitely hitting traefik. I’m testing by turning the Wi-Fi on my phone off/on and opening the page after. I get the same cert every time but it’s not trusted when on Wi-Fi. This makes sense since it’s the origin server cert which is meant to encrypt traffic between my server and cloudflare. To add more certainty, when Wi-Fi is on, a traceroute shows only one hop to my server and shows a bunch of hops when it’s off.


Barring any Traefik tricks that allows me to accomplish what I’m after, I was thinking of going with your “third” option of just letting it use Cloudflare for everything but, I had to check with the experts first before just doing it.

I have some apps that complain or, in one case, flat out doesn’t work if the cert is invalid. I’ve been working around it (sort of) but it would be nice to have it set up “correctly” for once. If routing all traffic through Cloudflare is the answer, so be it ¯_(ツ)_/¯


If I use the Cloudflare origin server certs, the browser shows insecure and the message is “certificate not trusted” which is the same message as self-signed, if I’m not mistaken. I’m not sure what other details are relevant as I’m still new-ish to the networking portion of this home server thing. I’m happy to answer any questions if you suspect something.


I’m not using self-signed anymore, I’m getting them from Cloudflare via DNS challenge


Traefik conditional certificate for same URL
Hey all! I have a bunch of services running on my home server and was looking to expose some of them publicly via Cloudflare tunnel. This is done and working great using the origin server certificate and strict TLS. Up until now, I've been using self-signed certs internally but now I don't want to deal with the "proceed anyway" crap on browsers. I have Traefik set up to get certs from Cloudflare using DNS challenge and that *seems* to be working. So, now my problem is: how do I switch between these certificates for the same URL when I'm internal vs public? I'd rather keep that traffic local if I'm at home, which is also working, I just can't figure out how to get Traefik to use the appropriate certificate depending on if the request is coming from my LAN or Cloudflare. Any suggestions? Is there a better way to accomplish what I want to do? EDIT: Looks like I'm just going full Cloudflare on this one, thanks for your help everyone!
fedilink

My guess is they’re referring to these release posts with zero detail.

“KelmRigger new release!” means nothing to anybody that’s never heard of it. At least add a sentence to say what it is rather than make everyone go look it up.


I needed something dead-simple to keep homelab documentation. If it’s not simple, I probably wouldn’t keep up with changes. I landed on An Otter Wiki https://github.com/redimp/otterwiki