Failed to connect to the remote server in the deployment after successfully setting up ssh
Answered
After updating to pycharm 2021, I have a strange problem. I can successfully connect to the remote server via ssh, but cannot connect to it in the deployment setting. I do not have such problem when using pycharm 2020. I am using windows 10 1909.
Please sign in to leave a comment.
Unfortunately, it is hard to say anything for sure without checking logs first. Would it be possible to enable the extended logging, reproduce the error message and collect&share log files?
To increase the deployment actions logging level, please add the following lines to the "Help > Diagnostic Tools > Debug Log Settings" section:
#com.intellij.ssh
#com.jetbrains.plugins.webDeployment
Afterwards, logs can be collected via the "Help > Collect Logs" menu option.
To upload files, you may use JetBrains Uploads services, just let me know the upload id after:
https://uploads.jetbrains.com/
Hi, I uninstalled pycharm 2021.1 and reinstalled pycharm 2020.3, but the problem is the same. I do not have the problem using pycharm 2020.3 before the updating to 2021.1.
The uploaded log file is 2021_04_14_Xbq51AaBJnFZb39P
Hello,
Thanks for sharing the log files pack.
Could you please double-check if you are able to access the /*/home/home3/31/*/unix//work (I hope that it is clear what the real path is as I have used * to hide some parts of it) on your SFTP server with any other SFTP client?
Is there any chance that "/work" is a symlink?
Vasiliy Yur Hi, currently `work` is a symlink. `work` was a folder that I stored the code before this week. I decided to change the folder structure this week. The original `work` folder was renamed to another name and `work` became a symlink pointing to another folder. I now realize this is a dangerous operation.
I changed the deployment setting in the mappings, or even clear it, but it does not work. Maybe there is some cache there.
How exactly did you change the mapping, does it point to the directory without the symlink now? Would it be possible to try creating a new deployment configuration from scratch (do not remove an old one yet) and set it as default, will it work?
I am having the same problem. Has anyone been able to solve it, please
Abdulsalam Abass
Please file an issue to https://youtrack.jetbrains.com/issues/WI and attach your idea.log file from Help | Show Log in...