I've noticed that portscanner is failing to identify ports on certain systems. This results in other scans such as Nuclei not being kicked off properly. We may need to tweak the scan rate on masscan as it seems like we are occasionally missing some stuff here. I think this tends to happen more with things like a lower resource VPS that is slower to respond to SYN packets than our timeout window within masscan.
We use MacOS locally, and portscanning does not work properly within docker on MacOS. That appears to be the root cause of this issue. I believe we can close this ticket.
I've noticed that portscanner is failing to identify ports on certain systems. This results in other scans such as Nuclei not being kicked off properly. We may need to tweak the scan rate on masscan as it seems like we are occasionally missing some stuff here. I think this tends to happen more with things like a lower resource VPS that is slower to respond to SYN packets than our timeout window within masscan.