mirror of
https://github.com/yusing/godoxy.git
synced 2026-01-11 21:10:30 +01:00
no matching route for subdomain - docker containers #4
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @earvingad on GitHub (Mar 28, 2024).
compose:
Config file content:
Provider eee.yml:
Panel is working and accessible, hello container is detected but with bad healt:

from inside go-proxy container (ip: 172.27.0.2) the hello contained ip (172.27.0.3) is reachable.
hello container can be accessed through 10.1.1.240:81

And adding a manual provider entry does work, however this should be the automated behavior expected with docker container to avoid manual entries.
log result when running
curl http://hello.neon.lan:Hellocontainer is running and subdomain matches container name and alias. Additionally Firewall is disabled, so I dont know what is wrong.@yusing commented on GitHub (Mar 29, 2024):
There is no docker provider in your config, please add this part back to your config file
into:
@yusing commented on GitHub (Mar 29, 2024):
modify the
valueif you have docker running in other machine@yusing commented on GitHub (Mar 29, 2024):
@earvingad commented on GitHub (Mar 29, 2024):
I have added:
And still can't get it to work, if I don't specify the
ports:section for the container, then go-proxy wont recognize the container exists.Already tested with adguardhome container, needed to specify
ports: -3000:3000or go-proxy wouldnt detect it.This create a conflict with any container that uses any port of which
go-proxyuses: 80. 8080, 443 and 8443.Withouth specify ports:
specifying Ports:
@yusing commented on GitHub (Mar 29, 2024):
Somehow I messed up the port selection function so I won't work starting from 0.4. Now fixed
@yusing commented on GitHub (Mar 29, 2024):
The expected behaviour is:
port - host:container is needed, only when
network_mode: hostis setotherwise, use exposed ports (already declared in Dockerfile of the image most of the time)
or explicity specify
For adguardhome, those are unnecessary as the latest commit fixed.
@earvingad commented on GitHub (Mar 29, 2024):
Yes, now it is working fine!
In the case of adguardhome, port 3000 is just used once during first setup and if not explicitly set the webui at port 3000, the default will be changed to port 80 and webui wont be accessible. As long as you set up webui port to 3000 during first adguardhome set up, everything will be fine.
Finally, to allow DNS querys, port 53 UDP must declared in adguardhome compose block (this is just if anyone have an issue with it):
Everything is working fine! thanks for the support!
@yusing commented on GitHub (Mar 29, 2024):
I think you should either map port to host, or use reverse proxy, but not both.
Could you try this for example?
then in go-proxy:
Finally, set your dns to go-proxy's ip (your case 10.0.1.240? I forgot)
@earvingad commented on GitHub (Mar 30, 2024):
Hello, port seems mapped when adding labels, both adg and adg-setup subdomains work, but the forward request does not seem to work.

Ports:
@yusing commented on GitHub (Mar 31, 2024):
Should work now, also please update compose.yml to use
image: ghcr.io/yusing/go-proxyinstead ofbuild: .😄@earvingad commented on GitHub (Mar 31, 2024):
Yes, I can confirm udp forward is working now!
Thanks for the support!