aarond10
https_client.c:426 EC4A: CURLINFO_OS_ERRNO: 65 No route to host
./build/https_dns_proxy -v
[W] 1707365381.236897 main.c:235 HTTP/3 is not supported by current libcurl
[W] 1707365398.268900 https_client.c:353 EC4A: curl request failed with 0: No error
[W] 1707365398.268937 https_client.c:355 EC4A: curl error message: Failed to connect to dns.google port 443 after 0 ms: Couldn't connect to server
[W] 1707365398.268955 https_client.c:382 EC4A: No response (probably connection has been closed or timed out)
[W] 1707365398.269033 https_client.c:426 EC4A: CURLINFO_OS_ERRNO: 65 No route to host
OS: FreeBSD 14
commit: 8afbba7
Does adding "-x" work? (no HTTP/2 or HTTP/3).
The 0ms timeout is odd. Seems to suggest it couldn't resolve dns.google properly.
Does dig @8.8.8.8 dns.google work for you?
On Thu, 8 Feb 2024 at 15:09, Yonas Yanfa @.***> wrote:
./build/https_dns_proxy -v [W] 1707365381.236897 main.c:235 HTTP/3 is not supported by current libcurl [W] 1707365398.268900 https_client.c:353 EC4A: curl request failed with 0: No error [W] 1707365398.268937 https_client.c:355 EC4A: curl error message: Failed to connect to dns.google port 443 after 0 ms: Couldn't connect to server [W] 1707365398.268955 https_client.c:382 EC4A: No response (probably connection has been closed or timed out) [W] 1707365398.269033 https_client.c:426 EC4A: CURLINFO_OS_ERRNO: 65 No route to host
OS: FreeBSD 14 commit: 8afbba7
— Reply to this email directly, view it on GitHub https://github.com/aarond10/https_dns_proxy/issues/168, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABTOXSI4NHW46EHRKAZDSLYSRFX5AVCNFSM6AAAAABC67DFM2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGEZDIMZSGA4DMMQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Thanks @aarond10
Does adding "-x" work? (no HTTP/2 or HTTP/3).
No, I get the same error.
$ build/https_dns_proxy -v -x
[W] 1707440609.746723 main.c:235 HTTP/3 is not supported by current libcurl
[W] 1707440648.877940 https_client.c:353 1A7F: curl request failed with 0: No error
[W] 1707440648.877976 https_client.c:355 1A7F: curl error message: Failed to connect to dns.google port 443 after 0 ms: Couldn't connect to server
[W] 1707440648.877993 https_client.c:382 1A7F: No response (probably connection has been closed or timed out)
[W] 1707440648.878076 https_client.c:426 1A7F: CURLINFO_OS_ERRNO: 65 No route to host
[W] 1707440653.935986 https_client.c:353 1A7F: curl request failed with 0: No error
[W] 1707440653.936037 https_client.c:355 1A7F: curl error message: Failed to connect to dns.google port 443 after 0 ms: Couldn't connect to server
[W] 1707440653.936059 https_client.c:382 1A7F: No response (probably connection has been closed or timed out)
[W] 1707440653.936095 https_client.c:426 1A7F: CURLINFO_OS_ERRNO: 65 No route to host
[W] 1707440658.988562 https_client.c:353 1A7F: curl request failed with 0: No error
[W] 1707440658.988614 https_client.c:355 1A7F: curl error message: Failed to connect to dns.google port 443 after 0 ms: Couldn't connect to server
[W] 1707440658.988629 https_client.c:382 1A7F: No response (probably connection has been closed or timed out)
[W] 1707440658.988646 https_client.c:426 1A7F: CURLINFO_OS_ERRNO: 65 No route to host
Does
dig @8.8.8.8dns.google work for you?
Yes.
Odd.. Did you build the code from source and what version of curl are you running? (curl -V) Is this in a docker container? Anything odd about the environment?
On Fri, 9 Feb 2024 at 12:03, Yonas Yanfa @.***> wrote:
Thanks @aarond10 https://github.com/aarond10
Does adding "-x" work? (no HTTP/2 or HTTP/3). No, I get the same error.
$ build/https_dns_proxy -v -x [W] 1707440609.746723 main.c:235 HTTP/3 is not supported by current libcurl [W] 1707440648.877940 https_client.c:353 1A7F: curl request failed with 0: No error [W] 1707440648.877976 https_client.c:355 1A7F: curl error message: Failed to connect to dns.google port 443 after 0 ms: Couldn't connect to server [W] 1707440648.877993 https_client.c:382 1A7F: No response (probably connection has been closed or timed out) [W] 1707440648.878076 https_client.c:426 1A7F: CURLINFO_OS_ERRNO: 65 No route to host [W] 1707440653.935986 https_client.c:353 1A7F: curl request failed with 0: No error [W] 1707440653.936037 https_client.c:355 1A7F: curl error message: Failed to connect to dns.google port 443 after 0 ms: Couldn't connect to server [W] 1707440653.936059 https_client.c:382 1A7F: No response (probably connection has been closed or timed out) [W] 1707440653.936095 https_client.c:426 1A7F: CURLINFO_OS_ERRNO: 65 No route to host [W] 1707440658.988562 https_client.c:353 1A7F: curl request failed with 0: No error [W] 1707440658.988614 https_client.c:355 1A7F: curl error message: Failed to connect to dns.google port 443 after 0 ms: Couldn't connect to server [W] 1707440658.988629 https_client.c:382 1A7F: No response (probably connection has been closed or timed out) [W] 1707440658.988646 https_client.c:426 1A7F: CURLINFO_OS_ERRNO: 65 No route to host
Does dig @8.8.8.8 dns.google work for you?
Yes.
— Reply to this email directly, view it on GitHub https://github.com/aarond10/https_dns_proxy/issues/168#issuecomment-1935171068, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABTOXVJ2WODNDJ2X2IV56TYSVYVLAVCNFSM6AAAAABC67DFM2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZVGE3TCMBWHA . You are receiving this because you were mentioned.Message ID: @.***>
Did you build the code from source...
Yes.
...what version of curl are you running? (curl -V)
❯ curl --version
curl 8.5.0 (amd64-portbld-freebsd14.0) libcurl/8.5.0 OpenSSL/3.0.12 zlib/1.3 libpsl/0.21.2 (+libidn2/2.3.4) libssh2/1.11.0 nghttp2/1.58.0
Release-Date: 2023-12-06
Protocols: dict file ftp ftps gopher gophers http https imap imaps pop3 pop3s rtsp scp sftp smtp smtps telnet tftp
Features: alt-svc AsynchDNS GSS-API HSTS HTTP2 HTTPS-proxy IPv6 Kerberos Largefile libz NTLM NTLM_WB PSL SPNEGO SSL threadsafe TLS-SRP UnixSockets
Is this in a docker container?
No, just a FreeBSD 14 virtual machine.
More logs would have been nice with: -v -v -v
Also you could try -4 maybe.
This is the second report for issues with libcurl 8.5.0. I don't know what it could have been, but I am running fine with 8.8.0. Please try to upgrade.