[bug]: Proxy no working with docker-compose

[davaxi]

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

When using docker-compose, in all instance set automaticly HOSTNAME variable with docker instance name. BUT in node app web/server.js we have :

const currentPort = parseInt(process.env.PORT, 10) || 3000
const hostname = process.env.HOSTNAME || '0.0.0.0'

And service never listen 0.0.0.0. Need using other name (and PORT)

Steps to reproduce

Simple lanch docker-compose and try to access with other proxy to docker (traefikfor exemple)

Browser

Google Chrome

Version

Self-hosted

[davaxi]

Same problème with space/server.js

[mguptahub]

@davaxi

I am interested to know what are we trying to achieve here? Why do you want to hit WEB & SPACE directly from any ip instead of using proxy ?

While I use docker compose, it works perfectly fine for me.

nginx is able to proxy the request to web & spaces containers.

If you are looking at using traefik, i can provide you the sample docker-compose.yml I created few days back.

[mguptahub]

Closing this issue as there is no response from the author.

[vansergen]

@davaxi It works with traefik as well.

[pcasad]

@davaxi

I am interested to know what are we trying to achieve here? Why do you want to hit WEB & SPACE directly from any ip instead of using proxy ?

While I use docker compose, it works perfectly fine for me.

nginx is able to proxy the request to web & spaces containers.

If you are looking at using traefik, i can provide you the sample docker-compose.yml I created few days back.

Hey! @mguptahub if you could give me the docker-compose with traefik you're mentionning, that'd be greatly helpful, I've been struggling with CORS related issues after doing compose up (Plane didn't start up screen with 404 on /api/instances,
/api/users etc