Infrastructure
Ports & links
Open ports mapped to processes with web links.
The story
These pages use illustrative scenarios to walk through real workbench panels. Sidebar labels, Bridge paths, and connection schemes match the app; characters and timelines are examples for learning.
Why is staging reachable on 5432 from the internet? Ports & links maps listeners to processes — click 443 when safe, jump to nginx.
Dev correlates open port with binary before firewall change ticket.
Bridge path: /server/ports
Step 1
Open ports and processes
Port 5432 mapped to postgres — incident explained. Port 3000 mystery mapped to node.
Web links when HTTP responds.
Open ports mapped to processes with web links. /server/ports.
Step 2
Safe click-through
443 opens app in browser — confirm correct vhost.
Skip on prod if policy forbids.
HTTP probe for web ports.
Step 3
Pair with Security audit
Unexpected listener feeds security audit finding.
Remediation copied to terminal.
Link to feature-ssh-security.
This panel appears in the Nexoxa Bridge left sidebar after you connect with the matching connection URL. See the connection docs above for
postgresql://, ssh://, sftp://, s3://, or smtp:// examples.Related connections