mirror of
https://github.com/bakito/adguardhome-sync.git
synced 2026-03-02 22:57:06 -05:00
synch error #3
Labels
No labels
Stale
bug
bug
dependencies
dependency to upstream
duplicate
enhancement
help wanted
missing Information
openapi_gen
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/adguardhome-sync#3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @elRadix on GitHub (Apr 5, 2021).
can you please have a look at the error below
2021-04-05T12:57:01.816+0200 ERROR sync sync/sync.go:104 Error getting origin filters {"from": "192.168.1.101:81", "error": "parsing time \"\"\"\" as \"\"2006-01-02T15:04:05Z07:00\"\": cannot parse \"\"\" as \"2006\""} github.com/bakito/adguardhome-sync/pkg/sync.(*worker).sync /root/go/pkg/mod/github.com/bakito/adguardhome-sync@v0.0.6/pkg/sync/sync.go:104 github.com/bakito/adguardhome-sync/pkg/sync.Sync.func1 /root/go/pkg/mod/github.com/bakito/adguardhome-sync@v0.0.6/pkg/sync/sync.go:24 github.com/robfig/cron/v3.FuncJob.Run /root/go/pkg/mod/github.com/robfig/cron/v3@v3.0.1/cron.go:136 github.com/robfig/cron/v3.(*Cron).startJob.func1 /root/go/pkg/mod/github.com/robfig/cron/v3@v3.0.1/cron.go:312@bakito commented on GitHub (Apr 5, 2021):
Hi Can you please provide the output of your origin adguard instance?
https:///control/filtering/status
What version of adguard home are you using?
@JoshStark commented on GitHub (Apr 5, 2021):
I also had this issue when first setting up the sync tool against an existing primary and new (running but empty) replica instance. I found this issue could be caused by bad filter lists (either empty or malformed), but the only way I was able to resolve the issue was to copy the filter section of the primary instance .yaml file over into the replica .yaml file then restart replica. Only then did sync work for filters.
AdGuard Home version: v0.105.2 (primary & replica).
Output of the lists I'm using (via http://<primary_IP>:80/control/filtering/status) is:
@elRadix commented on GitHub (Apr 5, 2021):
here is my output
@bakito commented on GitHub (Apr 5, 2021):
I've built a new version https://github.com/bakito/adguardhome-sync/releases/tag/v0.0.7 where the last_updated timestamp is ignored. It's anyway not of any use for the synchronization.
Your replica instance needs to be manually initialized via the adquard home wizard. Did you to this?
@JoshStark commented on GitHub (Apr 5, 2021):
Yes, I went through the initial wizard to bind it and set it up, then restarted, then attempted to sync.
@elRadix commented on GitHub (Apr 5, 2021):
how can I push the wizard again?
@bakito commented on GitHub (Apr 5, 2021):
Does the error stil occur with the new Version?
To run the wizard again, you probably have to re-install adguard home.
@elRadix commented on GitHub (Apr 5, 2021):
updated the app to the latest version
its working great now
@bakito commented on GitHub (Apr 5, 2021):
Cool
Thx for the feedback
@aayushus commented on GitHub (Apr 17, 2021):
Hi @bakito ,
I am using the latest build from the quay.io repo.
I am getting a similar error -
2021-04-18T01:12:00.083Z ERROR sync sync/sync.go:83 Error getting origin status {"from": "10.0.0.10:8082", "error": "403 Forbidden"}
github.com/bakito/adguardhome-sync/pkg/sync.(*worker).sync
/go/src/app/pkg/sync/sync.go:83
I am able to get a response from http://10.0.0.10:8082/control/filtering/status via postman.
Can you please help?
@bakito commented on GitHub (Apr 18, 2021):
Hi @mercplus
What's the Version of your origon adguard home?
How does your config look ?
@aayushus commented on GitHub (Apr 18, 2021):
Both of the adguards are docker deployment. I was syncing manually, so I tried switching Origin and Secondary with the same error.
Origin Version - v0.105.2
Secondary Version - v0.105.2
Here's my config - https://pastebin.com/zJ7BQ5KS
Please note - The adguards deployments are on 2 different (self-hosted) servers. The Adguardhome-sync deployment is on a third server which I primarily use for testing. I am able to get a response to the curl from this third server.
@bakito commented on GitHub (Apr 18, 2021):
Are username and password in your config correct?
403 is returned from adguard home if username / password are incorrect.
You adguard home instances need to be initialized via the Weg UI befor synch is working.
@aayushus commented on GitHub (Apr 18, 2021):
Yeah, the username/password is correct. If they were incorrect, I would have gotten 401 unauthorized vs 403 Forbidden?
Is there a way to enable debug mode and see the actual curl request going out to Adguard?
@bakito commented on GitHub (Apr 18, 2021):
There's currently no verbose mode.
Adguard Home does not return 401 but 403 on invalid credentials.
At least, that's what I'm seeing with the version v0.105.2 running in docker.
`curl http://localhost:9090/control/status -v
< HTTP/1.1 403 Forbidden
< Date: Sun, 18 Apr 2021 15:39:45 GMT
< Content-Length: 9
< Content-Type: text/plain; charset=utf-8
<
Forbidden`
What can you see in the log of adguard home container?
With the curl above I see
2021/04/18 15:37:58 [info] Auth: invalid Basic Authorization value
@bakito commented on GitHub (Apr 18, 2021):
I added the possibility to see the requests sent to adguard home.
You can see the messages when settintgthe environment variable LOG_LEVEL=debug
You need v0.1.2 for that.
@aayushus commented on GitHub (Apr 18, 2021):
Thanks. I get the below log -
2021-04-18T16:47:00.059Z DEBUG client client/client.go:105 do get {"host": "10.0.0.10:8082", "method": "GET", "path": "status", "username": "username"}
2021-04-18T16:47:00.132Z DEBUG client client/client.go:110 got response {"host": "10.0.0.10:8082", "method": "GET", "path": "status", "username": "username", "body": "Forbidden"}
2021-04-18T16:47:00.132Z ERROR sync sync/sync.go:86 Error getting origin status {"from": "10.0.0.10:8082", "error": "403 Forbidden"}
My password is a complete numeric string (no alphabets). Could that be an issue?
@aayushus commented on GitHub (Apr 18, 2021):
Hi @bakito
I was able to get it up and running.
I created a new instance on a new server with the same ID/Pass using the setup wizard, didn't work.
I then changed the username to an email address with an alphanumeric password, it worked. I reinitialized my regular adguards and everything started working!
@bakito commented on GitHub (Apr 18, 2021):
OK, then it must have been something with your first setup.
It worked for me, when I used the setup with an all numeric password.
I was not able to reproduce this issue.
@Ionutsbirnea commented on GitHub (Jan 1, 2024):
Hi all. I get the same 403 error, username is an email and password is indeed alphanumeric but with one capital letter. So far no luck logging in. I am running this in a jail on a TrueNas server. The install has been done via plug-in tab. Any help will be much appreciated. Thanks all!
@GeneralUser-NonDev commented on GitHub (Jan 6, 2024):
Hi all I have the following error trying to setup the sync program (unraid docker)
Primary Adguard (v0.107.43) is on my unraid server, same as the sync program. 192.168.10.0
secondary is on another machine (v0.107.43, proxmox container, helper script install) on another VLAN. 192.168.1.0
sync seems to be having issue seeing the primary which is on the same machine as itself.
Both instances seem to be working (set same filters manually when sync didnt work) and are showing use.
Ive even tried putting both adguard and sync on "custom: br0" in unraid as i'd seen a comment on another issue post about different custom docker networks messing with the program.
I can only install things like this via youtube videos so i have no clue what i'm looking at, any assistance is appreciated.
edit:
I just found the webui of sync, and logged in. when i clicked on the red "origin" button i got an error ( don't recall it, something about a file/command/something being too long), but when i hovered it said something about returning a non-secure connection on a secure request, no i removed the "s" on the http addresses of both origin and replica, noow when i click the origin button it loads the page, but i still have errors, (now 403 forbidden) but it loads the origin page, i don't see any buttons for the replica(s), i'd seen the extras so I commented them out (multiple setup) and left just the single setup.
Edit again:
I figured it out, finally got the sync webui to have an icon for both primary and secondary instances, then i quintuple checked the logins and what do you know, i messed up the password on the primary, fixed it and it appears to be working correctly now from what i can tell.
@bartclone commented on GitHub (Jan 7, 2024):
Hi,
The error log shows that the AG running in the Proxmox container cannot be
reached.
As you state this Proxmoc container is on another VLAN, which separates
networks, you only can solve it using a specific route on your proxmox-host
and/or firewall/router.
As such, this is beyond AG, and more of a network issue.
Have you ticked the box in Proxmox (host) to be VLAN-aware?
Regards, Bart
Op zo 7 jan. 2024 om 00:32 schreef GeneralUser-NonDev <
@.***>
@gh57gh commented on GitHub (Apr 16, 2024):
I'm having a similar problem. My situation is the following:
Replica: DietPi with Adguard installed over the dietpi-software (not docker)
Origin: Unraid with Adguard installed over the Docker Compose Manager.
Adguard-Sync: Part of the docker-compose of the Unraid Adguard instance.
I get the two errors in the Adguard-Sync webui:
my filtering status for the unraid adguard origin is the following:
I can click on both instances of adguard through the adguard-sync webgui.
Unfortunately I'm no expert and I think there is an underlying problem with the Unraid Adguard origin.
This is the yaml I created in Unraid: