-
-
Notifications
You must be signed in to change notification settings - Fork 77
Open
Description
Expected Behavior
wd-security's update script should complete without errors.
Current Behavior
AU runs from this repository's AppVeyor environment as of June 19th fail with results similar to this:
au_GetLatest failed
ERROR: The request could not be satisfied
403 ERROR
The request could not be satisfied.
Request blocked.
We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
Generated by cloudfront (CloudFront)
Request ID: EisK0Kq2fWsh89rFAtln6-jvC2WMdeUUmWg9NorIQFQIRTy9HbFv4g==
Possible Solutions
- Work with Western Digital's support to get traffic from the AppVeyor environment unblocked.
- Funnel update traffic through an unblocked proxy or VPN connection to work around the block.
- Update the package from another environment that is not blocked.
- Hand off maintenance for this package to another maintainer that is not subject to this block.
- I am willing to take over maintenance, if needed. I go by sublym0nal on the Community Repository.
Steps to Reproduce (for bugs)
Simply wait for the repository's next AU run, and check the package's attempted update results.
Context
wd-security is currently outdated, and package updates fail in part due to this.
Your Environment
N/A
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels