My g3proxy http_rproxy example using docker containers #493
Replies: 6 comments 12 replies
-
|
You need to use https://github.com/bytedance/g3/blob/master/g3proxy/examples/simple_http_gateway/g3proxy.yaml this as an example HTTP reverse proxy config. The You need to mount your g3proxy.yaml config file or config dir when start the docker container, and change the entry command to |
Beta Was this translation helpful? Give feedback.
-
|
The g3proxy container has a http_proxy server, which is a forward proxy mode server, you can test it with I think you need to expose the ports in g3proxy container to the host, so you can run it from the host. I will try this when I have some free time. |
Beta Was this translation helpful? Give feedback.
-
|
I checked out I will test something from chatgpt like shown below in a little bit. Thank you for the information regarding curl and configuring up a network. I can't wait to test that out.g3proxy.yamldocker networkdocker web-appdocker run g3proxy |
Beta Was this translation helpful? Give feedback.
-
|
The g3proxy.yaml file can be changed to: log: stdout
resolver:
- name: default
type: c-ares
server: 127.0.0.1
escaper:
- name: default
type: direct_fixed
no_ipv6: true
resolve_strategy: IPv4Only
server:
- name: test
escaper: default
type: http_rproxy
listen: [::]:8080
hosts:
- exact_match: my-web-app.local
upstream: my-web-app.local:80
resolver: default
escaper: defaultMake sure the DNS server set in |
Beta Was this translation helpful? Give feedback.
-
|
I did try your example. And as you pointed out in the link, DNS services it is an issue with the my the docker DNS "resolver.conf" not correctly pointing to my Docker service. Which I'm working out next after several attempts below trying to avoid looking at this. *edit: |
Beta Was this translation helpful? Give feedback.
-
|
try this with the latest code: log: stdout
resolver:
- name: default
type: c-ares
escaper:
- name: default
type: direct_fixed
no_ipv6: true
resolve_strategy: IPv4Only
server:
- name: test
escaper: default
type: http_rproxy
listen: [::]:8080
hosts:
- exact_match: who.landingdev.xyz
upstream: who.internal:80
resolver: default
escaper: default |
Beta Was this translation helpful? Give feedback.
-
|
Thank you, you solved my problem. I was on a tangent with assigning IPs, I haven't tested your better solution yet, it appears cleaner than what I used below. I will keep experimenting and learning more about G3Proxy and integrating it with Docker. I have a lot of use cases I want to test out. I consider this solved. |
Beta Was this translation helpful? Give feedback.
-
|
I believe I got it using This configuration is likely not compose.ymlmy_g3proxy.ymldocker pscurl who.landingdev.xyz:8080client same as hostremote clientdocker compose upfiles |
Beta Was this translation helpful? Give feedback.
-
|
I have my I haven't tried removing I can also probably remove the dedicated IPs also This still doesn't feel *PS: sorry for commenting on this closed thread compose.ymlmy_g3proxy.ymldocker compose upcurl who.landingdev.xyz:8080 |
Beta Was this translation helpful? Give feedback.
-
|
Ok, this I think the whole time I only needed to include whatever was my docker named network compose.ymlnetworks:
g3w-net:
services:
g3proxy_w:
image: g3proxy/comp:g3
build:
context: ./g3
dockerfile: g3proxy/docker/debian.Dockerfile
networks:
- g3w-net
ports:
- "8080:8080"
volumes:
- .:/g3/
command:
-c /g3/my_g3proxy.yml
who:
image: traefik/whoami
hostname: who # <-- this also can be removed, leaving for logging
container_name: who.internal # <-- this also can be removed
networks:
- g3w-netmy_g3proxy.ymllog: stdout
resolver:
- name: default
type: c-ares
server:
- 127.0.0.11
escaper:
- name: default
type: direct_fixed
resolve_strategy: IPv4Only
resolver: default
server:
- name: g3proxy
escaper: default
type: http_rproxy
listen:
address: 0.0.0.0:8080
hosts:
- exact_match: who.landingdev.xyz
# upstream: who:80 #<-- also works
upstream: who.internal:80curl who.landingdev.xyz:8080docker compose up |
Beta Was this translation helpful? Give feedback.
-
|
can you try: resolver:
- name: default
type: c-ares
#server: --> delete this and use default address in /etc/resolv.conf
# - 127.0.0.11I think that the containers are in a connected network by default, so you can also try to delete that g3w-net definition. |
Beta Was this translation helpful? Give feedback.
-
|
I knew removing the However, changing the I'm learning about I was looking at what Docker's domainname was used for to find that it is for compose.ymlservices:
g3proxy_w:
image: g3proxy/comp:g3
build:
context: ./g3
dockerfile: g3proxy/docker/debian.Dockerfile
ports:
- "8080:8080"
volumes:
- .:/g3/
command:
-c /g3/my_g3proxy.yml
who:
image: traefik/whoami
hostname: who
container_name: who.internalmy_g3proxy.ymllog: stdout
resolver:
- name: default
type: c-ares
# server: 127.0.0.53 # <-- This gives me `530 Origin DNS Error`
server: 127.0.0.11 # <-- This works
# server: # <-- This works also
# - 127.0.0.11
escaper:
- name: default
type: direct_fixed
resolve_strategy: IPv4Only
resolver: default
server:
- name: g3proxy
escaper: default
type: http_rproxy
listen:
address: 0.0.0.0:8080
hosts:
- exact_match: who.landingdev.xyz
# upstream: who:80
upstream: who.internal:80
curl who.landingdev.xyz:8080docker compose upDocker's g3proxy/comp:g3 /etc/resolve.confVPS Hostinger's /etc/resolve.conf |
Beta Was this translation helpful? Give feedback.
-
|
It seems that the /etc/resolv.conf file in the container is mounted at start and it's correct. What I means is that you can just use resolver:
- name: default
type: c-areswithout set the DNS server address manually, and then g3proxy will read the /etc/resolv.conf file in the container and get the correct DNS server address from there, which will make the config file more portable. |
Beta Was this translation helpful? Give feedback.
-
|
When I do not have a resolver:
- name: default
type: c-aresI noticed in the examples that sometimes a root@server:~/dn# docker exec -it 6a30 bash # <-- my running g3proxy docker instancedocker compose upmy_g3proxy.ymllog: stdout
resolver:
- name: default
type: c-ares
# server: 127.0.0.11
# server: 127.0.0.53
# server:
# - 127.0.0.11
escaper:
- name: default
type: direct_fixed
resolve_strategy: IPv4Only
resolver: default
server:
- name: g3proxy
escaper: default
type: http_rproxy
listen:
address: 0.0.0.0:8080
hosts:
- exact_match: who.landingdev.xyz
# upstream: who:80
upstream: who.internal:80compose.ymlservices:
g3proxy_w:
image: g3proxy/comp:g3
build:
context: ./g3
dockerfile: g3proxy/docker/debian.Dockerfile
ports:
- "8080:8080"
volumes:
- .:/g3/
command:
-c /g3/my_g3proxy.yml
who:
image: traefik/whoami
hostname: who
container_name: who.internal |
Beta Was this translation helpful? Give feedback.
-
|
this is a new feature I added recently, so you need to rebuid the docker image to the latest commit |
Beta Was this translation helpful? Give feedback.
-
|
Works! and is I did a complete prune of docker, including the buildx cache. And I restarted twice to confirm Everything still works, just an anomalous entry in the log file type I get this in my Filescompose.ymlservices:
g3proxy_w:
image: g3proxy/comp:g3
build:
context: ./g3
dockerfile: g3proxy/docker/debian.Dockerfile
ports:
- "8080:8080"
volumes:
- .:/g3/
command:
-c /g3/my_g3proxy.yml
who:
image: traefik/whoami
hostname: who
container_name: who.internalmy_g3proxy.ymllog: stdout
resolver:
- name: default
type: c-ares
escaper:
- name: default
type: direct_fixed
resolve_strategy: IPv4Only
resolver: default
server:
- name: g3proxy
escaper: default
type: http_rproxy
listen:
address: 0.0.0.0:8080
hosts:
- exact_match: who.landingdev.xyz
# upstream: who:80
upstream: who.internal:80docker psdocker compose upcurl who.landingdev.xyz:8080 |
Beta Was this translation helpful? Give feedback.
-
|
It's a bug introduced yesterday, and it will be fixed in this PR: #553. |
Beta Was this translation helpful? Give feedback.
-
|
All set, grabbed the latest commit. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
How do I make a reverse proxy with g3?
Your documentation is very good but my cave man literacy level is lower than any other recorded caveman.
I understand some caveman technology and I can often make other rocks that cavemen use work. I usually see how the other cavemen smash rocks and then repeat their rock smashing actions with my own rocks.
But these rocks look a little different than what this caveman encountered seeing other caveman use and is not getting an immediate fire in his cave.
How do I smash these rocks together to make a reverse proxy?
Caveman first procured the rocks like so.
And this Caveman then sees that his rocks are indeed in his cave now.
Caveman then poked the rock and not smash the rock yet to verify it is a working rock.
Caveman now wants to use his rock on his VPS I mean Cave to point from the entrance of his cave to another
special rock in his cave whenever someone enters his Cave.
Caveman is not good with "words" and wants to see rocks!
I think this is the cave pit that I need to use for the "whoami" reverse-proxy
Beta Was this translation helpful? Give feedback.
All reactions