[Bug]: Terminal not acessible without external proxy and tunnel

[yWilliamLima]

Error Message and Logs

I installed Coolify on a self-hosted server
I'm not using any type of proxy or tunnel
I can't access the terminal via web access

Steps to Reproduce

1. Install Coolify on a Server
2. Set up a custom domain
3. Navigate to Terminal Page
   ERROR: Terminal websocket connection lost.

Example Repository URL

No response

Coolify Version

v4.0.0-beta.460

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Debian 12

Additional Information

Running a curl command externally on my domain and port is working correctly:

curl coolify.example.net:6002/ready
OK

I noticed that on the web it's connecting to the websocket without port 6002, perhaps that's the problem:

Request URL: wss://coolify.example.net/terminal/ws

However, I'm not using any proxy or tunnel to route traffic to the specific port. Can I do this directly through Coolify?

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Possible Duplicates

• [Bug]: Cannot connect to terminal #6074

Related Issues

• Bug: host host.docker.internal not in authorized list #5823
• [Bug]: Setting up a server using cloudflare tunnel #5944
• [Bug]: WebSocket connection fails when accessing Coolify via HTTPS - Terminal and real-time features not working #5968
• WebSocket connection to /terminal/ws fails when accessing Coolify dashboard via coolify-proxy on same host #6026

👤 Suggested Assignees

• easis
• yipfram
• maslyankov
• DigiRift-frontend
• jk779

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[djsisson]

when using the website, the terminal is proxied via the path /terminal/ws but this proxy is not set within the coolify container, but only when a domain has been set for coolify, a dynamic config is created, and then that path is proxied to port 6002 via your proxy.

so if you are browsing via a domain, how have you set this up? (this does not work direct to ip:8000)

[yWilliamLima]

I simply pointed the domain to the public IP and configured it within the settings.

[djsisson]

how are you proxying traffic to this container, your title makes it seem like you are not using the coolify proxy, if you are not you would need to do this path proxy yourself

@peaklabs-dev is there a reason the ws proxies are not done directly in nginx running inside coolify, instead of being done outside in the proxy? this would remove the need to make 6001/6002 public as well as make proxying simpler, as all traffic could be directed to the coolify container

[yWilliamLima]

I apologize, I'll correct the title; I'm not using any external proxy, just everything that comes with the Coolify installation.

[djsisson]

can you check server - proxy - dynamic (you should see the file containing the routes for the coolify domain as well as the two path proxies
also what container are you trying to open a terminal in, as not all containers have a shell
lastly you mention tunnel, if you are using a tunnel what have you set for the coolify domain?

[yWilliamLima]

The configuration is all default:

I have several containers, or even the server itself, but none of them connect:

[djsisson]

who is your domain provider? if its cf check your waf rules and make sure you're not using flexible ssl, a normal installation has no issues using the terminal, so there is something blocking it.

[yWilliamLima]

There's no WAF or SSL; I'm just pointing an A record from RegistroBR to my server's public IP.

I also noticed that when I access the URL https://coolify.example.net/terminal/ws via the web, it returns "not found"
however, the container logs show that the request is arriving:

docker logs coolify-realtime
2026-01-06 17:22:55 [TERMINAL] Authentication error: connect ECONNREFUSED 10.0.1.16:8080
2026-01-06 17:23:00 [TERMINAL] Authentication error: connect ECONNREFUSED 10.0.1.16:8080
2026-01-06 17:23:30 [TERMINAL] Authentication error: connect ECONNREFUSED 10.0.1.16:8080

And the initialization is proceeding normally:

2026-01-06 12:45:25 [TERMINAL] Coolify realtime terminal server listening on port 6002. Let the hacking begin!
2026-01-06 12:45:27 [SOKETI]
2026-01-06 12:45:27 [SOKETI] 🕵️‍♂️ Initiating metrics endpoints...
2026-01-06 12:45:27 [SOKETI]
2026-01-06 12:45:27 [SOKETI] 🎉 Server is up and running!
2026-01-06 12:45:27 [SOKETI] 📡 The Websockets server is available at 127.0.0.1:6001
2026-01-06 12:45:27 [SOKETI] 🔗 The HTTP API server is available at http://127.0.0.1:6001
2026-01-06 12:45:27 [SOKETI] 🎊 The /usage endpoint is available on port 9601.
2026-01-06 12:45:27 [SOKETI]
2026-01-06 12:45:27 [SOKETI] (node:8) NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023.
2026-01-06 12:45:27 [SOKETI]
2026-01-06 12:45:27 [SOKETI] Please migrate your code to use AWS SDK for JavaScript (v3).
2026-01-06 12:45:27 [SOKETI] For more information, check the migration guide at https://a.co/7PzMCcy
2026-01-06 12:45:27 [SOKETI] (Use `node --trace-warnings ...` to show where the warning was created)

[djsisson]

have you changed the coolify port? as that looks like its trying to connect to the coolify container and can't

[yWilliamLima]

Initially I didn't change anything, and I don't even know where to change that. Can I validate it?

From inside the coolify-realtime container:

/terminal # curl 10.0.1.16:8080
curl: (7) Failed to connect to 10.0.1.16 port 8080 after 0 ms: Could not connect to server

/terminal # ping 10.0.1.16
PING 10.0.1.16 (10.0.1.16): 56 data bytes
64 bytes from 10.0.1.16: seq=0 ttl=64 time=0.060 ms
64 bytes from 10.0.1.16: seq=1 ttl=64 time=0.116 ms
64 bytes from 10.0.1.16: seq=2 ttl=64 time=0.076 ms
--- 10.0.1.16 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.060/0.084/0.116 ms

/terminal # telnet 10.0.1.16 8080
telnet: can't connect to remote host (10.0.1.16): Connection refused

[djsisson]

have you enabled ipallowed list ? you cant directly connect to coolify from realtime without authentication

can you check coolify.example.net/terminal/auth/ips

[yWilliamLima]

This link doesn't work for me, and I don't remember configuring an IP list

I disabled the domain and tested using the internal IP address, and the problem is exactly the same: