I am in the process of configuring my first nginx proxy, which unfortunately does not conform to any standard configuration either.
About the infrastructure:
We have a vServer running a Gitlab including embedded Mattermost. These services are provided via a Docker Compose container. So far, this configuration has been running flawlessly for months. Mattermost is accessible via matterbost.my-domain.de and GitLab via gitlab.my-domain.de. For each of these subdomains an A-record is stored at our domain provider and the redirect is managed via the preconfigured nginx of the GitLab container. I did not have to configure anything here myself.
About the problem:
Now we want to run an additional web server with wordpress on this server. I would like to provide this service with Docker Compose as well. This has also worked without any problems so far and is accessible via port 8080 (my-domain.de:8080). Now, however, I want Wordpress to be accessible without specifying port 8080, i.e. via the URL my-domain.de.
My question:
Can anyone give me some advice on what kind of configuration or setup of the service infrastructure would be ideal for this case? I would prefer not to have to reconfigure the embedded Nginx from Gitlab, as this can certainly be very error-prone.
My attempted solution:
With the domain provider a simple forwarding with the IP address of the server and port, so my-domain.de points to XX.XX.XX.XX:8080. This works so far, but the URL in the Broswer is replaced afterwards by the IP address.
