Open pickles4evaaaa opened 1 month ago
Hi @pickles4evaaaa Did you check https://github.com/bakito/adguardhome-sync/wiki/FAQ#sync-error-403-forbidden--401-unauthorized ? Is your password field in single quotes?
Hi @pickles4evaaaa Did you check https://github.com/bakito/adguardhome-sync/wiki/FAQ#sync-error-403-forbidden--401-unauthorized ? Is your password field in single quotes?
I rechecked my config file and still no dice. I am going to paste my updated config, as my original did not have the quotations.
Here is what is in my docker-compose file on portainer stack: https://pastebin.com/X28rAFzb
Thanks
Try SINGLE quotes 'xxx'
not DOUBLE quotes
Try SINGLE quotes
'xxx'
not DOUBLE quotes
I will try this- should I switch all of the double quotes to single quotes in the compose file? Or just the username and password of the origin server?
At least username and password, for the rest, it should not matter. Docker compose interpretes some characters, when they are in double quotes. With single quotes they should be kept as is.
At least username and password, for the rest, it should not matter. Docker compose interpretes some characters, when they are in double quotes. With single quotes, they should be kept as is.
No luck, still getting an error. For what it's worth, I can connect to the replica server just fine using the same setup in the config file as the origin. Meaning, the application can reach my replica1 server with no issue whereas it doesn't want to connect to my origin.
Have you considered using a different password, or the same as for your replica?
There's not much more I can do here, sorry
What happened?
My origin AdGuard instance is not playing nice with sync. I have verified that the address, username, and password are all correct. My replica 1 server can be logged into just fine. I am running AdguardHome-Sync in a container that is on the same machine as my origin AGH instance.
AdguardHome-Sync Version
v0.6.12
AdguardHome Version
v0.107.52
Configuration
Relevant log output
Anything else?
No response