<p>That means your server/browser isn't setting the proper <code>application/json</code> accept header for AJAX requests.</p>

<p><a href="https://i.sstatic.net/5q7Z6.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/5q7Z6.png" alt="enter image description here"></a></p>

CC BY-SA 4.0
2019-08-23T12:55:15.527Z
Thanks @Brad. Over different browsers / locations, we are getting the same issue. I contacted to hosting provider and they said developer to analyse problem. Now, I am clueless for the next step :(
Bhashkar Yadav
CC BY-SA 4.0
2021-11-19T13:06:07.403Z
Any updates on resolving this issue? It's happening to a client's site now, with Craft 3 and Nginx.
Sandwich
CC BY-SA 4.0
2019-08-16T19:30:23.437Z
2019-08-16T19:30:23.437Z
Brad Bell
<p>I am getting error message while loading entries from dashboard. Please see attached screenshot -
<a href="https://i.sstatic.net/w01T6.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/w01T6.png" alt="enter image description here" /></a></p>
<p>While looking into browser console, I found the error message <code>Request must accept JSON in response</code> (using Craft v3.1.18)</p>

<entries><cp-dashboard>
Request must accept JSON in response
# Request must accept JSON in response

(Asked by: username_0 on 2019-08-15)

I am getting error message while loading entries from dashboard. Please see attached screenshot -
[![enter image description here](https://i.sstatic.net/w01T6.png)](https://i.sstatic.net/w01T6.png)

While looking into browser console, I found the error message `Request must accept JSON in response` (using Craft v3.1.18)

**Tags:** entries, cp-dashboard

---

## 1 answers

### Answer by username_1 on 2019-08-16. Score: 1

That means your server/browser isn't setting the proper `application/json` accept header for AJAX requests.

[![enter image description here](https://i.sstatic.net/5q7Z6.png)](https://i.sstatic.net/5q7Z6.png)

> **Comments:**
> **username_0**: Thanks @Brad. Over different browsers / locations, we are getting the same issue. I contacted to hosting provider and they said developer to analyse problem. Now, I am clueless for the next step :(  
> **username_2**: Any updates on resolving this issue? It's happening to a client's site now, with Craft 3 and Nginx.  

---

