Research Academy
My account Customers About Blog Careers Legal Contact Resellers

Burp Suite User Forum

Create new post

Connectivity issues with Burp Collaborator

S | Last updated: Jul 16, 2021 01:18PM UTC

Hi there, I'm trying to set up a private Burp Collaborator. I can connect to it, e.g. by curling it, using its external IP address from the server it is running on, but not from anywhere else. This is on Digital Ocean, no firewall at present, no ufw or iptables issues afaict. Running as root for now. The server can be connected to via ping and ssh, but the Collaborator only returns its html to `curl 1.2.3.4` when run from the local server, not from anywhere else. Here is a copy of my configuration. I have changed the IP address and hostname, but the real ones have been double checked and are correct. Can anyone see where I'm going wrong? Thanks very much for your help. { "serverDomain" : "collab.example.com", "workerThreads" : 10, "eventCapture": { "publicAddress" : [ "5.6.7.8" ], "localAddress" : "1.2.3.4", "http": { "ports" : 80 }, "https": { "ports" : 443 }, "smtp": { "ports" : [25, 587] }, "smtps": { "ports" : 465 }, "ssl": { "certificateFiles" : [ "/usr/local/collaborator/keys/privkey.pem", "/usr/local/collaborator/keys/cert.pem", "/usr/local/collaborator/keys/fullchain.pem" ] } }, "polling" : { "publicAddress" : "5.6.7.8", "localAddress" : "1.2.3.4", "http": { "port" : 9090 }, "https": { "port" : 9443 }, "ssl": { "certificateFiles" : [ "/usr/local/collaborator/keys/privkey.pem", "/usr/local/collaborator/keys/cert.pem", "/usr/local/collaborator/keys/fullchain.pem" ] } }, "metrics": { "path" : "jnaicmez8", "addressWhitelist" : ["0.0.0.0/1"] }, "dns": { "interfaces" : [{ "name":"ns1.collab.example.com", "publicAddress":"5.6.7.8", "localAddress":"1.2.3.4" }], "ports" : 53 }, "logLevel" : "INFO" } root@burp-collaborator-server:/usr/local/collaborator# java -Xms10m -Xmx200m -XX:GCTimeRatio=19 -jar /usr/local/collaborator/burpsuite_pro.jar --collaborator-server --collaborator-config=/usr/local/collaborator/collaborator.config 2021-07-16 13:14:53.767 : Using configuration file /usr/local/collaborator/collaborator.config 2021-07-16 13:14:54.097 : Listening for SMTP on 1.2.3.4:587 2021-07-16 13:14:54.097 : Listening for HTTP on 1.2.3.4:80 2021-07-16 13:14:54.099 : Listening for SMTP on 1.2.3.4:25 2021-07-16 13:14:54.099 : Listening for HTTP on 1.2.3.4:9090 2021-07-16 13:14:54.117 : Listening for DNS on 1.2.3.4:53 2021-07-16 13:14:54.465 : Listening for HTTPS on 1.2.3.4:9443 2021-07-16 13:14:54.467 : Listening for SMTPS on 1.2.3.4:465 2021-07-16 13:14:54.468 : Listening for HTTPS on 1.2.3.4:443

Michelle, PortSwigger Agent | Last updated: Jul 19, 2021 08:52AM UTC

Thanks for your message. When you ping/ssh to the server are you connecting via the 5.6.7.8 address? Is that then being NATted to the 1.2.3.4 address? Is the same NAT being applied to the HTTP connection? You can email us directly using support@portswigger.net if that makes it easier to share information on your setup.

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