What network ports does Foldr use?

Foldr’s appliance opens a number of TCP and UDP ports. Most are only needed in specific configurations (Kerberos SSO, multi-node clusters, search-tier appliances). The list below groups them by purpose so you can decide which ones your deployment actually needs to allow through your firewall.

Client access (inbound)

Port	Protocol	Purpose
443	TCP	HTTPS for the web app, mobile apps, and desktop drives. The main port to allow from your user network or the internet.
80	TCP	HTTP redirect to HTTPS. Also used briefly during Let’s Encrypt certificate validation and renewal.
25	TCP	SMTP, used by the Inbox feature to receive email attachments into shared folders. Only required if you use Inbox.

Directory and storage backends (outbound to your services)

Port	Protocol	Purpose
389	TCP	LDAP to your domain controllers (clear text).
636	TCP	LDAPS to your domain controllers (recommended).
88	TCP/UDP	Kerberos. Required only when Kerberos SSO is enabled.
464	TCP/UDP	Kerberos password change. Required only when Kerberos SSO is enabled.
445	TCP	SMB to your Windows or Samba file servers.
53	TCP/UDP	DNS to your name servers.

Foldr administration (inbound to fadmin only)

Port	Protocol	Purpose
2082	TCP	SSH on Foldr v9 and earlier.
20820	TCP	SSH on Foldr v10 and later.
30537	TCP/SSL	Foldr Settings (admin UI) on Foldr v9 and earlier. v10 serves Foldr Settings on 443.
5481	TCP/SSL	Custom update channel.

Cluster and search (between Foldr appliances)

These are only relevant if you run a multi-appliance cluster, a back-end + client-access split, or a dedicated search appliance. None should be open to client networks; restrict them to the appliances themselves.

Port	Protocol	Purpose
3306	TCP	MySQL replication between cluster nodes.
4444, 4567, 4568	TCP	Cluster state transfer and replication.
6379	TCP	Redis cache.
6380	TCP	Redis queue.
8983	TCP/SSL	Search service. Required inbound on a search appliance from the application appliances.
11211	TCP	Memcached.

Related articles

• Running Foldr on a custom HTTPS port: if 443 is taken by another service.
• Geo-location blocking: per-country firewall rules.
• SSL ciphers: modern vs legacy: which ciphers are accepted on 443.