EZProxy "This web property is not accessible via this address"

Hi
There is a while that we encounter an error entitled “This web property is not accessible via this address” when trying to download any PDF material on some scientific websites such as Wiley and TandFonline by our EZProxy service. Would you please check and let us know how the problem can be resolved?
Thank you in advance

It looks like those sites have made a conscious decision to block EZProxy. Neither Cloudflare nor the Community can override this decision. You would have to contact the site owners to address this issue.

2 Likes

In this instance, a specific library content hosting platform activated Bot and/or DDoS protection, and EZproxy (along with other rewriting proxy servers commonly used in academic settings) were caught in the net.

It looks like those sites have made a conscious decision to block EZProxy. Neither Cloudflare nor the Community can override this decision. You would have to contact the site owners to address this issue.

Close, but not quite. This was NOT a “conscious decision” by the platform provider, it was an unintentional side-effect based on the behavior of Cloudflare’s Bot detection algorithms mis-categorizing legitimate proxied traffic as malicious traffic.

I have been attempting to contact the Bot group within Cloudflare to work with them to make this less likely to happen in the future, since many academic publishers leverage the Cloudflare platform for its protection services, but Cloudflare does NOT make it easy for platform providers to initiate contact with their internal groups to resolve broad issues like this.

There REALLY needs to be a better conduit to initiate technical conversations between service providers and Cloudflare in instances like this, where the very protection mechanisms that Cloudflare is selling act contrary to the intended design and cause loss of connectivity for paying users. Cloudflare support simply closes tickets, and the only way to get in touch with a human so far is to call into the sales line (I do not have high hopes that will lead anywhere).

Does anyone from the Cloudflare Bot detection team monitor the community? If so, I would very much like to have a conversation with you about how to avoid this class of problem in the future, since thousands of libraries contacting hundreds of individual vendors to implement work-arounds for a Cloudflare feature that is causing as many problems as it allegedly solves does not scale.