NGINX reverse proxy to Apache with Wordpress bad gateway

I was having the same problem. The solution was to pass everything to apache, not just .php files

    location / {
        proxy_pass http://127.0.0.1:8080;
        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;
    }

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.

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; server_name xxxxx.domainx.com; return 301 https://$host$request_uri; }

server { listen 443 ssl; server_name xxxxx.domainx.com; ssl_certificate /etc/nginx/ssl/cert_domainx.crt; ssl_certificate_key /etc/nginx/ssl/cert_domainx.key; location / { proxy_pass https://192.168.0.100:6443; 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 https; proxy_set_header X-Forwarded-Port 443; proxy_set_header 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>