Very slow access to self-hosted applications through Docker

[francislavoie]

Ahhh I think you’re running into NAT hairpinning issues:

Network address translation

Basically, DNS for your domain is resolved to the WAN IP, then when a request goes out, it reaches your router, then because it likely doesn’t support NAT hairpinning, the connection gets dropped because it doesn’t know to route the request back internally.

Please read through this article to get an idea of how it works:

Using Caddy as a reverse proxy in a home network

If you want to run a service inside a Local Area Network (LAN) such as your home or office – and especially if you want to be able to access it from outside that network – Caddy can help you accomplish this quite easily. This guide will show you how. It assumes you’ve never done this before, but that you have some technical proficiency and are somewhat knowledgable about your own network. Do this at your own risk. There are several ways to make private services accessible from other n…

The solution is typically to also run a DNS server in your home network, to implement split DNS. Basically this means that your local DNS server will resolve your domain to the LAN IP address of your server, instead of the WAN IP address, but when outside of your home network, the domain will still resolve to the WAN IP.

@OursBlanc

Then this is my log (again for the RSS subdomain) .

Those are your access logs, not the Caddy logs. You can see those by running docker logs <name-of-the-caddy-container>.