nginx-le | Nginx with automatic let 's encrypt | TLS library

So you can get more information on the problem using

It all looks good. . Any chance your config was cached ?

php artisan config:clear

php artisan cache:clear

If the above not works.

Try deleting cache if any something you can find cache>config.php

Try these to test you Laravel connection in config>web.php

I think you overread that the htpasswd here is a folder and the name of your corresponding htpasswd file has to match your virtual host name:

you have to create a file named as its equivalent VIRTUAL_HOST variable on directory /etc/nginx/htpasswd/$VIRTUAL_HOST

That means:

• You mount a folder into /etc/nginx/htpasswd of your docker container
• In this folder, you create a passwdfile named according to your vhost adress, like example.de:
• You can create this corresponding file with the command: htpasswd -c example.de username

Silly mistake, port 443 wasn't allowed on my application. I was confused because when i checked on my server, port 443 was open. Then I checked here, https://www.yougetsignal.com/tools/open-ports/ , saying it was closed. I then found out that there's an inbound rule for AWS EC2 instance top allow port 443.

Credits here: NGINX SSL Timeout

This is an issue with react-scripts@3.4.1. You can follow the issue and see the recommended workarounds via github: https://github.com/facebook/create-react-app/issues/8688

Either try downgrading the version of react-scripts to 3.4.0, or add the following line in your docker-compose file:

The problem is if the hostname can not be resolved in upstream blocks, nginx will not start. Here you have defined service container1 to be dependent on container_nginx . But nginx container is never up due to the fact the container1 hostname is not resolved (because container1 is not yet started) Don't you think it should be reverse? Nginx container should be dependent on the app container.

Additionally in your nginx port binding you have mapped 8080:8080 while in nginx conf you have 80 listening.

For that to work you need odoo container in your docker-compose.yaml, which would listen on port 8069. Right now it looks like it can't be resolved.

If you have it in your docker-compose - please let us see it so we can help you.

Plus by doing sudo docker-compose up reverse you are starting only reverse out of whole docker-compose. though you should start odoo first. or start everything by sudo docker-compose up

Managed to resolve this issue through luck...

After rebuilding another server and migrating across, I ran into this issue again. So I thought may be there was something in Windows 10 that is causing this issue. So I thought I would use WSL (Windows Subsystem for Linux) to resolve this.

After I managed to get meteor running on WSL, I noticed that I have not upgraded mup and mup reconfig ran successfully, after downgrading from mup 1.4.6 to mup 1.3.6, everything worked, and I was able to deploy to my staging server again.

You need to create a docker file with that configuration and add build config in the docker-compose file.

First, create a Dockerfile named nginx_proxy.df with the following content.