Menu

#2097 Connection via http proxy not possible

KeePass_2.x
closed
nobody
Proxy (3)
5
2016-04-19
2016-02-12
veeroohre
No

Hi

I am behind a corporate firewall (BlueCoat) which I tunnel through via Cntlm and Putty. With Firefox I can use the http proxy provided Putty without problems (it works with other programs like SCP too). But when I try to connect to a file on a webdav server I get the error message "Die zugrundeliegende Verbindung wurde geschlossen: Die Verbindung wurde unerwartet getrennt". In english it would be something like "The underlying connection was closed: The connection was terminated unexpectedly".

Since the update check does not work I think KeePass has in general problems with using the proxy provided by Putty. Due to the firewall I cannot use a different proxy type like Socks. Unfortunately I have no further information I can share. Is there a log file or a debug possibility?

I would be glad if you you check my issue and hopefully show me a solution.

Best

Veeroohre

Discussion

  • Paul

    Paul - 2016-02-12

    Proxy behaviour was improved in 2.29. What version are you running?

    cheers, Paul

     
  • veeroohre

    veeroohre - 2016-02-12

    Oh, sorry I forgot to mention this. V2.31 on Windows 7

     
  • Paul

    Paul - 2016-02-12

    You can set the proxy via Tools > Options > Advanced > Proxy.

    cheers, Paul

     
  • veeroohre

    veeroohre - 2016-02-12

    I know. I did that with "localhost:8080" and tried all 3 authentication possibilities. Did not work.

     
  • Paul

    Paul - 2016-02-13

    Have you tried the IOProtocolExt plug-in?

    cheers, Paul

     
  • veeroohre

    veeroohre - 2016-02-15

    I use MagentaCloud which is a cloud service from Deutsche Telekom. They are only supporting webdav access which needs https. Your mentioned plug-in extense the available protocols by "scp://, sftp://, ftps://". Furthermore the readme of IOProtocolExt stats "As soon as the plugin is installed once, KeePass can open URLs starting with scp://, sftp://, ftps:// (and of course the ones that were supported already, i.e. http://, https:// and ftp://)." So this should mean KeePass supports connections through a http proxy. Did I get something wrong?

     
  • Paul

    Paul - 2016-02-15

    The plug-in replaced the network IO so it may work where the default .NET calls don't.
    Try it and let us know.

    cheers, Paul

     
  • Dominik Reichl

    Dominik Reichl - 2016-02-27
    • status: open --> closed
    • private: Yes --> No
     
  • Dominik Reichl

    Dominik Reichl - 2016-02-27

    I'm not sure, but I doubt the proxy is the problem here. A web search for your error message rather indicates an incompatibility of the .NET HTTPS/WebDAV implementation and your server.

    Please try the following development snapshot:
    http://keepass.info/filepool/KeePass_160227c.zip

    If it doesn't work, please go to the 'Advanced' tab in the 'Open From URL' dialog, set 'Expect 100-Continue responses' to 'No' and specify a large timeout. Does it work then?

    If it still doesn't work, I'm out of suggestions, sorry. If you can get server logs, these might indicate why the server is closing the connection.

    Best regards,
    Dominik

     
  • veeroohre

    veeroohre - 2016-02-29

    Hi Dominik

    I tried what you suggested but unfortunately it did not work.
    No matter how high I set the timeout I get the error message immediately. Thus I think the communication between KeePass and Putty does not work at all. When I check the log of Putty I do not see a single entry form KeePass. From Firefox I get a lot of traffic. My conclusion is that KeePass cannot connect to Putty's local port (localhost:8080). But I do not see a reason why.

    Edit: I checked again with another program (FileZilla) whether my local putty proxy is working or not. But it is. I could connect with an unsecured ftp connection without a problem.

    Best regards

    Veeroohre

     

    Last edit: veeroohre 2016-02-29
  • veeroohre

    veeroohre - 2016-04-19

    I tried it again with the "--debug" option I found in another thread. See the attachement for the error message I got. Does this help you? I'm still searching for a solution for this problem.

    The update check does not work either. What kind of protocol is used for this check?

     

Log in to post a comment.