<p>The setting useXSendFile was set to true.  I changed this setting to false and everything works now.  Looks like this <a href="https://www.nginx.com/resources/wiki/start/topics/examples/xsendfile/" rel="nofollow">guide</a> could help to get things working when this setting is set to true.</p>

CC BY-SA 3.0
2016-09-28T04:50:46.530Z
2016-09-28T04:50:46.530Z
kalu
<p>The issue I am experiencing is very similar to the one described here: <a href="https://craftcms.com/support/missing-cp-css-js" rel="nofollow noreferrer">link</a>.  The fix described there does not work.</p>

<p>Here is what happens when I request a resource from that page directly using curl:</p>

<pre><code>$ curl -v 'http://localhost/admin/resources/js/craft.js?d=1474612391'
*   Trying ::1...
* Connected to localhost (::1) port 80 (#0)
&gt; GET /admin/resources/js/craft.js?d=1474612391 HTTP/1.1
&gt; Host: localhost
&gt; User-Agent: curl/7.47.0
&gt; Accept: */*
&gt; 
&lt; HTTP/1.1 200 OK
&lt; Server: nginx
&lt; Date: Fri, 23 Sep 2016 07:07:59 GMT
&lt; Content-Type: application/javascript; charset=utf-8
&lt; Transfer-Encoding: chunked
&lt; Connection: keep-alive
&lt; Vary: Accept-Encoding
&lt; X-Powered-By: PHP/7.0.8-0ubuntu0.16.04.2
&lt; Content-Disposition: attachment; filename="craft.js"
&lt; X-Sendfile: [CENSORED]/craft/app/resources/js/compressed/craft.js
&lt; 
* Connection #0 to host localhost left intact
</code></pre>

<p>Here is some version info:</p>

<ul>
<li>Linux: 16.04 LTS (Xenial Xerus)</li>
<li>PHP: 7.0.8-0ubuntu0.16.04.2</li>
<li>nginx: 1.10.0</li>
</ul>

<p>Here is a <a href="https://gist.github.com/kenzie/5811327" rel="nofollow noreferrer">link</a> to my nginx config (approximately).</p>

<p>Here is a screenshot of what the page looks like:</p>

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

CC BY-SA 3.0
2016-09-23T23:50:22.860Z
The cURL output looks like it actually works... you get a 200OK and the correct response headers.  Do you get a 200OK from the browser as well for those CSS/JS files?
Brad Bell
CC BY-SA 3.0
2016-09-28T04:48:37.900Z
Yes I get 200 in browser as well.  But the files are empty.  The source files are intact on the server.  I turned dev mode on and opened up craft/storage/runtime/logs/craft.log and everything looks normal
kalu
<installation>
Missing CSS/JS in the Control Panel
# Missing CSS/JS in the Control Panel

(Asked by: username_0 on 2016-09-23)

The issue I am experiencing is very similar to the one described here: link.  The fix described there does not work.
Here is what happens when I request a resource from that page directly using curl:
$ curl -v 'http://localhost/admin/resources/js/craft.js?d=1474612391'
*   Trying ::1...
* Connected to localhost (::1) port 80 (#0)
> GET /admin/resources/js/craft.js?d=1474612391 HTTP/1.1
> Host: localhost
> User-Agent: curl/7.47.0
> Accept: */*
> 
< HTTP/1.1 200 OK
< Server: nginx
< Date: Fri, 23 Sep 2016 07:07:59 GMT
< Content-Type: application/javascript; charset=utf-8
< Transfer-Encoding: chunked
< Connection: keep-alive
< Vary: Accept-Encoding
< X-Powered-By: PHP/7.0.8-0ubuntu0.16.04.2
< Content-Disposition: attachment; filename="craft.js"
< X-Sendfile: [CENSORED]/craft/app/resources/js/compressed/craft.js
< 
* Connection #0 to host localhost left intact

Here is some version info:

Linux: 16.04 LTS (Xenial Xerus)
PHP: 7.0.8-0ubuntu0.16.04.2
nginx: 1.10.0

Here is a link to my nginx config (approximately).
Here is a screenshot of what the page looks like:

**Tags:** installation

> **Comments:**
> **username_1**: The cURL output looks like it actually works... you get a 200OK and the correct response headers.  Do you get a 200OK from the browser as well for those CSS/JS files?  
> **username_2**: Yes I get 200 in browser as well.  But the files are empty.  The source files are intact on the server.  I turned dev mode on and opened up craft/storage/runtime/logs/craft.log and everything looks normal  

---

## 1 answers

### Answer by username_2 on 2016-09-28. Score: 1

The setting useXSendFile was set to true. I changed this setting to false and everything works now. Looks like this [guide](https://www.nginx.com/resources/wiki/start/topics/examples/xsendfile/) could help to get things working when this setting is set to true.


---

