Port 1775 VDAB
Port 1775 is the IANA-assigned vdab port for data interchange between visual processing containers (TCP).
What is port 1775 used for?
Port 1775 is assigned to vdab and uses TCP. The IANA registry describes the service as “data interchange between visual processing containers”. It sits in the registered range, the block used by databases, application servers and developer tooling. Port conflicts here are common when several local services start at once.
Ports are the transport-layer address a service listens on. A client that wants to reach vdab connects to port 1775. If nothing is listening, the connection is refused. That is why a port conflict appears whenever two processes try to bind the same number.
Use the commands below to confirm whether port 1775 is actually in use before you change firewall rules. Blocking the port stops new inbound traffic at the firewall, but it does not stop a local process from listening, and it does not remove the service from the machine.
Browse all Containers and orchestration ports
Source: IANA Service Name and Transport Protocol Port Number Registry. Registered assignee: [MJA_Technology_LLC].
Check and block port 1775
Copy-ready commands for the protocols assigned to this port. Run the check first, then block only what should not be reachable.
Check on Linux
sudo ss -tlpn 'sport = :1775'Check on Windows
Get-NetTCPConnection -LocalPort 1775 -State Listen -ErrorAction SilentlyContinueBlock with UFW
sudo ufw deny 1775/tcpBlock with iptables
sudo iptables -A INPUT -p tcp --dport 1775 -j DROPThese commands are examples for a typical host. Check the listener before you change firewall rules, and persist iptables rules with iptables-save or netfilter-persistent. On Windows, use Windows Defender Firewall or New-NetFirewallRule for persistent blocks. The iptables rules here cover IPv4; mirror them with ip6tables if IPv6 is enabled.
Is port 1775 safe to expose?
This port is not on our curated list of services with a widely exploited profile. Exposure is only safe when the listening service is intended, patched and protected by a firewall. Keep the listening service patched and remove it if unused. A default-deny firewall policy with explicit allow rules is still the safest baseline.
Where port 1775 is usually used
Most traffic on port 1775 falls into these scenarios. The demo below is a safe way to confirm the listener before you change anything.
- Cluster control-plane traffic and automation clients managing workloads.
- Operators inspecting nodes, pods and secrets from a trusted network.
- CI pipelines deploying manifests against a cluster endpoint.
Check the cluster endpoint
Use the vendor CLI with the kubeconfig that already knows the endpoint; a raw probe only proves the socket is open.
kubectl cluster-info
Common problems with port 1775
Connection refused or timed out
Refused usually means the host is reachable but nothing is listening on port 1775. A timeout more often means a firewall drop, a wrong host or a service bound to a different interface.
Port already in use
Find the process holding the port with sudo ss -tlpn 'sport = :1775' or sudo lsof -i :1775. Stop that process or configure it to bind another port; killing it without identifying it can take down a production service.
Firewall rule did not survive a reboot
UFW and Windows Firewall keep rules across restarts. Raw iptables rules do not: save them with iptables-save or the netfilter-persistent package, and re-apply after upgrades that reset the ruleset.
The port is blocked but still reachable
A firewall rule filters inbound traffic; it does not close the listener. Confirm with the check command above and bind the service to 127.0.0.1 when only local clients need it.
Port 1775 at a glance
| Port number | 1775 |
|---|---|
| Service name | vdab |
| Transport protocol | TCP |
| Category | Containers and orchestration |
| Range | Registered port (1024–10000) |
| Risk level | Standard/Low |
| Registered assignee | [MJA_Technology_LLC] |
| Registry description | data interchange between visual processing containers |
| Source | IANA Service Name and Transport Protocol Port Number Registry |
Frequently asked questions
What is port 1775 used for?
Port 1775 (VDAB) uses TCP. data interchange between visual processing containers.
How do I check if port 1775 is open?
On Linux run `sudo ss -tlpn 'sport = :1775'`. On Windows run `Get-NetTCPConnection -LocalPort 1775 -State Listen -ErrorAction SilentlyContinue` in PowerShell. If the port is open, the output shows a process listening on port 1775; empty output usually means nothing is bound to it.
How do I block port 1775?
With UFW run `sudo ufw deny 1775/tcp`. With iptables run `sudo iptables -A INPUT -p tcp --dport 1775 -j DROP`. Persist the iptables rules with your distribution's netfilter-persistent or iptables-save tooling so they survive a reboot.
Is port 1775 safe to expose?
This port is not on our curated list of services with a widely exploited profile. Exposure is only safe when the listening service is intended, patched and protected by a firewall. Nevertheless, keep the listening service patched and remove it if unused. A default-deny firewall policy with explicit allow rules is still the safest baseline.
Related ports
- Port 1752 · lofr-lmLeap of Faith Research License Manager
- Port 1776 · femisFederal Emergency Management Information System
- Port 2375 · dockerDocker REST API (plain text)
- Port 2376 · docker-sDocker REST API (ssl)
- Port 2377 · swarmRPC interface for Docker Swarm
- Port 2379 · etcd-clientetcd client communication
Primary data: IANA Service Name and Transport Protocol Port Number Registry.
Last reviewed 2026-10-30 · Methodology · About · Privacy