-
Notifications
You must be signed in to change notification settings - Fork 508
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
How do I change TLSv1.3 to TLSv1.2 in curl? | onRequestTemporaryError #2573
Comments
Hi, thanks for explaining that you are using AdGuard. Are you using any VPN along with that (but not in the other case?). I can see that in your first example you've connected to MEGA on an ipv4 address, which is normal. And in the second example, the c-ares library is not able to do a DNS lookup to get MEGA's address. You're getting c-ares error 11 back: #define ARES_ECONNREFUSED 11. And when the MEGA library tries to use the hardcoded list of servers, you get "network unreachable". I suspect you have a VPN running which is interfering with the DNS lookups? thanks |
Hi, I appreciate your answer to the problem, the AdGuard application filters the network locally, therefore it does not use any VPN or connects to a remote network, the app asks to install a "CA" certificate to filter HTTPS connections. (All the logs I will provide use network filtering with AdGuard) Regarding the MEGA code, I noticed that the libraries compiled at "https://github.com/meganz/android" do not use OpenSSL: This is the MEGA application for Android (4.0.2) (I am not compiling the code, I just use the application directly from Google Play):
This is the compiled code from: "https://github.com/meganz/sdk/tree/master/examples/android/ExampleApp/app/src/main/jni" (NOTE: I am not using megachat, just code that is already written).
I have noticed several things: When they updated the minSDK for android that would be 21, this problem started, previously I was compiling the libraries equal to or lower than sdk-3.7.1 and without problem, it does not present the problem with the AdGuard application. in the log I see that the dns changes when filtering is used: Using AdGuard: I/AndroiMegaApi: net.cpp: 467: DNS servers: 127.0.0.1 Not using AdGuard: |
Well, I'm not too familiar with android's networking myself, but the change in your DNS address seems to be the root of the problem. 127.0.0.1 is the loopback address, does android even respond to itself for DNS requests like that? From your logs, it would seem not. The other address seems to be your ISP's DNS servers. Perhaps AdGuard has a setting you can change for DNS lookup? |
The mega app also makes the dns change and using AdGuard filtering it works flawlessly:
|
Hello! I have a problem with TLS 1.3 version because it does not work with a VPN that installs a local certificate on the device.
I explain the inconvenience;
In the Mega application for Android (current version 4.0.2) I see in the registry that it uses TLS 1.2 and it works perfectly with an ad blocker (AdGuard). Example:
Whereas if I compile the sdk (recent version) and use the sample libraries for Android and use vpn (AdGuard to remove app ads) it throws me the following error:
I clarify that the libraries that I have compiled work perfectly if I do not use the AdGuard application. (I can use all SDK MEGA without problem).
I have also added this and it doesn't work:
Will there be any settings directly in megaApi that I am missing?
The text was updated successfully, but these errors were encountered: