[Bug]: Terminal function doesn't seem to use the Websocket domain

[davidpp]

Error Message and Logs

I'm not able to use the Terminal feature.

Looking at my console, I'm seeing an attempt to connect to my "non websocket" url:

Where other features correctly use my websocket domain:

Steps to Reproduce

1. Have a separate domain configured for WS connection
2. Try to open a terminal session on a service

Example Repository URL

No response

Coolify Version

v4.0.0-beta.347

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Ubuntu 22.04

Additional Information

No response

[LEstradioto]

How did you setup a different WS domain ?

[djsisson]

Traefik will send wss to the real-time container as long as you are accessing via the instance domain.

There is no need to change anything here

[davidpp]

Looking back at my note, the ws. subdomain is the pusher server.

The reason I had to configure a separate domain is because of Cloudflare Access since pusher is running on another port.

Knowing that this particular traffic is instead going through Traefik, it make sense that it's using the main domain then.

The issue is probably on the Cloudflare tunnel/access side then, I'll need to figure out why the error is happening

[djsisson]

@davidpp if youre using a tunnel, and the coolify domain isnt covered by a wildcard entry, then you just set the coolify suibdomain to be localhost 80, traefik will then route all traffic (http and wss) to the correct containers

[CallMeSlinky]

@davidpp I'm currently facing the same issue, please update if you find a resolution, thanks. 👍

[CallMeSlinky]

@davidpp I figured it out. My coolify is based at https://coolify.example.com I set this in Cloudflare tunnels for the terminal

[VipinGoyal]

I tried this @CallMeSlinky , but I'm still getting same problem as per OP shared screenshot.

[djsisson]

if youre still running traefik, then from the above example, all you need to do is set coolify.example.com to be localhost 80

[VipinGoyal]

I just refreshed, what I found is that original error as per OP is gone after making changes as suggested by @CallMeSlinky , but terminal is not working. @djsisson Yes Im using default proxy coming from Coolify, no change in that, Im facing weird issue, after changing port number from 8000 to 80, Im getting this error in browser i.e.

coolify.example.com redirected you too many times. Try deleting your cookies. ERR_TOO_MANY_REDIRECTS

Am I missing something ?

[djsisson]

you need to set it as http in instancedomain in coolify

[VipinGoyal]

Do you mean value of IP address / Domain in server settings ? Currently its set as host.docker.internal, since Im not using wildcard domain. When I tried updating value of IP address / Domain to coolify.example.com, I got an alert like this, so before doing this thought of checking with you just to make sure that its not going to break existing setup

[djsisson]

no on settings page - > instance domain

[VipinGoyal]

Wao, it worked thanks a lot :) 🙏 So, coolify.example.com is mapped with localhost:80 instead of 8000, is it okay, If I remove other mappings in cloudflare ( public hostname ) like 6001 for realtime and 6002 for terminal/ws path, Im about to delete those, but just confirming with you once.

[djsisson]

if you are running a proxy like traefik,

then in tunnels you only need to point to http localhost : 80 and the proxy will take care of it or https localhost : 443 if you have setup certificates and require https in your containers

[VipinGoyal]

Sure, thanks for confirmation, its really helpful. 🙏

[CallMeSlinky]

Wao, it worked thanks a lot :) 🙏 So, coolify.example.com is mapped with localhost:80 instead of 8000, is it okay, If I remove other mappings in cloudflare ( public hostname ) like 6001 for realtime and 6002 for terminal/ws path, Im about to delete those, but just confirming with you once.

Nice, this worked for me too, a lot more simple. I was receiving ERR_TOO_MANY_REDIRECTS beforehand, but I believe it's because my instance domain was set to https. 👍