Skip to content

Commit 385a9fe

Browse files
authored
docs(dashboard-inaccessible): port conflict section (#429)
1 parent 56abc00 commit 385a9fe

File tree

1 file changed

+19
-0
lines changed

1 file changed

+19
-0
lines changed

docs/troubleshoot/dashboard/dashboard-inaccessible.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -55,6 +55,25 @@ If the dashboard isn’t accessible via the IP address, then follow these steps:
5555
_(Replace `NAME` with your actual container name)_
5656
- **Test:** After restarting, try accessing `http://203.0.113.1:8000` _(Replace `203.0.113.1` with your actual server IP address)_ again. If this doesn't work, skip to [step 5](#_5-getting-further-assistance)
5757

58+
### C. Conflict Coolify-Related Containers Port
59+
60+
Sometimes, the issue occurs if a non-Coolify container is using the same port (e.g., port 8000) as Coolify's dashboard, causing a conflict.
61+
62+
- **Steps:**
63+
64+
1. SSH into your server.
65+
2. Stop all Docker containers gracefully:
66+
```bash
67+
docker stop $(docker ps -q)
68+
```
69+
3. Start only the containers related to Coolify:
70+
```bash
71+
docker start $(docker ps -a -q --filter "name=coolify")
72+
```
73+
4. Try accessing your Coolify dashboard again. The dashboard should now be accessible since conflicts on port 8000 are cleared.
74+
75+
- **Next:** Check your containers for the same port as your Coolify instance through the Coolify dashboard and change the port accordingly (don't forget to verify firewall rules)
76+
5877
## 4. Addressing Proxy-Related Issues
5978

6079
If the dashboard is accessible via the server IP but not through your custom domain, then follow these steps:

0 commit comments

Comments
 (0)