Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error getting origin status #227

Closed
gdtms247 opened this issue Oct 17, 2023 · 1 comment
Closed

Error getting origin status #227

gdtms247 opened this issue Oct 17, 2023 · 1 comment

Comments

@gdtms247
Copy link

Describe the bug
Sync is failing to get status from origin server, not sure when this started, I haven't looked or changed Adguard or sync since implementation over a year ago. Just noticed today that sync is failing, and my logging doesn't go back more than a week to find when it started.

To Reproduce
Steps to reproduce the behavior:

  1. What version of AdGuardHome sync used? v0.4.15
  2. What version of AdGuardHome us used? v0.107.39
  3. How does the configuration look? No changes since setup
  4. What is the error message?
    sync/sync.go:111 Error getting origin status {"from": "192.168.X.X", "error": ": Get "http://192.168.X.X/control/status\": dial tcp 192.168.X.X:80: i/o timeout"}

Expected behavior
Sync is able to check status and move forward with syncing between hosts

@gdtms247
Copy link
Author

Just kidding, FW policy was blocking access from sync app to adguardhome instance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant