Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

martin

Re: WinSCP not working with specific webdav server

Does your university have another supported WebDAV client? Does it work? Can you post its log file?
kwilliams

WinSCP not working with specific webdav server

Hi,

I've been using WinSCP for about two years now for work at a university and it suddenly stopped working on Tuesday. I don't know what's wrong with it. I suspect it's something on our end, but I don't know what kinds of questions to ask. WinSCP is not "officially" supported by our support so I won't get any help unless I ask the right questions.

I am using Version 5.13.1 (Build 8265) on Windows 10.
I am using WebDAV with SSL encryption. I am using the GUI (Commander).

Here is the error message I'm getting:
Could not read status line: connection timed out

Connection failed.


Here is the most recent log (with sensitive information redacted):

. 2018-05-03 12:42:35.585 --------------------------------------------------------------------------

. 2018-05-03 12:42:35.616 ah_create, for WWW-Authenticate
. 2018-05-03 12:42:35.616 Sending request headers:
. 2018-05-03 12:42:35.632 OPTIONS /content/enforced/(redacted)/ HTTP/1.1

. 2018-05-03 12:42:35.632 User-Agent: WinSCP/5.13.1 neon/0.30.2

. 2018-05-03 12:42:35.632 Keep-Alive:

. 2018-05-03 12:42:35.632 Connection: TE, Keep-Alive

. 2018-05-03 12:42:35.632 TE: trailers

. 2018-05-03 12:42:35.632 Host: (redacted)
. 2018-05-03 12:42:35.632 Sending request-line and headers:
. 2018-05-03 12:42:35.632 Doing DNS lookup on (redacted)...
. 2018-05-03 12:42:35.632 req: Connecting to (redacted)
. 2018-05-03 12:42:35.632 Doing SSL negotiation.
. 2018-05-03 12:42:35.648 ssl: Verify callback @ 1 => 20
. 2018-05-03 12:42:35.648 ssl: Verify failures |= 8 => 8
. 2018-05-03 12:42:35.663 Verifying certificate for "(redacted)" with fingerprint (redacted) and 08 failures
. 2018-05-03 12:42:35.679 Certificate verified against Windows certificate store
. 2018-05-03 12:42:35.679 Using TLSv1.2, cipher TLSv1/SSLv3: (redacted), 2048 bit RSA
. 2018-05-03 12:42:35.679 Request sent; retry is 0.
. 2018-05-03 12:42:50.680 Aborted request (-2): Could not read status line
. 2018-05-03 12:42:50.681 sess: Closing connection.
. 2018-05-03 12:42:50.683 sess: Connection closed.
. 2018-05-03 12:42:50.684 Request ends, status 0 class 0xx, error line:
. 2018-05-03 12:42:50.684 Could not read status line: connection timed out
. 2018-05-03 12:42:50.684 Request ends.
. 2018-05-03 12:42:50.684 sess: Destroying session.
* 2018-05-03 12:42:50.700 (EFatal) Network error: Connection to "(redacted)" timed out.
* 2018-05-03 12:42:50.700 Could not read status line: connection timed out
* 2018-05-03 12:42:50.700 Connection failed.


I've tried forgetting and setting up the webdav sites fresh. I've tried uninstalling and reinstalling WinSCP. I've tried adding winscp.exe as an exception to Windows Firewall.

I am able to connect to this webdav using other programs (BitKinex, Transmit on mac) but I much prefer WinSCP. I can connect to other webdav servers using WinSCP. It's just my particular webdav and WinSCP that aren't getting along.

If I can provide any additional information I will be happy to provide it.