[Bug]: Deployments keep failing.

[thejm-12]

Error Message and Logs

Deployments keep failing. Deleting the mux file fixes the issue but the file keeps getting created. I am not sure what is creating the mux file that causes the deployments to fail.

A few of my containers include node, mariadb, grafana, phpmyadmin, clickhouse, redis, dragonfly

Error:

mux_client_request_session: session request failed: Session open refused by peer /var/www/html/storage/app/ssh/mux/mux_ already exists, disabling multiplexing

Steps to Reproduce

1. Try to deploy any container

Example Repository URL

No response

Coolify Version

v4.0.0-beta.397

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Ubuntu 24.04

Additional Information

No response

[andrasbacsai]

Can you please update to the latest version and let me know if it is still an issue?

[thejm-12]

Can you please update to the latest version and let me know if it is still an issue?

@andrasbacsai I'll let you know. It might take up to 1 week to know for sure. The file that prevented the deployments was normally created randomly or at least appeared random.

[gerwitz]

This smells like #4173, which has been closed but is still an issue for many.

[thejm-12]

@andrasbacsai it hasn't happened anymore. I'm not sure if it was actually fixed or just a coincidence. Closing for now.

[thejm-12]

Spoke too soon. Just got the error again

[gerwitz]

I have opened discussion #5207 to track this persistant but not pervasive problem

[thejm-12]

@andrasbacsai So the error causes the commit to appear like this... Commit: mux_cli

[twhite96]

I have been experiencing this the past week. Deploying static sites from different git sources always fails with the error:

Oops something is not okay, are you okay? 😢
fatal: could not read Username for 'https://git.tld': No such device or address
Deployment failed. Removing the new version of your application.

It deployed successfully on April 26th but it fails today.

[thejm-12]

I have been experiencing this the past week. Deploying static sites from different git sources always fails with the error:

Oops something is not okay, are you okay? 😢 fatal: could not read Username for 'https://git.tld': No such device or address Deployment failed. Removing the new version of your application. It deployed successfully on April 26th but it fails today.

@twhite96 Looks like your error is unrelated to this. You should open your own GitHub issue

[Cristy94]

I am still getting this with version 418

mux_client_request_session: session request failed

2025-May-24 12:50:43.467382
Oops something is not okay, are you okay? 😢
2025-May-24 12:50:43.474584
mux_client_request_session: session request failed: Session open refused by peer
2025-May-24 12:50:43.474584
ControlSocket /var/www/html/storage/app/ssh/mux/mux_csgs0g0 already exists, disabling multiplexing
2025-May-24 12:50:43.474584
#0 building with "default" instance using docker driver
2025-May-24 12:50:43.474584
2025-May-24 12:50:43.474584
#1 [internal] load .dockerignore
2025-May-24 12:50:43.474584
#1 transferring context:
2025-May-24 12:50:43.474584
#1 transferring context: 2B done
2025-May-24 12:50:43.474584
#1 DONE 0.2s
2025-May-24 12:50:43.474584
2025-May-24 12:50:43.474584
#2 [internal] load build definition from Dockerfile
2025-May-24 12:50:43.474584
#2 transferring dockerfile: 465B done
2025-May-24 12:50:43.474584
#2 DONE 0.2s
2025-May-24 12:50:43.474584
Dockerfile:1
2025-May-24 12:50:43.474584
--------------------
2025-May-24 12:50:43.474584
1 | >>> mux_client_request_session: session request failed: Session open refused by peerControlSocket /var/www/html/storage/app/ssh/mux/mux_csgs0g0 already exists, disabling multiplexing# Use the official Node.js image from the Docker Hub
2025-May-24 12:50:43.474584
2 |     FROM node:18
2025-May-24 12:50:43.474584
3 |
2025-May-24 12:50:43.474584
--------------------
2025-May-24 12:50:43.474584
ERROR: failed to solve: dockerfile parse error on line 1: unknown instruction: mux_client_request_session:
2025-May-24 12:50:43.474584
exit status 1
2025-May-24 12:50:43.481432
Deployment failed. Removing the new version of your application

[Cristy94]

This fixed it for me: removing the contents of /data/coolify/ssh/mux

https://github.com/coollabsio/coolify/issues/4173#issuecomment-2599695117

[quarkcore]

Im recently having issues that: ssh -O check -o ControlPath=/var/www/html/storage/app/ssh/mux/mux_lgookwssog8w0kw408s4sgoo <user>@<host> is timing out when starting a deployment.

Clearing the directory helped as a first fix.

[peturgeorgievv]

I have the same issue from time to time, I do believe it happens when new deployment happen, but in general this was during the night when there were NO deployments.

mux_client_request_session. I have no idea how it happened, or why, as it's pretty random but it's quite scary.

Removeing all from ssh/mux/ when I do docker restart on the coolify server it returns 3 SSH stuff there