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

[Error]: Web sockets errors #4762

Open
id535 opened this issue May 23, 2024 · 9 comments
Open

[Error]: Web sockets errors #4762

id535 opened this issue May 23, 2024 · 9 comments
Labels
blocked: waiting-response waiting a response from the user

Comments

@id535
Copy link

id535 commented May 23, 2024

I am having exactly the issue described here:
#4407

I tried reinstalling with docker and docker compose, reverse proxied with caddy then with Nginx (as per your recommendation https://www.activepieces.com/docs/install/setup-ssl) , but still have these sockets errors and and that testing circle spins forever...

Firefox can’t establish a connection to the server at wss://wss/socket.io/?EIO=4&transport=websocket.

No errors in the docker logs

Tried multiple browers too.

This is my Nginx config

server {
    listen 80;
    listen [::]:80;

    server_name domain.com www.domain.com;

    return 301 https://$server_name$request_uri;
}

server {
    listen 443 ssl http2;
    listen [::]:443 ssl http2;

    server_name domain.com www.domain.com;

    ssl_certificate /etc/letsencrypt/live/domain.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/domain.com/privkey.pem;

    location / {
        proxy_pass http://localhost:8080;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;
    }
}
@id535 id535 closed this as completed May 24, 2024
Copy link

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If this issue is continuing with the latest stable version of Activepieces, please open a new issue that references this one.

@id535 id535 reopened this May 24, 2024
@id535
Copy link
Author

id535 commented May 24, 2024

Nevermind I have the issue in 0.26.1 too.

@abuaboud
Copy link
Contributor

Hmm that's odd

Did you try another browser? does it show same error?

@id535
Copy link
Author

id535 commented May 24, 2024

Yes, I usually use chrome and downloaded firefox just to double check it's not a browser issue...

@abuaboud
Copy link
Contributor

@id535 Do you use cloudflare or other services that is on top of the reverse proxy?

@id535
Copy link
Author

id535 commented May 27, 2024

@id535 Do you use cloudflare or other services that is on top of the reverse proxy?

No. Also, the second time, I installed it on a separate digitalocean droplet to have a clean installation. Docker was preinstalled already. Just installed activepieces, nginx and certbot for ssl certificate. And i followed DigitalOcean's tutorial for those, so I don't think I installed it wrong or anything like that. Apart from that, nothing else.

I am using a subdomain though. Not sure if that makes any difference as I see you have activepieces on the cloud.activepieces.com subdomain too but I thought maybe there's some extra configurations I need to do for that?

@abuaboud abuaboud added the 🤷‍♂️🤷‍♀️ untriaged Need attention from maintainer in activepieces label May 28, 2024
@abuaboud
Copy link
Contributor

To isolate the problem, whether it's from the load balancer or Activepieces, can you try to access Activepieces directly via the IP address of the droplet and attempt to run 'Test flow'? Does it work?

@abuaboud abuaboud added blocked: waiting-response waiting a response from the user and removed 🤷‍♂️🤷‍♀️ untriaged Need attention from maintainer in activepieces labels May 28, 2024
@id535
Copy link
Author

id535 commented May 29, 2024

@abuaboud The websocket errors dissapeared and i get a few of these:
[object Object]:1 Uncaught SyntaxError: Unexpected token '<' (at [object Object]:1:1)
But the flow test works actually
Also, if you're referring to digitalocean load balancers I don't have one.

@jridevapp
Copy link

I am getting wss failed on a fresh deploy on render too.

WebSocket connection to 'wss://wss/socket.io/?EIO=4&transport=websocket' failed:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked: waiting-response waiting a response from the user
Projects
None yet
Development

No branches or pull requests

3 participants