Research Academy
My account Customers About Blog Careers Legal Contact Resellers

Burp Suite User Forum

Create new post

Private Burp Collaborator Issues (Server HTTP connection Error + Verify Warning + Version Warning)

Adrian | Last updated: Jan 04, 2017 09:03PM UTC

I have set up a private burp collaborator server in AWS using all custom ports but I have redirected the standard ports to these using iptables so from an external perspective they are fine. However I am having several issues when running the health check: ---------- Initiating health check Server address resolution => Success Server HTTP connection => Error Server HTTPS connection (trust enforced) => Warning Server HTTPS connection (trust not enforced) => Warning Polling server address resolution => Success Polling server connection => Success Verify DNS interaction => Warning Verify HTTP interaction => Warning Verify HTTPS interaction => Warning Verify SMTP interaction => Warning Verify SMTPS interaction => Warning Server version => Warning An HTTPS connection to the capture server at [redacted] could not be opened. Communication using other protocols did work; possibly a firewall is preventing this connection. The HTTP response of the capture server was not as expected, perhaps this is not a collaborator server. We successfully connected to Burp Collaborator polling service. Since we were unable to connect to the capture interface of the server, we could not verify that interactions could be retrieved. The Collaborator server software is out of date. Some Burp features will not work completely with the configured Collaborator server. ---------- I'm currently using self-signed certs (that the collaborator server generates as per the documentation) so I'm not concerned with the HTTPS issues at the moment. However the fact that the HTTP response "was not expected" is strange, because if I visit the web server in my browser is displays a "Burp Collaborator Server" page which states various pieces of information. The metrics page is accessible also. The version out of date error is also strange, because I'm running the v1.7.15 of the JAR as both the Burp client and the collaborator server. Any help would be appreciated.

Burp User | Last updated: Jan 04, 2017 09:27PM UTC

Ok, I've figured this out! Apparently I had Burp configured to use an upstream proxy which wasn't performing the DNS lookups properly. Everything seems to be working now!

You must be an existing, logged-in customer to reply to a thread. Please email us for additional support.