-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Wax doesn't handle failures elegantly #11
Comments
Thanks for your report. I don't understand where the first error comes from: how can the I'll take a look in the following weeks. |
Here's the full output (with my FIDO token redacted) when I startup my local server without a VPN:
CloudFlare is serving a challenge page instead of returning the metadata. No big deal- I can workaround it and won't be behind this IP for long. |
Looks like it is related to this bug: benoitc/hackney#464 Closing this bug, hoping the HTTPoison version bump in v0.2.0 will fix this. Reopen if needed. |
My current IP is flagged for spam from a number of domains (including CloudFlare). This causes this error from Wax unless I run through a VPN:
The failure body is a HTML page with status 403.
I'm also getting this failure when starting up my server with my VPN enabled:
Wax then resumes update and everything seems to be working properly.
Let me know what other info would be helpful!
The text was updated successfully, but these errors were encountered: