Research Academy
My account Customers About Blog Careers Legal Contact Resellers

Burp Suite User Forum

Login to post

Error resolving polling server address in private Collaborator

Carl | Last updated: Mar 03, 2023 02:06PM UTC

Hi - I'm having an error resolving the polling server address, but not the server address. They are the same thing. This is the netstat output - tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN tcp 0 0 127.0.0.54:53 0.0.0.0:* LISTEN tcp6 0 0 147.182.222.108:25 :::* LISTEN tcp6 0 0 147.182.222.108:80 :::* LISTEN tcp6 0 0 147.182.222.108:587 :::* LISTEN tcp6 0 0 147.182.222.108:9443 :::* LISTEN tcp6 0 0 147.182.222.108:9090 :::* LISTEN tcp6 0 0 147.182.222.108:443 :::* LISTEN tcp6 0 0 147.182.222.108:465 :::* LISTEN tcp6 0 0 :::22 :::* LISTEN udp 0 0 127.0.0.54:53 0.0.0.0:* udp 0 0 127.0.0.53:53 0.0.0.0:* udp6 0 0 147.182.222.108:53 :::* The server name is bitbucket.me. I'm using bitbucket.me:9090 for the polling server address with "Poll over unencrypted HTTP" checked (I've tried 9443 with that unchecked, too). Thanks!

Carl | Last updated: Mar 03, 2023 02:07PM UTC

My config is - { "serverDomain" : "bitbucket.me", "workerThreads" : 10, "eventCapture": { "localAddress" : ["147.182.222.108"], "publicAddress" : "147.182.222.108", "http": { "ports" : 80 }, "https": { "ports" : 443 }, "smtp": { "ports" : [25, 587] }, "smtps": { "ports" : 465 }, "ssl": { "certificateFiles" : [ "/etc/letsencrypt/live/bitbucket.me/fullchain.pem", "/etc/letsencrypt/live/bitbucket.me/privkey.pem" ] } }, "polling" : { "localAddress" : "147.182.222.108", "publicAddress" : "147.182.222.108", "http": { "port" : 9090 }, "https": { "port" : 9443 }, "ssl": { "certificateFiles" : [ "/etc/letsencrypt/live/bitbucket.me/fullchain.pem", "/etc/letsencrypt/live/bitbucket.me/privkey.pem" ] } }, "metrics": { "path" : "chs", { "serverDomain" : "bitbucket.me", "workerThreads" : 10, "eventCapture": { "localAddress" : ["147.182.222.108"], "publicAddress" : "147.182.222.108", "http": { "ports" : 80 }, "https": { "ports" : 443 }, "smtp": { "ports" : [25, 587] }, "smtps": { "ports" : 465 }, "ssl": { "certificateFiles" : [ "/etc/letsencrypt/live/bitbucket.me/fullchain.pem", "/etc/letsencrypt/live/bitbucket.me/privkey.pem" ] } }, "polling" : { "localAddress" : "147.182.222.108", "publicAddress" : "147.182.222.108", "http": { "port" : 9090 }, "https": { "port" : 9443 }, "ssl": { "certificateFiles" : [ "/etc/letsencrypt/live/bitbucket.me/fullchain.pem", "/etc/letsencrypt/live/bitbucket.me/privkey.pem" ] } }, "metrics": { "path" : "chs", "addressWhitelist" : ["0.0.0.0/1"] }, "dns": { "interfaces" : [{ "name": "ns1.bitbucket.me", "localAddress" : "147.182.222.108", "publicAddress" : "147.182.222.108" }], "ports" : 53 }, "logLevel" : "INFO" }

Michelle, PortSwigger Agent | Last updated: Mar 03, 2023 03:27PM UTC

Hi Thanks for getting in touch. Can we check a few details about your setup, please? In Burp, under Settings -> Collaborator -> Polling location, have you specified the custom port, e.g. yourcollaborator.net:9443 or yourcollaborator.net:9090? Is the firewall protecting your Collaborator server blocking access on ports 9090 and 9443? If there are any details you'd prefer to share directly rather than via the public forum, feel free to email support@portswigger.net

You need to Log in to post a reply. Or register here, for free.