WinSCP 5.13.5 (build 8967) Can't create a directory.
OS: Win 10
WinSCP: 5.13.5 (Build 8967)
Protocol: SFTP
Port: 2222 (iPage website SFTP connection port)
Issue:
While I can successfully login to my iPage domain and transfer files into already existing directories, I can not create new directories (I can delete existing directories) either using the F7 key, or by selecting from the menu.
I've shut off my VPN and firewall and still see the same results. If I create the directory using the iPage web interface, I can download files into the newly created directories, but again can't create any subdirectories.
I tried opening a putty terminal to run the "mdkir -m7555 Junk" command and received the message that no pty access was granted by the remote system.
I've been in contact with the iPage technical support and they claim they were able to create a directory using Filezilla (I confirmed the directory was present) using the SFTP protocol. I don't know what's different about the SFTP implementation that might cause this issue.
I have attached the log file to this issue.
WinSCP: 5.13.5 (Build 8967)
Protocol: SFTP
Port: 2222 (iPage website SFTP connection port)
Issue:
While I can successfully login to my iPage domain and transfer files into already existing directories, I can not create new directories (I can delete existing directories) either using the F7 key, or by selecting from the menu.
I've shut off my VPN and firewall and still see the same results. If I create the directory using the iPage web interface, I can download files into the newly created directories, but again can't create any subdirectories.
I tried opening a putty terminal to run the "mdkir -m7555 Junk" command and received the message that no pty access was granted by the remote system.
I've been in contact with the iPage technical support and they claim they were able to create a directory using Filezilla (I confirmed the directory was present) using the SFTP protocol. I don't know what's different about the SFTP implementation that might cause this issue.
I have attached the log file to this issue.