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

BUG: Skyvern sensitive to port change #1277

Open
gwpl opened this issue Nov 27, 2024 · 4 comments
Open

BUG: Skyvern sensitive to port change #1277

gwpl opened this issue Nov 27, 2024 · 4 comments
Labels

Comments

@gwpl
Copy link

gwpl commented Nov 27, 2024

When I changed ports in docker-compose file to others , then Skyvern UI create new task started returning "network error" box .

However, after reverting this change and restarting, skyvern was working back again on default ports.

@prajwal2431
Copy link

is this issue still open i want to work on it

@gwpl
Copy link
Author

gwpl commented Dec 8, 2024

still not working, example port change:

diff --git a/docker-compose.yml b/docker-compose.yml
index a94b875..8e0ce9a 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -3,8 +3,8 @@ services:
     image: postgres:14-alpine
     restart: always
     # comment out if you want to externally connect DB
-    # ports:
-    #   - 5432:5432
+    ports:
+      - 5048:5432
     volumes:
       - ./postgres-data:/var/lib/postgresql/data
     environment:
@@ -23,7 +23,7 @@ services:
     restart: on-failure
     # comment out if you want to externally call skyvern API
     ports:
-      - 8000:8000
+      - 5049:8000
     volumes:
       - ./artifacts:/data/artifacts
       - ./videos:/data/videos
@@ -59,8 +59,8 @@ services:
     image: public.ecr.aws/skyvern/skyvern-ui:latest
     restart: on-failure
     ports:
-      - 8080:8080
-      - 9090:9090
+      - 5050:8080
+      - 5051:9090
     volumes:
       - ./artifacts:/data/artifacts
       - ./videos:/data/videos

@prajwal2431
Copy link

To resolve the issue caused by changing ports in the docker-compose.yml file, ensure that all related environment variables, such as VITE_WSS_BASE_URL, are updated to reflect the new ports. For example, if the Skyvern API port changes to 5049, set VITE_WSS_BASE_URL=ws://localhost:5049/api/v1. After updating the configuration, rebuild and restart the containers using docker-compose down and docker-compose up --build. Clear your browser cache or perform a hard refresh (Ctrl+Shift+R) to load the updated settings. Additionally, verify service communication by checking the logs (docker-compose logs -f). Ensuring consistency across port configurations should resolve the "network error" issue.

@orapaorapa
Copy link

docker-compose(dot)yml.txt
After rebuilding with 'docker-compose up -build' , i launch the navigation panel on 192.168.1.32:8080 , works fine ...but when i try 'new task' i have : unexpected application error! 404 not found . The second error is when i try from prompt : 'error creating task from prompt : request failed with status error 400' . ??? thx

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

No branches or pull requests

4 participants