The Burp Suite User Forum was discontinued on the 1st November 2024.

Burp Suite User Forum

For support requests, go to the Support Center. To discuss with other Burp users, head to our Discord page.

SUPPORT CENTER DISCORD

No connections to the polling server at polling.[domain] could be opened. The collaborator will not work in this configuration.

Peter | Last updated: Jun 22, 2022 09:00AM UTC

I am struggling to get my private Burp collaborator working correctly, running a health check gives: An HTTP connection to the capture server at 6qxgdpy57h21gh1p4si6u6jil9rm55pntqi.[DOMAIN] could not be opened. An HTTPS connection to the capture server at 6qxgdpy57h21gh1p4si6u6jil9rm55pntqi.[DOMAIN] could not be opened. An SMTP connection to the capture server at 6qxgdpy57h21gh1p4si6u6jil9rm55pntqi.[DOMAIN] port 25 could not be opened. An SMTP connection to the capture server at 6qxgdpy57h21gh1p4si6u6jil9rm55pntqi.[DOMAIN] port 587 could not be opened. Communication using other protocols did work; possibly a firewall is preventing this connection. No connections to the polling server at polling.[DOMAIN] could be opened. The collaborator will not work in this configuration. Running the recommended checks show that it is resolving okay: $ dig [DOMAIN] NS +noall +answer +short ns1.[DOMAIN] ns1\.[DOMAIN]\.[TLD].[DOMAIN]. [CORRECT IP] $ dig ns1.[DOMAIN] A +noall +answer +short [CORRECT IP] [CORRECT IP] [CORRECT IP] $ dig randomsubdomain.[DOMAIN] A +noall +answer +short ns1.[DOMAIN] [CORRECT IP] [CORRECT IP] [CORRECT IP] [CORRECT IP] My config file is as follows: { "serverDomain": "[DOMAIN]", "workerThreads": 10, "eventCapture": { "localAddress": "[CORRECT PRIVATE IP]", "publicAddress": "[CORRECT PUBLIC IP]", "http": { "ports": 80 }, "https": { "ports": 443 }, "smtp": { "ports": [ 25, 587 ] }, "smtps": { "ports": 465 }, "ssl": { "certificateFiles": [ "/etc/letsencrypt/live/[DOMAIN]/privkey.pem", "/etc/letsencrypt/live/[DOMAIN]/cert.pem", "/etc/letsencrypt/live/[DOMAIN]/fullchain.pem" ] } }, "polling" : { "localAddress" : "[CORRECT PRIVATE IP]", "publicAddress" : "[CORRECT PUBLIC IP]", "http": { "port" : 9090 }, "https": { "port" : 9443 }, "ssl": { "certificateFiles" : [ "/etc/letsencrypt/live/[DOMAIN]/privkey.pem", "/etc/letsencrypt/live/[DOMAIN]/cert.pem", "/etc/letsencrypt/live/[DOMAIN]/fullchain.pem" ] } }, "metrics": { "path": "{[REDACTED]}", "addressWhitelist": [ "127.0.0.1" ] }, "dns": { "interfaces": [ { "name": "ns1.[DOMAIN]", "localAddress": "[CORRECT PRIVATE IP]", "publicAddress": "[CORRECT PUBLIC IP]" }], "ports": 53 }, "customDnsRecords": [ { "label": "_acme-challenge", "record": "holder", "type": "TXT", "ttl": 60 }], "logLevel": "INFO" } When changing LogLevel to DEBUG I am getting results appear in SYSLOG for all subdomains. JAVA version: openjdk 17.0.3 2022-04-19 OpenJDK Runtime Environment (build 17.0.3+7-Ubuntu-0ubuntu0.22.04.1) OpenJDK 64-Bit Server VM (build 17.0.3+7-Ubuntu-0ubuntu0.22.04.1, mixed mode, sharing) Burp Pro version: 2022.5.1 Hopefully someone can Debug this issue for me? - I have emailed this content unredacted to the support email address.

Peter | Last updated: Jun 22, 2022 09:02AM UTC

All the required ports are also open on the firewall (host and network firewall).

Liam, PortSwigger Agent | Last updated: Jun 22, 2022 12:47PM UTC