[PR #8785] [CLOSED] Add proper Adguard Home update #7639

Closed
opened 2026-02-26 15:35:42 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/community-scripts/ProxmoxVE/pull/8785
Author: @burgerga
Created: 10/31/2025
Status: Closed

Base: mainHead: feat_adguard_update


📝 Commits (3)

  • 18edfc2 Add real Adguard Home update
  • f09d218 Update Adguard update frontend info
  • d2a93dc Remove comment from Adguard update script

📊 Changes

2 files changed (+33 additions, -2 deletions)

View changed files

📝 ct/adguard.sh (+32 -1)
📝 frontend/public/json/adguard.json (+1 -1)

📄 Description

✍️ Description

Currently Adguard is listed as updateable, but the only thing it does is msg_error .... Update via the web interface might fail though (happened to me this morning), which is why Adguard has also provided manual instructions. This PR will implement the manual update. It also takes into account that github.com might not resolve anymore after stopping the Adguard service (again, happened to me, as Adguard is my only DNS server :P), so it first installs Adguard into a temporary location, and then stops the service and moves it to the correct location.

Link: #

Prerequisites (X in brackets)

  • Self-review completed – Code follows project standards.
  • Tested thoroughly – Changes work as expected.
  • No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

🛠️ Type of Change (X in brackets)

  • 🐞 Bug fix – Resolves an issue without breaking functionality.
  • New feature – Adds new, non-breaking functionality.
  • 💥 Breaking change – Alters existing functionality in a way that may require updates.
  • 🆕 New script – A fully functional and tested script or script set.
  • 🌍 Website update – Changes to website-related JSON files or metadata.
  • 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
  • 📝 Documentation update – Changes to README, AppName.md, CONTRIBUTING.md, or other docs.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/community-scripts/ProxmoxVE/pull/8785 **Author:** [@burgerga](https://github.com/burgerga) **Created:** 10/31/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `feat_adguard_update` --- ### 📝 Commits (3) - [`18edfc2`](https://github.com/community-scripts/ProxmoxVE/commit/18edfc2473937da01688f8e868d2c3e2efb5ad7c) Add real Adguard Home update - [`f09d218`](https://github.com/community-scripts/ProxmoxVE/commit/f09d218419d6a6084b9b3c3011941ec739303945) Update Adguard update frontend info - [`d2a93dc`](https://github.com/community-scripts/ProxmoxVE/commit/d2a93dcf2aa7ae0fddfebbc028be828f9b859e66) Remove comment from Adguard update script ### 📊 Changes **2 files changed** (+33 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `ct/adguard.sh` (+32 -1) 📝 `frontend/public/json/adguard.json` (+1 -1) </details> ### 📄 Description <!--🛑 New scripts must be submitted to [ProxmoxVED](https://github.com/community-scripts/ProxmoxVED) for testing. PRs without prior testing will be closed. --> ## ✍️ Description Currently Adguard is listed as updateable, but the only thing it does is `msg_error ...`. Update via the web interface might fail though (happened to me this morning), which is why Adguard has also provided [manual instructions](https://adguard-dns.io/kb/adguard-home/faq/#manual-update). This PR will implement the manual update. It also takes into account that github.com might not resolve anymore after stopping the Adguard service (again, happened to me, as Adguard is my only DNS server :P), so it first installs Adguard into a temporary location, and then stops the service and moves it to the correct location. ## 🔗 Related PR / Issue Link: # ## ✅ Prerequisites (**X** in brackets) - [x] **Self-review completed** – Code follows project standards. - [x] **Tested thoroughly** – Changes work as expected. - [x] **No security risks** – No hardcoded secrets, unnecessary privilege escalations, or permission issues. --- ## 🛠️ Type of Change (**X** in brackets) - [ ] 🐞 **Bug fix** – Resolves an issue without breaking functionality. - [x] ✨ **New feature** – Adds new, non-breaking functionality. - [ ] 💥 **Breaking change** – Alters existing functionality in a way that may require updates. - [ ] 🆕 **New script** – A fully functional and tested script or script set. - [ ] 🌍 **Website update** – Changes to website-related JSON files or metadata. - [x] 🔧 **Refactoring / Code Cleanup** – Improves readability or maintainability without changing functionality. - [ ] 📝 **Documentation update** – Changes to `README`, `AppName.md`, `CONTRIBUTING.md`, or other docs. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-02-26 15:35:42 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ProxmoxVE#7639
No description provided.