WPengine Troubleshooting

Issues with largeFS with production site

1) We recently had an issue with mutual site when it was connected with largeFS. They searched on it alot and finally they were able to figure out that there was a ngnix rule that was added and was causing an issue.

Following is the rule that was causing an issue -
location ~* ^.+\.(ico|css|js|gif|jpe?g|png|woff|woff2|eot|svg|ttf|webp|jpg\?id=3642)$ {
expires 365d;
add_header Cache-Control "public, must-revalidate";
}

This rule was removed by wpengine team and that fixed the issue.



When images not visible in DEV or STAGING

Many times when we copy an environment since we are using large FS
images don't work and we need to contact support, we lose time on that
how can we solve it?

Normally we have it set to talk to our WP Engine subdomain but my team member is saying that some sites can have this error unless we directly specify the domain in question. This way our domain is not touched at all.

If you ever see this happen again I would have us check to see if the fallback rule we have is set to talk to our WP Engine subdomain or your custom domain. Since this looks to have fixed the issue I'm suspecting this should fix it moving forward with no need to contact us but I would totally recommend to put that to a test as soon as you are able just to be sure.

Excellent! Anytime at all! I apologize for the troubles! If you see this issue happen again with any other site using large FS I'd ask if our fallback rule is using your custom domain or our WP Engine subdomain for the live site and if its using our domain we should then update it to the custom domain. The line in particular used to be location @fallbackToLive { rewrite ^(/.*)  https://agilerising.wpengine.com$1  break; but is now location @fallbackToLive { rewrite ^(/.*)  https://www.agilerising.com$1  break;