[Bug]: Subnet Scan Returns 504

[S-Bryce]

What happened?

When I try to scan a subnet, after waiting awhile, it finishes the scan and returns a 504 error (which shows up in the inspector page for some reason)

What did you expect?

I expected it to scan the subnet using ICMP and then return all of the hosts it found. Interestingly, this works fine for two other non-local subnets, so I'm not sure why it fails for this one.

Steps to reproduce

1. Go to Discovery
2. Select a non-local subnet in the top right
3. Press Scan Subnet
4. Wait for the error message to appear in Inspector

Rackpad version

v1.7.0-beta.4

Browser / client (if UI bug)

Not applicable (server/API)

Logs or screenshots

I've tried looking at the network/console debugs, but they're not any more descriptive, and nothing appears in the docker logs related to the return code (or any other error/warning)

From what I can see, the traffic is being allowed in the firewall

Checklist

• I searched existing issues for duplicates
• I can reproduce this on the latest beta/dev branch

[Kobii-git]

Thanks for the detailed report. I found the subnet scan was running inside one long HTTP request, so slower routed subnets could outlive the reverse proxy and show up as a 504 even though Rackpad itself did not log much.

I’ve changed manual Discovery scans and “run now” scheduled scans to use an async scan job with polling instead of holding the request open. Please test the same non-local subnet on the next beta; it should no longer 504, and the Discovery inbox should update when the scan finishes. v1.7.0-beta.4