Cant access the UI from a remote box #9

New Issue

2026-02-15T16:29:07-05:00

yindo commented

2026-02-15 16:29:07 -05:00

Originally created by @shyamsfo on GitHub (Jul 28, 2023).

Nice work. Comes up fine...

I am running using docker-compose up -d --build

What's the way to access the UI from a remote box?
Something in the frontend always tries to authenticate to 127.0.0.1:3001/api/

I see a VITE_API_BASE variable but I am not sure where to set this (and what to rebuild (for docker) after setting it)

Originally created by @shyamsfo on GitHub (Jul 28, 2023). Nice work. Comes up fine... I am running using `docker-compose up -d --build` What's the way to access the UI from a remote box? Something in the frontend always tries to authenticate to `127.0.0.1:3001/api/` I see a `VITE_API_BASE` variable but I am not sure where to set this (and what to rebuild (for docker) after setting it)

yindo added the question label 2026-02-15 16:29:07 -05:00

yindo closed this issue

2026-02-15 16:29:07 -05:00

yindo commented

2026-02-15 16:29:08 -05:00

@timothycarambat commented on GitHub (Jul 28, 2023):

If this is a remote machine that is running the dockerized instance you shouldn't have to change the VITE_API_BASE because the internal docker instance will have access to its own local network. However for you to connect to the UI on the remote machine (like EC2) you should go to HTTP://<REMOTE MACHINE IP>:3001

@timothycarambat commented on GitHub (Jul 28, 2023): If this is a remote machine that is running the dockerized instance you shouldn't have to change the VITE_API_BASE because the internal docker instance will have access to its own local network. However for _you_ to connect to the UI on the remote machine (like EC2) you should go to `HTTP://<REMOTE MACHINE IP>:3001`

yindo commented

2026-02-15 16:29:09 -05:00

@shyamsfo commented on GitHub (Jul 28, 2023):

yes, that works and the login page comes up, but the moment i type my username and password, it tries to authenticate at 127.0.0.1:3001 not the remote ip.

@shyamsfo commented on GitHub (Jul 28, 2023): yes, that works and the login page comes up, but the moment i type my username and password, it tries to authenticate at 127.0.0.1:3001 not the remote ip. ![Screenshot 2023-07-28 at 8 48 47 PM](https://github.com/Mintplex-Labs/vector-admin/assets/13055215/91c38d81-6a56-4075-af31-153069276352)

yindo commented

2026-02-15 16:29:09 -05:00

@timothycarambat commented on GitHub (Jul 31, 2023):

So to clarify, are you running docker on an EC2-like instance that is available via some IP address?

@timothycarambat commented on GitHub (Jul 31, 2023): So to clarify, are you running docker on an EC2-like instance that is available via some IP address?

yindo commented

2026-02-15 16:29:09 -05:00

@shyamsfo commented on GitHub (Aug 1, 2023):

Yes. Patch below doesnt completely fix it, but this should be the starting point of your fix.
remote.patch

@shyamsfo commented on GitHub (Aug 1, 2023): Yes. Patch below doesnt completely fix it, but this should be the starting point of your fix. [remote.patch](https://github.com/Mintplex-Labs/vector-admin/files/12231355/remote.patch)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Mintplex-Labs/vector-admin#9