Share

Question

I have followed the guide here (https://www.digitalocean.com/community/tutorials/how-to-configure-nginx-as-a-web-server-and-reverse-proxy-for-apache-on-one-ubuntu-16-04-server)

While they are using Ubuntu we are using Centos 7.2.

Going directly to apache on port 8080 or 8443 (ssl) works. Pulling static files from Nginx works as well on port 80 and 443. However once the configuration is updated to use pass php traffic to apache I get 502 Bad Gateway. I

Nginx Config

server {
    listen 80;
    listen 443 ssl;
    server_name www.domain.com domain.com;  

    ssl on;
    ssl_protocols       TLSv1 TLSv1.1 TLSv1.2;
    ssl_ciphers         ECDHE-RSA-AES256-SHA384:AES256-SHA256:RC4:HIGH:!MD5:!aNULL:!eNULL:!NULL:!DH:!EDH:!AESGCM;
    ssl_session_cache   shared:SSL:5m;
    ssl_session_timeout 10m;
    ssl_prefer_server_ciphers on;
    ssl_certificate /etc/nginx/ssl/domain_com.pem;
    ssl_certificate_key /etc/nginx/ssl/domain_com.key;

    root /data/web/corp/domain;
    index index.php index.htm index.html;

    location / {
        try_files $uri $uri/ /index.php;
    }

    location ~ \.php$ {
        proxy_pass https://127.0.0.1:8443;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }

    location ~ /\. {
        deny all;
    }
}

I have tried to set the proxy_pass to the internal IP, Public IP, domain name, and loopback ip. Seems to all be the same issue.

Apache is set to listen on 8080 and 443.

The Nginx error logs show this:

2017/03/14 23:07:52 [error] 24934#0: *306 upstream prematurely closed connection while reading response header from upstream, client: 71.25.9.17, server: www.domain.com, request: "GET / HTTP/1.1", upstream: "https://127.0.0.1:8443/index.php", host: "www.domain.com"

Apache SSL error log:

[Tue Mar 14 23:12:36.955268 2017] [ssl:error] [pid 63873] [client 127.0.0.1:45822] AH02261: Re-negotiation handshake failed: Not accepted by client!?, referer: https://www.domain.com/favicon.ico

Apache SSL access log:

127.0.0.1 - - [14/Mar/2017:23:12:16 +0000] "GET /index.php HTTP/1.0" 403 211

I am not sure where to start as I am new to Nginx but from my reading it seems to be much better/faster at serving up static content than Apache. While our development group currently requires .htaccess we have to keep using Apache.

Answer 1

hansen March 15, 2017

I'm pretty sure your problem comes from using HTTPS through localhost.

Since all the traffic is contained on the same server between Nginx and Apache, then you don't really need to encrypt that traffic.

And remember to setup Apache to listen on 127.0.0.1 (known as localhost), and just HTTP port 8080. You don't want Apache to listen on your public IP - otherwise there would be multiple ways into your system, which wouldn't be good.

Try this instead in your Nginx php-section:

proxy_pass http://127.0.0.1:8080;

Reply

Answer 2

stephenafamo March 15, 2017

I had a battle with this myself.
Add the following lines to wp-config.php

// If we're behind a proxy server and using HTTPS, we need to alert Wordpress of that fact
// see also http://codex.wordpress.org/Administration_Over_SSL#Using_a_Reverse_Proxy
if (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] === 'https') {
    $_SERVER['HTTPS'] = 'on';
}

It should come just before

/* That's all, stop editing! Happy blogging. */

Reply

Answer 3

joshopkins March 15, 2017

Getting a little closer. But have a different error now. Now I am getting a forbidden error access denied.

Forbidden

You don't have permission to access /index.php on this server.

I have updated the user and group on the directory and files to apache:apache. I have even for testing given them all 777 permissions. Still no luck. Apache is running as user and group apache.

.htaccess file


# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L] 

#START - WP Hide & Security Enhancer
#WriteCheckString:1489014293_56908
<IfModule mod_env.c>
SetEnv HTTP_MOD_REWRITE On
</IfModule>

RewriteRule ^modules/(.+) /wp-content/plugins/$1 [L,QSA]

RewriteRule ^assets/(.+) /wp-includes/$1 [L,QSA]

RewriteRule ^site_uploads/(.+) /wp-content/uploads/$1 [L,QSA]
RewriteCond %{ENV:REDIRECT_STATUS} ^$
RewriteCond %{REQUEST_FILENAME} -f
RewriteCond %{REQUEST_FILENAME} !wp-activate.php [NC]
RewriteCond %{REQUEST_FILENAME} !wp-cron.php [NC]
RewriteCond %{REQUEST_FILENAME} !wp-signup.php [NC]
RewriteCond %{REQUEST_FILENAME} !wp-comments-post.php [NC]
RewriteCond %{REQUEST_FILENAME} !wp-login.php [NC]
RewriteRule ^wp-([a-z-])+.php /index.php [L]
RewriteCond %{ENV:REDIRECT_STATUS} ^$
RewriteRule ^readme.html /index.php [L]

RewriteRule ^user-input.php /wp-comments-post.php [L,QSA]
RewriteCond %{ENV:REDIRECT_STATUS} ^$
RewriteRule ^license.txt /index.php [L]

RewriteRule ^content/(.+) /wp-content/$1 [L,QSA]

                            <FilesMatch "">
                                <IfModule mod_headers.c>
                                    Header unset X-Powered-By
                                </IfModule>
                            </FilesMatch>

                            <FilesMatch "">
                                <IfModule mod_headers.c>
                                    Header unset X-Pingback
                                </IfModule>
                            </FilesMatch>
#END - WP Hide & Security Enhancer

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

Reply

Answer 4

jtittle1 March 17, 2017

@joshopkins @hansen

By chance, are you using CloudFlare? When you mentioned the too many redirects error, CloudFlare immediately came to mind as that's a very common error, but extremely easy to fix.

With CloudFlare, you need to login and head over to the SSL page, then set the configuration to use Full (Strict). Allow it to resolve and that should fix the issue.

As far as the 400 error, in your NGINX configuration, comment out:

ssl on;

So that it looks like:

#ssl on;

Once that change is made, reload or restart NGINX and let me know if you're still having issues.

Reply

joshopkins March 17, 2017

@jtittle @hansen

No we are not using cloudflare.

commented out ssl and reloaded nginx but it did not seem to make a difference.

Answer 5

joshopkins March 17, 2017

@jtittle @hansen

No we are not using cloudflare.

commented out ssl and reloaded nginx but it did not seem to make a difference.

Answer 6

jtittle1 March 18, 2017

@joshopkins

If you'd like to shoot me an e-mail, you can find it in my profile (click on my username). I can make a few suggestions and we can go from there depending on what you'd like to do.

Reply

joshopkins March 18, 2017

Email sent.

Answer 7

joshopkins March 18, 2017

Email sent.

Answer 8

rjh September 1, 2017

Did you ever get this resolved? After hours of tinkering I have been able to get this working because of 1 simple missing "s".. yes an S... If anyone else is having this issue, I'll post my configs for review... Once I added that s, it worked like a charm.. One issue I am stil having is with .htaccess files.. Apparently the proxy to apache from nginx does not include the ip traffic is originally coming from and this causes deny,allow issues.. I have not resolved this yet but the site is now accessible!! Anything in bold you should probably be changing to your own settings... :)

-------------- NGINX -> ** /etc/nginx/sites-available/domainx.conf**

server {
listen 80;
servername xxxxx.domainx.com;
return 301 https://$host$requesturi;
}

server {
listen 443 ssl;
servername xxxxx.domainx.com;
sslcertificate /etc/nginx/ssl/cert_domainx.crt;
sslcertificatekey /etc/nginx/ssl/cert_domainx.key;
location / {
proxypass https://192.168.0.100:6443;
proxysetheader X-Real-IP $remoteaddr;
proxysetheader X-Forwarded-For $proxyaddxforwardedfor;
proxysetheader X-Forwarded-Proto https;
proxysetheader X-Forwarded-Port 443;
proxysetheader Host $host;
}
}

*-------------- APACHE -> * ports.conf

Listen 8085

<IfModule ssl_module>
Listen 6443
</IfModule>

<IfModule mod_gnutls.c>
Listen 6443
</IfModule>

*-------------- APACHE -> * 000-default.conf

<VirtualHost *:**8085**>
ServerName xxxxx.domainx.com
Redirect permanent / https://xxxxx.domainx.com/
</VirtualHost>

<VirtualHost *:**6443**>
# The ServerName directive sets the request scheme, hostname and port that
# the server uses to identify itself. This is used when creating
# redirection URLs. In the context of virtual hosts, the ServerName
# specifies what hostname must appear in the request's Host: header to
# match this virtual host. For the default virtual host (this file) this
# value is not decisive as it is used as a last resort host regardless.
# However, you must set it for any further virtual host explicitly.
ServerName xxxxx.domainx.com

    ServerAdmin **webmaster@localhost**
    DocumentRoot /var/www/html

    SSLEngine on
    SSLCertificateFile **/etc/apache2/ssl/cert_domainx.crt**
    SSLCertificateKeyFile **/etc/apache2/ssl/cert_domainx.key**
    SSLCACertificateFile **/etc/apache2/ssl/cert_intermediate.crt**

    # Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
    # error, crit, alert, emerg.
    # It is also possible to configure the loglevel for particular
    # modules, e.g.
    #LogLevel info ssl:warn

    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined

    # For most configuration files from conf-available/, which are
    # enabled or disabled at a global level, it is possible to
    # include a line for only one particular virtual host. For example the
    # following line enables the CGI configuration for this host only
    # after it has been globally disabled with "a2disconf".
    #Include conf-available/serve-cgi-bin.conf

</VirtualHost>

Reply

Answer 9

royorbison October 3, 2018

If you append $request_uri to your proxy_pass, e.g. https://127.0.0.1:8080$request_uri; then install mod_rpaf as per https://www.digitalocean.com/community/tutorials/how-to-configure-nginx-as-a-web-server-and-reverse-proxy-for-apache-on-one-ubuntu-18-04-server, then Apache and thus PHP will see the right URL, and you won't need SSL on Apache. You can also tweak the standard WordPress rewrite rules because by the time the request gets to Apache, you already know it's for a .php file.

Reply

NGINX reverse proxy to Apache with Wordpress bad gateway

Leave a Comment

Share

Share your Question

NGINX reverse proxy to Apache with Wordpress bad gateway

Leave a Comment

Related Questions

Almost there!

Report a Bug