cheezitman

Nevermind I found that in my nginx virtualhost file I needed to set:

location ^~ /blogs.dir {
                internal;
                alias /var/www/SITENAME/wp-content/blogs.dir ;
                access_log off; log_not_found off;      expires max;
        }

resolved

Nevermind I found that in my nginx virtualhost file I needed to set:

location ^~ /blogs.dir {
                internal;
                alias /var/www/SITENAME/wp-content/blogs.dir ;
                access_log off; log_not_found off;      expires max;
        }

Nevermind I found that in my nginx config file I needed to set:

location ^~ /blogs.dir {
                internal;
                alias /var/www/SITENAME/wp-content/blogs.dir ;
                access_log off; log_not_found off;      expires max;
        }

You can edit wp-config to turn on debugging, and also check your .htaccess file to see if something has messed with that.

Tried all, no joy. From what I can tell all my media, even new uploads (while they end up in the server in the correct spot), can’t be accessed.

I’ll try permalinks, we’re not using any resizing tool, but I’ll see if I can disable all plugins except Active Directory.

If nothing else where is WordPress storing the path information for media?

I had to follow this and combine the certificate authority with the site certificate.

I’m getting the same thing, except that I’m running it on Ubuntu 12.04 LTS.

I seem to be having a similar problem

Here

However I still think it’s related to my nginx installation.

I’m not seeing anything in the error log.

I do see things like this in the access log:
https://pastebin.com/m7CLFZBX

My nginx.conf file:
https://pastebin.com/T3YTe4xt

My sites-enabled file:
https://pastebin.com/XRtRKBuJ

My wordpress config file:
https://pastebin.com/TtgTCmwV

Quick Cache， it seems to do the job.

Figured it out subscribe2 has a bug causing the problem. Delete subscribe2 folder and the site works again!

Any help?