CallMeDoc
CDCloudflare Developers
•Created by CallMeDoc on 9/30/2023 in #general-help
Can cloudflared egress route to the docker name
Thank you @foutkassir , I'll play with this a bit from the one dashboard. I just need to make sure they are in the same network partition..
5 replies
CDCloudflare Developers
•Created by CallMeDoc on 7/8/2023 in #general-help
Zero Trust - Network
Gotcha... Thanks, I'll give that a try. Appreciate your help
8 replies
CDCloudflare Developers
•Created by CallMeDoc on 7/8/2023 in #general-help
Zero Trust - Network
I'm not sure I follow... but are you saying I should run the cloudflared docker container and specify to use the host network?
docker run -d --network host cloudflare/cloudflared:latest tunnel --no-autoupdate run --token <token> like this?
docker run -d --network host cloudflare/cloudflared:latest tunnel --no-autoupdate run --token <token> like this?
8 replies
CDCloudflare Developers
•Created by CallMeDoc on 7/8/2023 in #general-help
Zero Trust - Network
All things considered, I should be able to route to it. Everything was built using the interface, so I didn't fudge the DNS record by manually setting it up. token should be the same, right?
8 replies
CDCloudflare Developers
•Created by CallMeDoc on 7/8/2023 in #general-help
Zero Trust - Network
The log says: 2023-07-08T19:51:44Z ERR Request failed error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp 127.0.0.1:22000: connect: connection refused" connIndex=3 dest=https://icore.xeven.io/ event=0 ip=198.41.192.77 type=http
8 replies
CDCloudflare Developers
•Created by CallMeDoc on 7/8/2023 in #general-help
Zero Trust - Network
The reason I ask, is trying out the zero trust tunnel, from the browser I can hit http://127.0.0.1:22000 no problem.
8 replies