Syntax error: Unterminated quoted string after update

[marufmax]

Prerequisites

• I have checked the Wiki and Discussions and found no answer

• I have searched other issues and found no duplicates

• I want to report a bug and not ask a question

Operating system type

Linux, Other (please mention the version in the description)

CPU architecture

64-bit ARM

Installation

GitHub releases or script from README

Setup

On one machine

AdGuard Home version

latest

Description

What did you do?

Update Adguard manually

Expected result

To update to new version

Actual result

./AdGuardHome: 1: Syntax error: Unterminated quoted string

Screenshots (if applicable)

Additional information

[EugeneOne1]

@marufmax, hello and thanks for the report. It seems you've fetched the build for a wrong architecture. What does the following command print on the Raspberry Pi?

uname -a

Some versions of Raspberry Pi are having the armv7 architecture instead of arm64.

[Shrekmachine]

same issue here:
Result of uname -a
Linux berry4 5.15.61-v8+ #1579 SMP PREEMPT Fri Aug 26 11:16:44 BST 2022 aarch64 GNU/Linux

[Shrekmachine]

Fun fact. After I manually copied the AdGuardHome Version: v0.108.0-b.15 from the agh-backup folder and restarted service, I got the backup offered again via Fontend UI.
I tried again and this time it worked.

[jmichelgarcia]

Same here, likely read these instructions too fast. Between arm64 and amd64, one can easily miss it/be confused.

[hotenov]

I faced with error earlier (on step 5 from Wiki instruction)

gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now

For me, It turned out that should be option CAPITAL -O instead of -o on step 1 (downloading) for wget command.

With -o file is downloaded as text file without wget's progress output:
pay attention that I use ARM build, filename is different

$ file /tmp/AdGuardHome_linux_arm64.tar.gz
/tmp/AdGuardHome_linux_arm64.tar.gz: Unicode text, UTF-8 text

With correct option -O you should see similar output:

wget 'https://static.adguard.com/adguardhome/release/AdGuardHome_linux_arm64.tar.gz'
--2022-10-04 09:35:18--  https://static.adguard.com/adguardhome/release/AdGuardHome_linux_arm64.tar.gz
Resolving static.adguard.com (static.adguard.com)... 104.20.90.49, 172.67.3.157, 104.20.91.49, ...
Connecting to static.adguard.com (static.adguard.com)|104.20.90.49|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 10999013 (10M) [application/octet-stream]
Saving to: ‘AdGuardHome_linux_arm64.tar.gz’

AdGuardHome_linux_arm64.tar.gz                 100%[====================================================================================================>]  10.49M  9.81MB/s    in 1.1s

2022-10-04 09:35:20 (9.81 MB/s) - ‘AdGuardHome_linux_arm64.tar.gz’ saved [10999013/10999013]

And if you check file type, it will be "gzip compressed data, max compression, from Unix, ..."

$ file /tmp/AdGuardHome_linux_arm64.tar.gz
/tmp/AdGuardHome_linux_arm64.tar.gz: gzip compressed data, max compression, from Unix, original size modulo 2^32 36300800

@EugeneOne1 I don't want to create a new tiny issue. Maybe you should correct this wget download command on Wiki page? 👀

[ainar-g]

@hotenov, well this is just embarrassing on our part, and you are absolutely correct. We have just pushed a fix to that Wiki page.

[Sil3ntVip3r]

Current follow-up: the lowercase wget -o typo discussed above was fixed years ago, but the canonical manual-update FAQ still hardcodes the AMD64 archive without mapping common machine names to AdGuard Home archive labels. In particular, Linux reports 64-bit ARM as aarch64, while the matching package uses arm64; a reader who keeps the example amd64 token can download a binary for the wrong CPU architecture.

I opened AdguardTeam/KnowledgeBaseDNS#460 with a narrow documentation fix. It tells Unix users to run uname -m, maps x86_64 to amd64 and aarch64/arm64 to arm64, requires replacing the token consistently in the file name and URL, and links all other results to the supported-platform matrix.

Validation completed on current KnowledgeBaseDNS master:

• Markdown lint passes with the same pnpm major used by CI.
• The English Docusaurus production build passes and renders the admonition/link correctly.
• Both official Linux AMD64 and ARM64 archive URLs currently return HTTP 200.

This addresses the confirmed documentation gap; it does not claim a separate current automatic-updater defect without a fresh reproducer.