jrcs | Automatically exported from code.google.com/p/jrcs

Since you are on a Windows host, the mount paths like /etc/localtime won’t work because they don’t exist on your system. The configuration you are using is for a Linux-based host.

Although, it’s recommended, you can remove those mounts from your services. But, keep in mind that you need to keep the docker socket mount, and you will need to adjust it for a Windows host (since the one you have is also for a Linux host). You can try some solution from here.

The correct approach here is to use only docker-compose commands, and to go ahead and rebuild your image:

I found out the bug causing upstream error.

Since I was exposing port 8000 for web, my nginx was unable to talk to web container, since they didn't share the same network.

So, it's better to remove the network from compose, so that they can talk to each other, which is the default behaviour of container.

I believe all you are missing is your VIRTUAL_PORT setting in your gitea container's environment. This tells the reverse proxy container which port to connect with when routing incoming requests from your VIRTUAL_HOST domain, effectively adding along the lines of ":3000" to your upstream server in the nginx conf. This is also the case when your containers are all on the same host. By default, the reverse proxy container only listens on port 80 on that service, but since gitea docker container uses another default port of 3000, you need to tell that to the reverse proxy container essentially. See below using snippet from your compose file.

2 services are unable to listen to the same port as you have found. Your laravel applications are already listening on ports 80/443, so when start your nextcloud containers, it won't be able to bind to those ports.

You'll have to have your jwilder/nginx-proxy:alpine act as a proxy to both the nextcloud container and the laravel servers. This can be done via your nginx configurations and mount it to your container (which you seem to be using the ./proxy/ directory):

https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy/

Although, if your VPS is able to have 2 IP addresses, then you are able to bind the laravel applications to one interface and your nextcloud proxy to the other which will also solve your problem. The first method is better practice as would allow you to scale your server better without having to add another IP address per-application.

https://docs.docker.com/config/containers/container-networking/

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

Just in case anybody else has this issue I have fixed it by removing containers, config files AND IMAGES and then recreating them... here is the process for those that have a setup similar to mine:

The Compose file version 3 upgrade nodes say:

volumes_from: To share a volume between services, define it using the top-level volumes option and reference it from each service that shares it using the service-level volumes option.

You have to do this for each directory you want to share. For the nginx virtual hosts directory, for example:

I've downgraded the mysql version from 8.0 to 5.7 and now it's working like a charm. Not sure why but I'm in contact with the guy's from mysql to find a reason/solution.

Edit 18.05.2020:

A little edit after some time. I'm using the Maria DB Image since then and never had such problems.