For me it did get better but that thought (that I was never fully on board) may always be in the back of your mind.

We have 2. I was mostly up for it the first time but still had a lot of time in the first few months (for both kids) where, if I were typing my experience out, I also would have had to reassure people I was not violent. Very shortly after our second was born I got a vasectomy, which gave me some peace of mind.

The first 3 months were really rough for me, and then the next 3 were a little easier, and after 6 months they become humans and are a bit more interesting. Around a year when they start walking, and especially when they start talking a bit later it can be a lot of fun. But not all of it; there will still be incredibly frustrating moments where you’ll wonder why you got into it at all (which is obviously true of nearly anything).

So it does get better, especially once they get beyond the potato stage, and right now you just have to keep them - and yourself - alive (which isn’t too difficult, thankfully).

Yeah, I've tried the 100.x.x.x IP and their tailscale URLs, neither of which work.

Some places will say nutrient deficiency (Ca) but mine have done that and the issue was largely solved by more water.

Then follow the third, undrawn track (I find a lot of Christian questions come with false dichotomies): let the church die out (ETA if those are the only two other options… I realize where I am).

We can say queer people deserve to be treated humanely AND women deserve to be treated humanely. It’s not either/or.

That's what I was counting on! Guess I just have to look at it as a learning opportunity.

Sorry for misformatted code.

  tailscale-authkey1:
    image: tailscale/tailscale:latest
    hostname: myhost
    environment:
      - TS_AUTHKEY=xx
      - TS_STATE_DIR=/var/lib/tailscale
      - TS_USERSPACE=false
      - TS_EXTRA_ARGS=--advertise-exit-node,--accept-routes
      - TS_ROUTES=192.168.0.0/24
    volumes:
      - ts-authkey-test:/var/lib/tailscale
      - /dev/net/tun:/dev/net/tun
    cap_add:
      - NET_ADMIN
      - SYS_MODULE
    restart: unless-stopped
  nginx-authkey-test:
    image: nginx
    network_mode: service:tailscale-authkey1

Yes, I'm using this container: https://github.com/... using the compose file as written (except I'm naming it nginx instead of app). It maps ports 80 and 443 for traffic and 81 for the manager, which is running.

Part of the idea here is to get comfortable with what's happening here in a safe/unexposed environment before trying something that I would expose to the internet, and I'm of the understanding that you can do it this way (pass it to the internet, which will then return that internal IP that Nginx should route appropriately.

I know this is a week old, but thanks for your input. I hadn't seen Avahi before, and that's a cool option, so thanks for sharing it. Part of why I wanted to do things this way was an excuse to practice with running a web server before setting up Foundry, so it's mostly just testing things out. Of course, if it was just a regular web server, I wouldn't have had this issue because DNS rebind protection on my router ended up being the problem.

Thanks, I did check that my machine had IP forwarding enabled, and it does. I also ran those lines to create the config file as well, but that didn't change anything. And I do have the lines in my compose file to advertise routes.

No, I thought the routing was to forward the IP from the Tailscale 100.x.x.x subnet(? not sure I'm using that word correctly) to where the resources I want to access are (in my case, my local 192.168 addresses).

Yes, the machine that is running Docker/Tailscale is serving as an exit node and it hosts all the other services I want to access, which are also in containers.

Misery loves company! Mine is Verizon and there was a setting that was causing me trouble recently, but probably is unrelated to yours (was DNS rebind protection).

LXC

Yes, it does (been checking with sysctl net.ipv4.ip_forward, but guess it's the same thing). It seems like the issue may be that IPv6 may not be enabled within the container. It's enabled on the host, but the docker logs say ipv6 forwarding is not enabled.

I'm still very much in a learning mode here, so forgive my ignorance - which logs? Nginx? I'm seeing a fallback_error and fallback_access (which has nothing interesting). There are also some empty files for the host I have set up (proxy-host-1_access/error)

2025/09/01 12:34:54 [error] 193#193: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.181, server: nginxproxymanager, request: "GET /api/ HTTP/1.1", upstream: "http://127.0.0.1:3000/", host: "192.168.1.196:81", referrer: "http://192.168.1.196:81/nginx/certificates"

Where, presumably obviously, 196 is the server and 181 is a laptop. FWIW I don't see the directory it's mentioning, /nginx/certificates, but I'm looking at the host's directory rather than in the container.

Yeah, i agree that could be helpful, but if OP is already feeling like they’re not able to do what they want to then it may be a stretch to add (and coordinate their, their partner’s, both parties’ work if in the US, and potentially a sitter’s schedules) may be asking too much.

At that age, there is almost certainly a lot of exhaustion (which doesn’t do great things for apathy itself) so I’m sure thats a part of it.

Yes, I believe I made the stupid mistake of not restarting after enabling. Once I did that the warning went away and I was able to enable subnets, but I'm still not able to see my local services (where I try to access via the IP of the host given by Tailscale or the magicDNS address). So, progress!

ETA: I also had removed the advertise exit nodes line and restarted the container with the --reset flag. After the warning went away I re-added the exit node option and I get the warning that it is misconfigured again.

It's true, and I was wondering if that would be the route I have to go. Good to know it has been a positive experience.

That was an interesting rabbit hole. I'm not sure if it's related or not, but maybe I'll give it a shot once I get my head wrapped around what it really means (though by then they might have developed a fix... and I see how long that's taken so far)