# Occasionally sites won't load after upgrade from Bullseye to Bookworm (Adguard?)
**URL:** https://dietpi.com/forum/t/occasionally-sites-wont-load-after-upgrade-from-bullseye-to-bookworm-adguard/23177
**Category:** Troubleshooting
**Created:** [1 April 2025 02:26 UTC](https://dietpi.com/forum/t/occasionally-sites-wont-load-after-upgrade-from-bullseye-to-bookworm-adguard/23177 "2025-04-01T02:26:42Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@Rhizome](https://dietpi.com/forum/u/Rhizome)
#### Post date: [1 April 2025 02:26 UTC](https://dietpi.com/forum/t/occasionally-sites-wont-load-after-upgrade-from-bullseye-to-bookworm-adguard/23177/1 "2025-04-01T02:26:42Z")
### 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](http://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
- Used the Bullseye to Bookworm migration script here: [Debian Bookworm has been released – DietPi Blog](https://dietpi.com/blog/?p=3128). Also did updates afterward that Dietpi prompted.
---
### Author:  [@Joulinar](https://dietpi.com/forum/u/Joulinar)
#### Post date: [1 April 2025 05:46 UTC](https://dietpi.com/forum/t/occasionally-sites-wont-load-after-upgrade-from-bullseye-to-bookworm-adguard/23177/2 "2025-04-01T05:46:31Z")
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`.
---
### Author:  [@Rhizome](https://dietpi.com/forum/u/Rhizome)
#### Post date: [4 April 2025 11:51 UTC](https://dietpi.com/forum/t/occasionally-sites-wont-load-after-upgrade-from-bullseye-to-bookworm-adguard/23177/3 "2025-04-04T11:51:58Z")
Ok, I’m not actually sure what the reason for pages not loading is. But when I switched off AGH, some pages still won’t load. If it’s a DNS resolution issue, where would I begin looking to solve this?
---
### Author:  [@Joulinar](https://dietpi.com/forum/u/Joulinar)
#### Post date: [4 April 2025 12:13 UTC](https://dietpi.com/forum/t/occasionally-sites-wont-load-after-upgrade-from-bullseye-to-bookworm-adguard/23177/4 "2025-04-04T12:13:27Z")
I cannot imagine that it is due to the DNS resolution. You can try different DNS servers on the client and see if anything changes.
---
### Author:  [@system](https://dietpi.com/forum/u/system)
#### Post date: [30 September 2025 00:13 UTC](https://dietpi.com/forum/t/occasionally-sites-wont-load-after-upgrade-from-bullseye-to-bookworm-adguard/23177/5 "2025-09-30T00:13:33Z")
This topic was automatically closed 178 days after the last reply. New replies are no longer allowed.