Name is required.
Email address is required.
Invalid email address
Answer is required.
Exceeding max length of 5KB

Polling server connection fails on private collaborator instance

floyd Jun 04, 2019 08:07AM UTC

Hi there,

I have setup a private collaborator server with let's encrypt wildcard certificates. It works fine, except that I can only pull over unencrypted HTTP. This is very strange, as I do not have a "polling" section in the configuration file. This means that Burp Collaborator server will use the same wildcard certificate for interactions and polling. I get the following when I try to poll over an encrypted connection:

Initiating health check
Server address resolution Success
Server HTTP connection Success
Server HTTPS connection (trust enforced) Success
Server HTTPS connection (trust not enforced) Success
Server SMTP connection on port 25 Success
Server SMTP connection on port 587 Success
Server SMTPS connection (trust enforced) Success
Server SMTPS connection (trust not enforced) Success
Polling server address resolution Success
Polling server connection Error

And all checks successful if I poll over unencrypted HTTP.

From my point of view this does not make sense. Isn't it the same HTTPS endpoint used for the "Server HTTPS connection (trust not enforced)" and "Polling server connection" checks when I don't have a polling section in my configuration?

cheers,
floyd


floyd Jun 04, 2019 08:08AM UTC
James says he can replicate it :)

Liam Tai-Hogan Jun 04, 2019 10:12AM UTC Support Center agent

Thanks for this report Floyd. Could you scale back to 2.0.13 and let us know if the issue persists?


floyd Jun 04, 2019 11:26AM UTC
Yes, running 2.0.13 works fine and there are no connection errors.

Liam Tai-Hogan Jun 05, 2019 12:49PM UTC Support Center agent

Thanks Floyd. We’ve added this to our development backlog to investigate further.


Post Your public answer

Your name
Your email address
Answer