Polling server connection fails on private collaborator instance
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?
Thanks for this report Floyd. Could you scale back to 2.0.13 and let us know if the issue persists?
Thanks Floyd. We’ve added this to our development backlog to investigate further.