<p>Adding my comment as an answer because it fixed my issue:</p>

<p>I traced the issue to a deprecation warning involving <code>$HTTP_RAW_POST_DATA</code> being populated. </p>

<p>I added the line <code>always_populate_raw_post_data = -1</code> to my <code>fpm_app.conf</code> which solved the issue.</p>

CC BY-SA 3.0
2018-01-10T22:58:26.777Z
2018-01-10T22:58:26.777Z
mlkiung
<p>When I attempt to display available updates on my local copy, Craft is unable to display them and instead shows “You’re all up-to-date!”. </p>

<p>Available updates do display on my live copy, as well as on the “updates available” badge on the local copy CP. </p>

<p>I’ve cleared the cache to no avail and I’ve checked the logs and can’t see any errors. I'm running an nginx server and am starting to wonder if this problem arose when switching from apache -> nginx.</p>

<p>I am currently running version 2.6.2996 and am trying to update to 2.6.3001 as well as update a few plugins. </p>

<p>Has anyone run into this issue while trying to display updates on their local copy CP?</p>

<p>The responses coming back when I hit the updates page were all 200s and <code>allowAutoUpdates</code> was set to true using the default setting. </p>

<p><a href="https://i.sstatic.net/3PIrf.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/3PIrf.png" alt="local copy"></a></p>

<p><a href="https://i.sstatic.net/7pbyA.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/7pbyA.png" alt="live copy"></a></p>

CC BY-SA 3.0
2018-01-10T01:36:16.720Z
Locally have you set https://craftcms.com/docs/config-settings#allowAutoUpdates to true by chance?  If you open your browser's console's network tab locally and hit the updates page, what's the response that comes back?
Brad Bell
CC BY-SA 3.0
2018-01-10T19:05:34.480Z
The responses coming back were all 200s and autoUpdates were set to true using the default setting. I ended up tracing the issue to a deprecation warning involving `$HTTP_RAW_POST_DATA` being populated. I was able to add the line `always_populate_raw_post_data = -1` to my `fpm_app.conf` which solved the issue.
mlkiung
CC BY-SA 3.0
2018-01-10T19:25:26.533Z
Ahh... awesome and weird.  Would you mind adding that as an official answer in case it helps someone in the future?
Brad Bell
CC BY-SA 3.0
2018-01-10T22:59:56.137Z
I posted my solution as an answer and updated my question to reflect the additional information. Thanks for your help!
mlkiung
<control-panel><updates><manual-updates>
Available updates not displaying on local copy but show up on live site; instead displays "You're all up to date!" with 5 pending updates
# Available updates not displaying on local copy but show up on live site; instead displays "You're all up to date!" with 5 pending updates

(Asked by: username_0 on 2018-01-09)

When I attempt to display available updates on my local copy, Craft is unable to display them and instead shows “You’re all up-to-date!”.

Available updates do display on my live copy, as well as on the “updates available” badge on the local copy CP.

I’ve cleared the cache to no avail and I’ve checked the logs and can’t see any errors. I'm running an nginx server and am starting to wonder if this problem arose when switching from apache -> nginx.

I am currently running version 2.6.2996 and am trying to update to 2.6.3001 as well as update a few plugins.

Has anyone run into this issue while trying to display updates on their local copy CP?

The responses coming back when I hit the updates page were all 200s and `allowAutoUpdates` was set to true using the default setting.

[![local copy](https://i.sstatic.net/3PIrf.png)](https://i.sstatic.net/3PIrf.png)

[![live copy](https://i.sstatic.net/7pbyA.png)](https://i.sstatic.net/7pbyA.png)

**Tags:** control-panel, updates, manual-updates
> **Comments:**
> **username_1**: Locally have you set https://craftcms.com/docs/config-settings#allowAutoUpdates to true by chance?  If you open your browser's console's network tab locally and hit the updates page, what's the response that comes back?  
> **username_0**: The responses coming back were all 200s and autoUpdates were set to true using the default setting. I ended up tracing the issue to a deprecation warning involving `$HTTP_RAW_POST_DATA` being populated. I was able to add the line `always_populate_raw_post_data = -1` to my `fpm_app.conf` which solved the issue.  
> **username_1**: Ahh... awesome and weird.  Would you mind adding that as an official answer in case it helps someone in the future?  
> **username_0**: I posted my solution as an answer and updated my question to reflect the additional information. Thanks for your help!  

---

## 1 answers

### Answer by username_0 on 2018-01-10. Score: 2

Adding my comment as an answer because it fixed my issue:

I traced the issue to a deprecation warning involving `$HTTP_RAW_POST_DATA` being populated.

I added the line `always_populate_raw_post_data = -1` to my `fpm_app.conf` which solved the issue.


---

