-
-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support self-signed TLS certiticate on HTTP component #95
Comments
try mkcert and it will be accepted as valid in your system |
Hi @lotyp |
@mortymacs would an approach similar to https://forfuncsake.github.io/post/2017/08/trust-extra-ca-cert-in-go-app/ work? |
@sbaeurle I was thinking the same to use
What's your idea? |
Probably a good approach, what kind of formats would you expect for each argument? |
We're looking for something like: this https://gist.github.com/michaljemala/d6f4e01c4834bf47a9c4 |
Looks like a good approach! |
It should be append in the system root store by using |
So, would you like to send a PR or I send it? |
I can take a look at it. I'm probably quite booked this week, but next week looks promising and I will try to adjust the certificate handling then :) |
@sbaeurle awesome! |
Today tried to use wait4x on my local domains, like https://router.docker, or https://auth.wod.docker But, in browser, I can open these domains: I'm using traefik locally, with mkcert I have macos Ventura 13.0.1 Interesting, that if I try, shipped curl with macos, it works and can access domains: I'm wondering, is this related to custom SSL certs ? Currently, can't use wait4x to ping services using http |
@vbnetadmin please add PS. logs in text format are better than screenshots, so we can copy and compare it more easily |
Output: Wait4X with debug
Ping:
Brew curl:
macOS default curl:
|
Hi Patrick, This is the DNS problem. Wait4x tries to lookup the domain via |
➜ dig router.docker @100.64.0.2 ; <<>> DiG 9.10.6 <<>> router.docker @100.64.0.2 ;; QUESTION SECTION: ;; Query time: 35 msec |
I'm using dnsmasq on my mac, and my ansible role https://github.com/wayofdev/ansible-role-dnsmasq to setup dns on mac machines. ➜ cat /etc/resolver/docker ➜ pwd ➜ cat dnsmasq.conf |
So, as it says, it couldn't fine anything.
Well, this issue is not related to Wait4X, but, in order to address your issue, we need to know how do you run Wait4X? by Docker or binary on your local machine? |
@mortymacs tried locally using binary and through docker (in separate image) ➜ which wait4x Quick result, using docker image:
But, as you can see, using docker image for wait4x, it shows proper IP address As a workaround, temporarily I can compile wait4x inside keycloak container (where I need to check for readiness) Update: Ok, this looks more promising, by adding flag --net=host I get this result: ➜ docker run --rm --net=host --name='wait4x' |
Temporary, working solution docker-compose.yaml:
Makefile:
Result: ➜ make _kc-wait Btw, wait4x does not work, if container port of target isn't statically exposed:
➜ make _kc-wait docker compose ps |
@vbnetadmin I'm not sure if you understand networking and docker correctly (see https://docs.docker.com/network/). Your first approach using a docker container and the localhost address may never work per default (since each container usually has it's own virtual network adapter). If instead of 127.0.0.1 you would use the actual address of the service/host you want to check (either the IP address or the compose service name) then wait4x would be able to find a route to the service and verify it. |
@vbnetadmin, If you can't fix the problem, you can use the |
No description provided.
The text was updated successfully, but these errors were encountered: