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
{{ message }}
This repository has been archived by the owner on Jun 30, 2020. It is now read-only.
I have an user which has a password with special symbols (~!?$/...). When i have setup the uri on code-workspace file, the remote folder became yellow and the ! shows an error like this "could not resolve workspace folder". Then i put ?debug=1 on the end, to see whats going on under the hood. The debug log said "Invalid username" which made no sense the username is right, checked it in WinSCP and Putty. Then i thought a little bit about it, urlencoded the special characters and now it works.
Suggestion: Please document that when you have a password with special characters that you have to "urlencode" these. This would help others not wasting much time figuring out whats wrong, this bugger stole me 45 mins.
BTW: Great job on that extension, i absolutely like it having VS Code not needing any SFTP/SCP client to remote edit files :)
Best regards
T. Schumacher
The text was updated successfully, but these errors were encountered:
Following problem with sftp:
I have an user which has a password with special symbols (~!?$/...). When i have setup the uri on code-workspace file, the remote folder became yellow and the ! shows an error like this "could not resolve workspace folder". Then i put ?debug=1 on the end, to see whats going on under the hood. The debug log said "Invalid username" which made no sense the username is right, checked it in WinSCP and Putty. Then i thought a little bit about it, urlencoded the special characters and now it works.
Suggestion: Please document that when you have a password with special characters that you have to "urlencode" these. This would help others not wasting much time figuring out whats wrong, this bugger stole me 45 mins.
BTW: Great job on that extension, i absolutely like it having VS Code not needing any SFTP/SCP client to remote edit files :)
Best regards
T. Schumacher
The text was updated successfully, but these errors were encountered: