Seeing an “Unexpected server response (204)” error where the PDF Embedder viewer should be loading? This is an uncommon error, and it almost always comes down to a browser extension (a download manager) intercepting the request PDF Embedder makes to fetch the file.
This guide explains the issue and how to resolve it on your site.
Understanding the Issue
Download manager extensions intercept file requests and attempt to handle them independently. When PDF Embedder requests the PDF from your server, the download manager can grab that request and return a 204 No Content response before the viewer receives the file.
Resolving the Issue
Below are the steps to resolve this issue:
Step 1: Test in a different browser
Open the page in a different browser, one without the download manager extension installed. If the PDF loads correctly, this confirms that the browser extension is the cause.
Step 2: Disable the download manager extension
Go to your browser’s extensions panel and disable the download manager. Reload the page and check whether the PDF displays.
Step 3: Configure the download manager to ignore PDF requests
If you want to keep the extension active, check its settings for an option to exclude certain file types or domains from interception. Configuring it to leave PDF file requests alone should resolve the conflict without disabling the extension entirely.
If the error persists after disabling all extensions, contact support and include a link to the page where the error occurs.