Windows 10 will reach EOS (end of support) on October 14, 2025. For more information, see this article.

Avatar for Username

Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

DNS resolution failure/timeout

  • Няма отговори
  • 0 имат този проблем
  • 1 изглед
lists14
lists14
more options

Since updating to v144.0.1 (distributed via Google Play) on OnePlus 5 with stock Android 10 (OxygenOS 10.0.1) Firefox initially performs as expected, but after a few days displays the 'connection has timed out' message when trying to access any URL (after a delay of around 45 seconds).

Issue occurs regardless of device connection to WiFi / cellular, other apps on the device have no issues with connectivity in both cases. PCAPDroid captures show DNS requests to the Android system resolver 10.215.173.2 with responses as expected, but no HTTP/HTTPS connections.

The issue persists across force stop, device restart, and clearing but is resolved by uninstalling and reinstalling until it recurs a few hours later. Issue also observed with beta build 145.0b7, but not yet seen using either Fennec 144.0.0 (Build #1440020) GV: 144.0-20251022155017 or with Nightly 146.0a1 (Build #2016122871), 6488d90a06c0b99c9f7000b8c0763c4f44253912, GV: 146.0a1-20251028041839

Since updating to v144.0.1 (distributed via Google Play) on OnePlus 5 with stock Android 10 (OxygenOS 10.0.1) Firefox initially performs as expected, but after a few days displays the 'connection has timed out' message when trying to access any URL (after a delay of around 45 seconds). Issue occurs regardless of device connection to WiFi / cellular, other apps on the device have no issues with connectivity in both cases. PCAPDroid captures show DNS requests to the Android system resolver 10.215.173.2 with responses as expected, but no HTTP/HTTPS connections. The issue persists across force stop, device restart, and clearing but is resolved by uninstalling and reinstalling until it recurs a few hours later. Issue also observed with beta build 145.0b7, but not yet seen using either Fennec 144.0.0 (Build #1440020) GV: 144.0-20251022155017 or with Nightly 146.0a1 (Build #2016122871), 6488d90a06c0b99c9f7000b8c0763c4f44253912, GV: 146.0a1-20251028041839

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.