-
Notifications
You must be signed in to change notification settings - Fork 712
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
Connection refused on Termux #169
Comments
wgcf does not currently support Android. For a workaround that may or may not work, check: #31 (comment) Otherwise, closing in favor of #79 |
Thanks for answer, I think my Google is broken cause I tried to search but found nothing. There is a working non-root solution for Termux by Saito.Alex from 4PDA. |
@ViRb3 Please just offer a way for users to define a custom DNS server. That will solve the problem without any further complications. It just makes no sense to pin on |
@PoneyClairDeLune Unless I'm missing something, wgcf does not have any code that selects or pins the DNS server? It is all resolved via the OS. As far as I recall, this is a known issue where a binary compiled for Linux and then ran on Android has issues with the networking stack. Sure, we could add hacks to override that, but it would be better to just properly compile wgcf for Android instead. Happy to take PRs on that. |
I solved this problem without installing
After building in termux wgcf working fine! |
I'm using arm64 prebuilt binary in Termux and getting this:
~/wgcf $ ./wgcf_2.2.12_linux_arm64 register 2022/03/18 13:29:10 Using config file: wgcf-account.toml This project is in no way affiliated with Cloudflare Cloudflare's Terms of Service: https://www.cloudflare.com/application/terms/ ✔ Yes 2022/03/18 13:29:11 Post "https://api.cloudflareclient.com/v0a1922/reg": dial tcp: lookup api.cloudflareclient.com on [::1]:53: read udp [::1]:49078->[::1]:53: read: connection refused
On my Windows laptop with same WiFi spot wgcf working properly. What possibly can be wrong?
The text was updated successfully, but these errors were encountered: