KeePass 2.22 with KeePassHttp 1.8.0.0 on Windows 7 does not listen on any port

[utapyngo]

Needless to say that chromeIPass can't connect to it.

[lsgd]

OffTopic: Can you tell me the application which is showing you these information?

---

Can you call http://localhost:19455/ in your browser and check whether KeePassHttp is responding to this? After calling the URL open KeePass, there should be an error message: System.NullReferenceException

[utapyngo]

Oh, I am stupid. I did not add localhost to the proxy bypass list. Now the connection seems to be ok. I think that chromeIPass should know that it should not use proxy to connect to KeePassHttp.

But why don't I see KeePass listening on any ports anyway? What another process does? With the KeePassRPC plugin, it is KeePass that listens for connections on port 12536.

The application is Process Explorer.

And there is no System.NullReferenceException error message (which is good in my opinion).

[lsgd]

I updated KeePassHttp to v1.8.1.0 which fixed the NullReferenceException. But this seems not to affect your problem.

KeePass needs to listen on a port on localhost. May it needs access to the private network (I cannot remember if it asked for it first time). Did you deny network access for KeePass?

[utapyngo]

There is no problem anymore, I already told. But I am curious why Process Explorer does not show the port in the TCP/IP activity of KeePass.

[lsgd]

I didn't get it in your previous message ;-) I don't know why Process Explorer is not showing the port, but may it's because the plugin is listening on the port and not KeePass directly?

[utapyngo]

Is the plugin a separate process?

[Phloks]

I think KeePassHttp communicates through the system process.