As I’ve asked in another thread before songdogtech closed the thread and also said I was “hijacking the thread”: are you running wordpress under some subdirectory?
This is a bug I can reproduce when running wordpress from /anything/, but not when running from http://www.domain.tld/.
Please let me know if you’re running it from /.
You can post here if you’re running it from a subdirectory:
another bug report
Should not have to add the nginx code to the nginx proxy conf. It should be handled by apache and .htaccess rules. What are the paths to your sitepath, wpurl, and the minify files paths in the HTML?
(Possibly Apache issue is lack of “AllowOverride All” for virtualhost <Directory>.
Also heres an conf for using nginx as reverse proxy:
server {
listen 80;
server_name www.xxxxx.net xxxxx.net;
access_log off;
error_log /var/log/nginx/xxxxx.net.error_log error;
location / {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $remote_addr;
proxy_set_header Host $host;
proxy_pass http://127.0.0.1:7777; # IP of upstream apache or varnish or anything else
}
}
# SSL example Here SSL certificate attached to Nginx Proxy
server {
listen 443;
#server_name localhost;
server_name www.xxxxx.net xxxxx.net;
ssl on;
ssl_certificate /etc/apache2/keys/xxxxx.net/xxxxx.net_chain.crt;
ssl_certificate_key /etc/apache2/keys/xxxxx.net/xxxxx.net.key;
ssl_protocols SSLv3 TLSv1;
access_log /var/log/nginx/xxxxx.net.ssl_access_log main;
error_log /var/log/nginx/xxxxx.net.ssl_error_log info;
location / {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $remote_addr;
proxy_set_header X-Forwarded-Proto https;
proxy_set_header Host $host;
proxy_pass http://127.0.0.1:7777; # IP of upstream apache or varnish or anything else
}
}
