fix: connection to local server terminal#1066
Merged
Siumauricio merged 6 commits intoDokploy:canaryfrom Jan 10, 2025
Merged
Conversation
Siumauricio
approved these changes
Jan 10, 2025
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
iproute2to dependecies in Dockerfile (required forip routecommand)authorized_keysfile on the server. Also added similar command for granting permission access to the/etc/dokploy/sshdirectory when needed.The last approach sadly only worked in local dev server, the new approach was tested locally on a built Docker image and Dokploy running inside Docker container instead of local dev server, and it connected fine.
Permission denied error with a command to fix it:

Access error for generated private SSH key with a command to authorize the key:

Successfull connection after running the above commands:
