Occasionally sites won't load after upgrade from Bullseye to Bookworm (Adguard?)

Creating a bug report/issue

I have searched the existing open and closed issues

Required Information

  • DietPi version | G_DIETPI_VERSION_CORE=9
    G_DIETPI_VERSION_SUB=11
    G_DIETPI_VERSION_RC=2
    G_GITBRANCH=‘master’
    G_GITOWNER=‘MichaIng’
  • Distro version | Bookworm
  • Kernel version | Linux DietPi 5.10.103-v8+ #1529 SMP PREEMPT
  • Architecture | arm64
  • SBC model | RPi 4 Model B (aarch64)
  • Power supply used | 5V
  • SD card used | Not sure (hidden in SmartPi 2 case)

Additional Information (if applicable)

  • Software title | Adguard v0.107.59
  • Was the software title installed freshly or updated/migrated? Migrated
  • Can this issue be replicated on a fresh installation of DietPi? Haven’t tried.
    ← If you sent a “dietpi-bugreport”, please paste the ID here →
  • Bug report ID | echo $G_HW_UUID

Steps to reproduce

  1. Enter any URL in browser (Firefox v136.0.4 on MacOS Sequoia 15.3.2)
  2. Most times the browser will connect to the site but about 10% of the time it won’t and I get the message to Try Again.
  3. Trying a few minutes later, it will connect no problem.

Expected behaviour

  • Immediate connection to the site.

Actual behaviour

  • I Get the message:
    Hmm. We’re having trouble finding that site.

We can’t connect to the server at www.newsminimalist.com. (This is one example.)

If you entered the right address, you can:

  • Try again later
  • Check your network connection
  • Check that Firefox has permission to access the web (you might be connected but behind a firewall)

Button: Try Again

Extra details

Probably something you should discuss with AGH developer as we don’t maintain AGH ourselves. As well you can have a look into AGH logs. There you should see the client DNS request. You would need to check the browser error messages in detail. There is a difference between can't connect and DNS resolution failing.

1 Like