Open suyashdb opened 3 days ago
@suyashdb
Are you running docker compose in a remote server?
If yes, what's your environment
under the skyvern-ui in your docker-compose.yml
?
@wintonzheng here the env under skyvern-ui. Yes, i am running docker compose in a remote server.
`
skyvern-ui:
image: public.ecr.aws/skyvern/skyvern-ui:v0.1.35
restart: on-failure
ports:
- 8080:8080
- 9090:9090
volumes:
- ./artifacts:/data/artifacts
- ./videos:/data/videos
- ./har:/data/har
- ./.streamlit:/app/.streamlit
environment:
- VITE_WSS_BASE_URL=ws://localhost:8000/api/v1
# - VITE_API_BASE_URL=
# - VITE_SKYVERN_API_KEY=
depends_on:
skyvern:
condition: service_healthy
@suyashdb I think this is the problem:
- VITE_WSS_BASE_URL=ws://localhost:8000/api/v1
I think we would expect this url to be pointing to the image running the Skyvern instance (not UI instance) -- ie this shouldn't be localhost
# if you want to run skyvern on a remote server,
# you need to change the host in VITE_WSS_BASE_URL and VITE_API_BASE_URL to match your server ip
So you want to set up these two environment variables under the skyvern-ui service inside docker-compose.yml:
environment:
- VITE_WSS_BASE_URL=ws://{your ec2 ip}:8000/api/v1
- VITE_API_BASE_URL=http://{your ec2 ip}:8000/api/v1
Thanks @wintonzheng!
for ec2 i will follow what you mentioned. Are there any changes expected if my docker containers are local. we have both being tested.
All three containers are running correctly, however when i click on the task creation i get 404 error. no docker logs which talks about any error.