Deploy Stardog behind a reverse Nginx proxy

Support Bug
1

Hi,

We are deploying Stardog using the stardog/stardog:latest docker container, and a reverse nginx-proxy for docker (cf. GitHub - nginx-proxy/nginx-proxy: Automated nginx proxy for Docker containers using docker-gen)

Here is the docker-compose we are using (running using Docker version 20.10.7, on CentOS 7):

version: '3'
services:
  stardog:
    image: stardog/stardog:latest
    container_name: stardog
    restart: unless-stopped
    volumes:
      - /data/stardog:/var/opt/stardog
    environment: 
      - "STARDOG_SERVER_JAVA_ARGS=-Xmx8g -Xms8g -XX:MaxDirectMemorySize=12g"
      - VIRTUAL_HOST=stardog.myurl.com
      - VIRTUAL_PORT=5820

The container starts without errors, but when we try to login to the URL "http://stardog.myurl.com" it does not work (Stardog just says it can't connect, and there is no log triggered in the docker container)

It seems to be due to specific configuration Stardog needs to perform the connection, anyone have an idea of what could be the cause here?

Note that this reverse nginx proxy for Docker works for dozen of services we have been deploying on our servers (all of them except Stardog)