7fc7bc42-6e0c-449e-92b2-6706b93a0592

is nextjs listening on ipv6? if not, it needs to be as the private network is ipv6 only

but is is working, it just stops working when I redeploy only the nextjs

if it was nextjs ipv6 not listening, it would have never worked

and thank you for your help 🙂

yep that's fair, I didn't hear back so I marked as solved, my apologies.

the issue here is that nginx is using a caching dns resolver, so when you deploy the other service it gets a new ipv6 ip and thus the ip that nginx has in its cache is incorrect and that's where you are getting the error.

the fix for this is to configure nginx to not cache dns, or the better option would be to switch to caddy instead where no extra configurations are needed to disable dns cache.

No problem, it was not urgent and I am between projects

Thanks for your follow up Brody

If you have a template with caddy and with a username password that will work, I am all in

or if we only need a simple nginx to not cache dns, I will try to find something there first

I'll see if I can whip something up for caddy

thanks 🙂

hey, sorry it took me longer than id like to get to this, but i have a working drop in replacement now -

simply fork this, then replace your auth services' source with your fork.

this caddy basic auth now also has a /health-check endpoint you can use to set a health check in the service settings

Wonderful thank you so much. I will try and revert back to you 🙂

sounds good!