Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HYPERDX_API_PORT and HYPERDX_API_URL conflicts with proxy #441

Open
Saddamus opened this issue Jun 21, 2024 · 1 comment
Open

HYPERDX_API_PORT and HYPERDX_API_URL conflicts with proxy #441

Saddamus opened this issue Jun 21, 2024 · 1 comment

Comments

@Saddamus
Copy link

Hello. These 2 variables are joined together.
HYPERDX_API_PORT: will make instance to start on the port
HYPERDX_API_URL will make the app to use api on HYPERDX_API_URL:HYPERDX_API_PORT
This way you can not deploy any reverse proxy on the same host / IP as port is already in use.
Is there any guide how to make it working with reverse proxy ?

@Foxonn
Copy link

Foxonn commented Feb 22, 2025

Hello. These 2 variables are joined together. HYPERDX_API_PORT: will make instance to start on the port HYPERDX_API_URL will make the app to use api on HYPERDX_API_URL:HYPERDX_API_PORT This way you can not deploy any reverse proxy on the same host / IP as port is already in use. Is there any guide how to make it working with reverse proxy ?

By default, HyperDX app/api will run on localhost with port 8080/8000. You can change this by updating HYPERDX_APP_** and HYPERDX_API_** variables in the .env file. After making your changes, rebuild images with make build-local.

and replace in .env
IMAGE_NAME_HDX=ghcr.hyperdx.io/hyperdxio/hyperdx -> ghcr.io/hyperdxio/hyperdx

and
docker compose up -d

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants