Related

Product App Platform: Run Docker containers without managing servers Product
PHP Error Log: authz_core:error - For files that don't exists on my server Question Question
blocked ip in spam Question Question

Question

NGINX reverse proxy to Apache docker container

Posted September 4, 2018 25.4k views
NginxApacheDockerUbuntu 16.04

I’m trying to host several websites on my droplet. I’m to do that, I’m using NGINX (not container) as reverse proxy to Dockerized apps. One such app I’m using is the dockerized Mediawiki set to run on 0.0.0.0:8081.

Mediawiki container is based on php7.2-apache.

Nginx configuration : 

server {

        listen 443 ssl;
        index index.php;

        server_name my.website.com;

        ssl_stapling on;
        ssl_stapling_verify on;

        location / {
                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_pass http://0.0.0.0:8081;
        }

    ssl_certificate /etc/letsencrypt/live/my.website.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/my.website.com/privkey.pem; # managed by Certbot
}

I run the application on port 8081, as can be seen by through docker ps -a

CONTAINER          IMAGE          PORTS
e40c9815d6cc      mediawiki    0.0.0.0:8081 -> 80/tcp

I can access my.website.com, but it shows the default Apache Ubuntu default page. Accessing other pages and resources (index.php, /folder/index.php, images/pic.jpg) returns 404.

Testing the container with similar setup on my machine works. I think there maybe something up I didn’t get with the NGINX config.

Help?

Add a comment
aerlaut
By:
aerlaut

Related

Product App Platform: Run Docker containers without managing servers Product
PHP Error Log: authz_core:error - For files that don't exists on my server Question Question
blocked ip in spam Question Question
Add a comment
1 comment

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
6 answers
mauriciolazo28 September 4, 2018

Hi @aerlaut!

Perhaps proxy_pass should be:

proxy_pass http://127.0.0.1:8081;

From what I understand is that, you want NGINX to listen on any IP address and network device in your server, at port 8081, (listen on 0.0.0.0:8081) and reroute that request to your local docker container on port 8081 (send to 127.0.0.1:8081).

Additionally what does nginx´s error log contains?

Reply Report
scarpion0990 January 31, 2020

I think this below link would be helpful for you

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

if after that you have questions ask about, thanks.

How To Configure Nginx as a Web Server and Reverse Proxy for Apache on One Ubuntu 18.04 Server
by Jesin A
In this tutorial you'll configure Nginx as both a web server and as a reverse proxy for Apache to host four domains on a single server.
Reply Report
gameterserah02 February 13, 2020

It’s simple. Just change the old configuration:

proxy_pass http://0.0.0.0:8081;

To this new one:

proxy_pass http://0.0.0.0:80;

The reason is, between container and Nginx in host server can’t communicate with published port. It just can communicate with the target port. 8081:80 (8081 is published port and 80 is target port).

Let say you have 8081:443, you must create the configuration with proxy_pass http://0.0.0.0:443; for Nginx listen to 443 port number. May this help.

edited by MattIPv4
Reply Report
Ernestas April 17, 2020

I had the same issue not too long ago…

you don’t need to open or map 8081 to 80 port for access, just have 80 and 443 ports exposed inside container.

On your nginx container (if you are using docker-compose) add 

depends_on: 
- proxied_container

in your nginx.config

proxy_pass http://proxied_container:80;

This way nginx connects to container and its internal port and apache will handle everything else…

Reply Report
akshatkarodiya82 July 3, 2020
[deleted]
Reply Report
akshatkarodiya82 July 3, 2020

try to change file in var/www/html put your index.php there..

Reply Report

Related

Looking for something else?

Ask a new question Search for more help