Yep, this is CURLE_COULDNT_RESOLVE_HOST.
What are you using as DNS servers?
List below this are from my Local Network, where the application it works as we expect:
dns1.rcs-rds.ro
dns2.rcs-rds.ro
vladurzica@MacBook-Pro---Vlad src % scutil --dns
DNS configuration
resolver #1
nameserver[0] : 193.231.252.1
nameserver[1] : 213.154.124.1
if_index : 6 (en0)
flags : Request A records
reach : 0x00000002 (Reachable)
Unfortunately I can’t find any settings regarding my DNS from the Cellular Carrier provider.
Tested on IOS with 1.1.1.1 by Cloudflare - and the app works fine.
So just to clarify, you can use 1.1.1.1 with the app over cellular? That should work, as far as I know, when a provider is being annoying and blocking/interfering.
Yes! The 1.1.1.1 with app over cellular is working fine!
I’m uncertain if the problem lies with the Cellular provider, but I came across a forum discussion where someone reported DNS issues three days ago on the provider’s forum.
1 Like
Awesome, glad to hear. I’ve heard of cellular providers blocking Plex via port, wouldn’t be surprised to hear they were also doing so using DNS.
I’m actually slightly confused about why we’re even using DNS here, the app has countermeasures to avoid this sort of thing and I think we can make an improvement for the next release.
Thank you Elan! For sure there can be a fix because Plex App is working fine and I asume the same API is called in order to retrieve metadata and music from the server. I am glad to help at testing if is necessary.
I think the key issue is that it’s a private IP you’re getting, and we skip the resolution for private IPs (at the moment).
Edit: We skip the manual resolution for non-private IPs because it was causing issues on Android in some cases (IPv6 related).
I don’t know the backend implementation details, but it would be great if the app could detect whether it’s an IPv6 or IPv4 and generate the URL accordingly.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
