You are right it seem to be wireguard related issue. I can indeed access reverse proxy like this. I was able to find this post. But it didn’t help. It seems to be close. I need to somehow redirect traffic to 10.13.13.3 which is address of wireguard container in wireguard network (nothing to do with docker) and which I use to access reverse proxy via vps.
What I can do is somehow access reverse proxy from local network when address is resolved, but the proxy doesn’t redirect. Which is weird. (hostnames are resolved on router in local network)
curl -I http://jelly
HTTP/1.1 307 Temporary Redirect
Server: nginx/1.25.3
Date: Sun, 29 Oct 2023 16:41:17 GMT
Connection: keep-alive
X-Powered-By: Express
Location: /login
jelly resolves to 192.168.0.22
curl -I http://192.168.0.22
<timeout>
curl -I http://service1.jelly
<timeout>
curl -I http://service2.jelly
<timeout>