You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error: bash: Zeile 1: /usr/lib/sftp-server: Datei oder Verzeichnis nicht gefunden scp: Connection closed
(Translation: Error: bash: Zeile 1: /usr/lib/sftp-server: File or directory not found scp: Connection closed)
Steps to Reproduce
I have no idea on how to reproduce this issue.
Add a server which has DietPi 9.8.0 installed as an OS
Try to deploy Uptime Kuma?
Example Repository URL
No response
Coolify Version
v4.0.0-beta.379
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
Debian 12 / DietPi v9.8.0
Additional Information
The service in question is Uptime Kuma, the server in question is a Raspberry Pi 3B+. The Raspberry Pi 3B+ and the OS are up to date.
I am able to restart/deploy the same service on other servers.
Last time I restarted/deployed this service on this server was with version v4.0.0-beta.348 where it worked without issues.
The text was updated successfully, but these errors were encountered:
alxhu-dev
added
🐛 Bug
Reported issues that need to be reproduced by the team.
🔍 Triage
Issues that need assessment and prioritization.
labels
Dec 22, 2024
Error Message and Logs
Error: bash: Zeile 1: /usr/lib/sftp-server: Datei oder Verzeichnis nicht gefunden scp: Connection closed
(Translation:
Error: bash: Zeile 1: /usr/lib/sftp-server: File or directory not found scp: Connection closed
)Steps to Reproduce
I have no idea on how to reproduce this issue.
Example Repository URL
No response
Coolify Version
v4.0.0-beta.379
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
Debian 12 / DietPi v9.8.0
Additional Information
The service in question is Uptime Kuma, the server in question is a Raspberry Pi 3B+. The Raspberry Pi 3B+ and the OS are up to date.
I am able to restart/deploy the same service on other servers.
Last time I restarted/deployed this service on this server was with version v4.0.0-beta.348 where it worked without issues.
The text was updated successfully, but these errors were encountered: