[Bug]: realtime works on ip but not on domain

terion-name commented 3 months ago

Description

I've deployed coolify on hetzner. No firewals yet. Everyuthing worked fine when I was accessing it via ip. Then I've added an instance domain. Also seems to work fine, except realtime: websocket (wss://example.com/app/....) is not working.

There are no cloudflare tunnels or something like this, simple dns, basic setup

Minimal Reproduction (if possible, example repository)

n/a

Exception or Error

No response

Version

v4.0.0-beta.319

Cloud?

[ ] Yes
[X] No

andrasbacsai commented 3 months ago

How is your dynamic proxy configuration looks like?

krokosik commented 2 months ago

I had the same issue on my VPS. I wanted to try coolify so I installed it using the script. However, I already had Nginx Proxy Manager set up together with other services running on my instance. The proxying is done by domain, so I just route the coolify.example.com requests to http://coolify:8000. This works since I added my NPM container to the coolify network. The UI seems to work, but I also get the error posted here with the proxy disabled in Coolify settings. I tried setting the domain to coolify.example.com but it didn't work.

I also have WebSocket support enabled in NPM and checked browser console to see that the frontend cannot establish a connection with wss://coolify.example.com...

The WebSocket option has worked for other services like Mattermost, so I doubt this is the reason for that. However, I just wanted to try out Coolify and it didn't work so I gave up. I don't know what else to try but since others have this issue, I would gladly help with narrowing down the root cause :)

coollabsio / coolify