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
Allowing full server best practice to disable root remote SSH login
Describe the solution you'd like
When attempting to deploy to a remote server using a non-root user, even one with full sudo privileges, the deployment fails without displaying any error messages or reasons. The process fails silently. However, if you switch the server's login user to root on the Dokploy dashboard settings and re-enable RootLogin, the deployment works as expected. This means that for now, root login must be enabled which may be problematic for some.
Describe alternatives you've considered
The workaround I consider for this is to check if sudo password prompts enabled for that user, if it's not it fails otherwise all sudo commands can be ran without the password prompt.
Additional context
No response
Will you send a PR to implement it?
Maybe, need help
The text was updated successfully, but these errors were encountered:
What problem will this feature address?
Allowing full server best practice to disable root remote SSH login
Describe the solution you'd like
When attempting to deploy to a remote server using a non-root user, even one with full sudo privileges, the deployment fails without displaying any error messages or reasons. The process fails silently. However, if you switch the server's login user to root on the Dokploy dashboard settings and re-enable RootLogin, the deployment works as expected. This means that for now, root login must be enabled which may be problematic for some.
Describe alternatives you've considered
The workaround I consider for this is to check if sudo password prompts enabled for that user, if it's not it fails otherwise all sudo commands can be ran without the password prompt.
Additional context
No response
Will you send a PR to implement it?
Maybe, need help
The text was updated successfully, but these errors were encountered: