Skip to content

Commit f08f35c

Browse files
committed
Merge branch 'next' into v4.x
2 parents 5244b76 + 2f5a77f commit f08f35c

File tree

2 files changed

+50
-0
lines changed

2 files changed

+50
-0
lines changed
87 KB
Loading

docs/troubleshoot/applications/no-available-server.md

Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -179,6 +179,56 @@ Make sure the protocol in your domain configuration matches how you want to acce
179179

180180
Ensure that `Rolling Updates` are correctly configured. See [Rolling Updates documentation](/knowledge-base/rolling-updates)
181181

182+
183+
### Solution 5: Update Traefik to Fix Docker API Version Issue
184+
185+
**Symptoms:**
186+
- "No Available Server" error appears
187+
- Coolify proxy logs shows the following error message:
188+
```py
189+
Error response from daemon: client version 1.24 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer version
190+
```
191+
- Application container is running healthy but visiting the domain shows "No Available Server"
192+
193+
194+
**Root Cause:**
195+
The problem happened because Traefik was hard-coding Docker API versions.
196+
197+
::: info
198+
The Traefik team has released a fix in **v2.11.31** and **v3.6.1**. Starting from v2.11.31 and v3.6.1, Traefik will now auto-negotiate the Docker API version, so this issue shouldn't happen again.
199+
:::
200+
201+
**Solution:**
202+
203+
Coolify won't automatically update Traefik for existing servers.
204+
205+
::: warning Why Coolify don't auto-update for existing servers
206+
Some users have custom configurations (like DNS challenges) that could break when updating to a newer Traefik version. Please check the [Traefik changelog](https://github.com/traefik/traefik/releases) before updating.
207+
208+
- If you're using the default Coolify Traefik configurations, you're safe to update to v3.6.1 without any issues.
209+
- If you're currently on Traefik v2 and don't want to upgrade to v3, you can update to the patched v2.11.31 instead.
210+
:::
211+
212+
If you're already using Coolify, you'll need to update Traefik manually by follow these steps:
213+
214+
1. **Navigate to Proxy Configuration:**
215+
- Go to your Coolify dashboard (https://app.coolify.io/ for cloud users) → Servers → [Your Server] → Proxy → Configuration
216+
217+
2. **Change Traefik Version:**
218+
- Change the version to: `v3.6.1` (or `v2.11.31` if staying on v2)
219+
220+
3. **Restart Proxy:**
221+
- Click `Restart Proxy`
222+
223+
<ZoomableImage src="/docs/images/troubleshoot/applications/bad-gateway/no-available-server/update-traefik-version.webp" alt="coolify proxy traefik version update" />
224+
225+
226+
**Notes:**
227+
- You need to do this on every server connected to your Coolify instance
228+
- This applies to both self-hosted and Coolify Cloud users
229+
- (Cloud users: Traefik runs on **your own server** not Coolify’s so you’ll need to update it yourself by following the guide above)
230+
- If you have changed Docker daemon configs to set Minimum supported API version, then we recommend to revert it as it could potentially cause problems in the future.
231+
182232
## Advanced Debugging
183233

184234
### Check Traefik Configuration

0 commit comments

Comments
 (0)