Magento2 cannot resolve path to pub/static JS files

[zucler]

Preconditions

1. Magento ver. 2.1.3
2. PHP 7.0
3. MySQL 5.6

All of the above running in docker containers. Files are sync'ed using docker-sync utility, but I've also tried mounting volumes directly from my local host drive and it did not help.

I've confirmed that PHP is running as www-data user and that all project files have read & write permissions on every file and directory within the project.

I have previously tried deleting all manual content and running setup:static-content:deploy. Static files were re-created, but it didn't help me to solve my problem.

Lastly, I've troubleshooted the code as far as I could and got to the point where in

vendor/magento/framework/View/Design/FileResolution/Fallback/Resolver/Simple.php file

protected function resolveFile(RuleInterface $fallbackRule, $file, array $params = [])
    {
        //->getPatternDirs return Array ( [0] => /var/www/html/lib/web )
        // given that nginx doc root path is /var/www/html
        foreach ($fallbackRule->getPatternDirs($params) as $dir) {
            $path = "{$dir}/{$file}";
            $dirRead = $this->readFactory->create($dir);
            if ($dirRead->isExist($file) && $this->checkFilePathAccess($file, $path)) {
                return $path;
            }
        }
        return false;
    }

Error details:

Unable to resolve the source file for '_requirejs/adminhtml/Magento/backend/en_US/requirejs-config.js'
#0 /var/www/html/vendor/magento/framework/App/StaticResource.php(97): Magento\Framework\View\Asset\File->getSourceFile()
#1 /var/www/html/vendor/magento/framework/App/Bootstrap.php(258): Magento\Framework\App\StaticResource->launch()
#2 /var/www/html/pub/static.php(13): Magento\Framework\App\Bootstrap->run(Object(Magento\Framework\App\StaticResource))
#3 {main}

Also, I have confirmed that these files actually exist, but Magento is unable to work out their paths correctly.

Steps to reproduce

1. Open management page or default Luma page

Expected result

1. All files are loaded and all Javascript on the page is working

Actual result

1. The files below can not be loaded, thus no JS is working on the page

• http://buywithme.local/static/version1482120120/_requirejs/frontend/Magento/luma/en_US/requirejs-config.js
• http://buywithme.local/static/version1482120120/frontend/Magento/luma/en_US/jquery/jquery-storageapi.js
• http://buywithme.local/static/version1482120128/_requirejs/adminhtml/Magento/backend/en_US/requirejs-config.js
• http://buywithme.local/static/version1482120128/adminhtml/Magento/backend/en_US/jquery/jquery-storageapi.js
• http://buywithme.local/static/version1482120128/adminhtml/Magento/backend/en_US/jquery/ui.js
• http://buywithme.local/static/version1482120845/adminhtml/Magento/backend/en_US/prototype.js

[swieczorek]

I noticed the same issue. After installing a blank Magento 2.1.3 you are not able to use the backend because of the missing files.

[careys7]

I have the same issue after upgrading from Magento 2.1.2 (Enterprise) to Magento 2.1.3 using a composer upgrade.

I think it's due to changes made in static files - see release notes:

• We’ve corrected a problem with _requirejs asset retrieval via static.php in static content versioning.
• Versioning of static files (including CSS, JS, font, and image files) is now enabled by default.

I am using example nginx configuration, and have tried switching to both developer and production modes. Request reaches static.php correctly which then returns a 404 header to nginx. The referenced files exist on disk and I have verified file permissions.

I used the following workaround to disable static file signing, which has corrected the 404 for me:

INSERT INTO `core_config_data` (`scope`, `scope_id`, `path`, `value`) VALUES ('default', 0, 'dev/static/sign', '0');

You will need to clear cache after this, and also check for any entries with the same config path if you have previously modified this setting.

This isn't a very good workaround as it would break cache-busting when using Varnish or any CDNs etc, but at least assets do not 404.

[jmonschke]

I ran into the same issue with the upgrade, and the solution is updating the nginx or apache configuration to fix the rewriting issues. The /static/ section of Nginx should be as follows to be able to get it working properly.

 location /static/ {
    if ($MAGE_MODE = "production") {
      expires max;
    }

    # Remove signature of the static files that is used to overcome the browser cache
    location ~ ^/static/version {
      rewrite ^/static/(version\d*/)?(.*)$ /static/$2 last;
    }

    location ~* \.(ico|jpg|jpeg|png|gif|svg|js|css|swf|eot|ttf|otf|woff|woff2)$ {
      add_header Cache-Control "public";
      add_header X-Frame-Options "SAMEORIGIN";
      expires +1y;

      if (!-f $request_filename) {
        rewrite ^/static/(version\d*/)?(.*)$ /static.php?resource=$2 last;
      }
    }

    location ~* \.(zip|gz|gzip|bz2|csv|xml)$ {
      add_header Cache-Control "no-store";
      add_header X-Frame-Options "SAMEORIGIN";
      expires off;

      if (!-f $request_filename) {
         rewrite ^/static/(version\d*/)?(.*)$ /static.php?resource=$2 last;
      }
    }

    if (!-f $request_filename) {
      rewrite ^/static/(version\d*/)?(.*)$ /static.php?resource=$2 last;
    }

    add_header X-Frame-Options "SAMEORIGIN";
  }

[careys7]

Thanks @jmonschke - my nginx file was missing the fix added in #2323. Adding this works for me.

It seems that the other version regexes are redundant (or were broken prior to #2323). I think these should just be removed (see #7921).

[adifucan]

@zucler @careysizer @swieczorek @jmonschke Guys, can you provide us with more information about your configuration to reproduce this issue.

• Are you all encountering this issue after update from previous version (what version?) to 2.1.3?
• Are you all using Nginx?
• Are you all using docker?
• What edition of Magento do you use: CE or EE?
• What permissions and ownership do you have for Magento webroot?
  I tested it with the following permissions: http://magento.stackexchange.com/a/95033

Firstly, I installed Magento CE 2.1.3 via composer on docker contains: 1 with nginx & php, 1 with mysql in default and developer mode and it works.
Secondly, in installed Magento CE 2.1.3 on vagrant with nginx/1.10.2, php 7.0.14, mysql 5.6 in default, developer and production modes and it works fine.
Thirdly, I installed Magento CE 2.1.2 on vagrant with nginx/1.10.2, php 7.0.14, mysql 5.6 in default& developer modes and updated via composer to Magento CE 2.1.3 and it worked.
But after I switched to production mode after upgrade from previous version to 2.1.3 I got an exception:

php bin/magento setup:static-content:deploy
Requested languages: en_US
Requested areas: frontend, adminhtml
Requested themes: Magento/blank, Magento/luma, Magento/backend
=== frontend -> Magento/blank -> en_US ===
=== frontend -> Magento/luma -> en_US ===
=== adminhtml -> Magento/backend -> en_US ===
.
                                                                                                                                                       
  [Magento\Framework\Exception\FileSystemException]                                                                                                    
  The path "_requirejs/adminhtml/Magento/backend/en_US/requirejs-config.js:///var/www/magento/pub/static/var/www/magento/pub/static/" is not writable

Is this it?

[jmonschke]

@adifucan That is not the issues that I was seeing at all. The issue was that the files were there and being generated, but when the browser made the request for them, the web server was unable to do anything about it.

There are new nginx.conf.sample and .htaccess.sample files in the repository that you should pay attention to when running this particular upgrade.

[adifucan]

@jmonschke Sorry for inconvenience but can you provide us with exact steps to reproduce this bug?

• Do you encounter this issue after update from previous version (what version?) to 2.1.3?
• Do you use Nginx?
• Do you use docker?
• What edition of Magento do you use: CE or EE?
• What permissions and ownership do you have for Magento webroot?
• What mode are you in?
• Do you have root $MAGE_ROOT/pub; in nginx.conf.sample file?
  I'm using the latest nginx.conf.sample and .htaccess.sample files.
  Thanks!

[jmonschke]

@adifucan I saw this when upgrading from 2.1.2 to 2.1.3.

I am using nginx and docker and EE.

I'm in developer mode, and have a special www-data user and group as ownership of the magento files.

[adifucan]

@jmonschke I have just installed Magento EE 2.1.2 on Vagrant with composer and nginx as a web server. I set permissions and ownership like here: http://devdocs.magento.com/guides/v2.1/install-gde/prereq/file-system-perms.html
I'm in developer mode.
Then I updated Magento to 2.1.3 with composer update like here: http://devdocs.magento.com/guides/v2.0/comp-mgr/cli/cli-upgrade.html
And Magento (backend/frontend works) fine.

So I guess probably it's the issue with docker?

But I have one more question: do you set the Magento root directory to /pub or not?
I tested it WITHOUT pub directory root. So may be that's the reason why I cannot reproduce it?

Thanks!