This article provides information to assist you in resolving the 'failed to fetch' or 'NetworkError when attempting to fetch resource' errors when playing media.
The errors "failed to fetch" and "NetworkError when attempting to fetch resource" are generally experienced by users of proxy software (such as EZproxy or WAM Proxy) when the correct configuration for the specific proxy setup has not been applied.
- Remove any existing stanzas for the legacy Digital Theatre+ website (www.digitaltheatreplus.com)
- Ensure that you have implemented the stanza precisely as described in our EZproxy stanza. Note that the stanza hosted by OCLC may be out of date, as getting updates made to it often take many weeks to be processed.
Potential root causes
The most common symptom we've seen is that requests to https://media.digitaltheatreplus.com/drm-token are failing. This endpoint uses the same IP Authentication as the website, so in theory, if you're able to access the website, the endpoint will also respond to your request.
Due to the nature of proxy configuration being highly variable between different instances, we have identified a number of different issues that may occur.
Different URLs are used when logged in and out of EZproxy
A customer reported that our EZproxy stanza worked when not logged into EZproxy, however the error occurred when logged in. Their solution was to duplicate the stanza modifying the key lines to reflect the URL of the proxied website, for example:
Title Digital Theatre Plus
HTTPHeader -request -process Bearer
HTTPHeader -request -process x-dt-auth-token
Remember to replace the AnonymousURL and URL with the correct URL for your instance of EZproxy
AnonymousURL is not included as the first line
The AnonymousURL line should appear as the first line but it’s may be appearing further down due to the way that the stanza gets published through your internal tools (such as FileMaker).
Modify the Stanza to ensure the AnonymousURL line appears as the first line.
HTTP Headers are being blocked
This error may occur because HTTP Headers are not included in requests made to endpoints required for media playback.
You will see in our EZproxy stanza, two HTTP Header directives that enable video playback.
In short, you will need to ensure the following endpoints are able be sent the correct HTTP Headers. If these are not sent, you will received one of the error messages above when you attempt to play media.
A non-permitted IP address is making the request
We have also identified (for OpenAthens Managed Proxy users) that requests to the https://media.digitaltheatreplus.com/drm-token endpoint were received from a different IP address to those provided by the customer. OpenAthens confirmed these IP addresses were related to their infrastructure, so we have added them to our permit list.
It may be necessary to perform investigation with firstname.lastname@example.org in order to identify whether requests from your organisation are coming from other IPs to those you have provided us with.