skyvern icon indicating copy to clipboard operation
skyvern copied to clipboard

[Bug] Status Code 404: Task not created

Open suyashdb opened this issue 1 year ago • 5 comments

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.

Screenshot 2024-10-28 at 8 49 12 PM

suyashdb avatar Oct 29 '24 03:10 suyashdb

@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 avatar Oct 29 '24 07:10 wintonzheng

@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 avatar Oct 29 '24 19:10 suyashdb

@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

suchintan avatar Oct 30 '24 04:10 suchintan

@suyashdb https://github.com/Skyvern-AI/skyvern/blob/54674c16cc9fc39148ea55e7ce8b7c50e61f12e9/docker-compose.yml#L70-L71

    # 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

wintonzheng avatar Oct 30 '24 06:10 wintonzheng

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.

suyashdb avatar Oct 30 '24 16:10 suyashdb

Referencing localhost (or 0.0.0.0) will work if all containers are running on the same node

suchintan avatar Nov 03 '24 05:11 suchintan

same here, i try with internal docker ip, 0.0.0.0 and external ip, all still return as 404 error

atrix228 avatar Nov 06 '24 12:11 atrix228

atrix228

still getting 404's here

rublev avatar Jan 04 '25 03:01 rublev