9.5. Network Ports

Attention

Almost all network ports used in the LOCKSS stack changed in LOCKSS 2.0-beta2 compared to earlier "alpha" and "beta" versions of LOCKSS 2.0, which impacts firewall rules, browser bookmarks, scripts, and more. For example, the port for the Web user interface of the LOCKSS Configuration Service, often used when first logging in to LOCKSS in a browser, has moved from 24621 to 24602. See LOCKSS 2.0-beta2 Port Changes.

This section describes the default network ports used by the LOCKSS stack.

All ports are TCP in the 24600-24649 range [1] (with a few exceptions [2]), clustered in six categories by like purpose, correlated with like clients:

Port range	Category	Clients
9729 [2]	LCAP port	Other nodes participating in the same LOCKSS network via LCAP (LOCKSS polling and voting)
24600-24609	Web UI	Administrators of the running LOCKSS stack
24610-24619	API	Other software that integrates with LOCKSS via its APIs
24620-24629, also 9739 [2]	Internal	Internal to the LOCKSS stack (access not expected to be granted to other clients)
24630-24639	Content access	Clients who are granted access to the preserved content by way of proxies (including other Web proxies/caches)
24640-24649, also 8080 [2]	Web replay	Clients who are granted access to the preserved content by way of Web replay

Port by port details are shown below. Unspecified ports below in the 24600-24649 range should be considered reserved, although some ports are specifically called out as reserved for future use.

Port	Category	Description	Component
8080 [3]	Web replay	OpenWayback Web replay engine	OpenWayback
9729	LCAP port	LCAP (LOCKSS audit and repair) port	LOCKSS Poller Service
9739	Internal	reserved for internal use (temporary LCAP port [4])	LOCKSS Poller Service
24600	Web UI	reserved for future use (centralized UI)
24601	Web UI	reserved for future use (repository service UI)
24602	Web UI	LOCKSS Configuration Service Web user interface	LOCKSS Configuration Service
24603	Web UI	LOCKSS Poller Service Web user interface	LOCKSS Poller Service
24604	Web UI	LOCKSS Crawler Service Web user interface	LOCKSS Crawler Service
24605	Web UI	LOCKSS Metadata Service Web user interface	LOCKSS Metadata Service
24606	Web UI	reserved for future use (SOAP service UI)
24610	API	reserved for future use (centralized API)
24611	API	LOCKSS Repository Service REST API	LOCKSS Repository Service
24612	API	LOCKSS Configuration Service REST API	LOCKSS Configuration Service
24613	API	LOCKSS Poller Service REST API	LOCKSS Poller Service
24614	API	LOCKSS Crawler Service REST API	LOCKSS Crawler Service
24615	API	LOCKSS Metadata Service REST API	LOCKSS Metadata Service
24616	API	LOCKSS SOAP Compatibility Service SOAP API	LOCKSS SOAP Compatibility Service
24620	Internal	PostgreSQL database	PostgreSQL
24621	Internal	ActiveMQ JMS port	LOCKSS Configuration Service
24622	Internal	reserved for future use (Solr)
24623	Internal	reserved for future use (HDFS)
24629	Internal	reserved for internal use (JMX)
24630	Content access	Content proxy	LOCKSS Poller Service
24631	Content access	Audit proxy	LOCKSS Poller Service
24632	Content access	UDP ICP server	LOCKSS Poller Service
24633	Content access	reserved for internal use (content proxy SSL)	LOCKSS Poller Service
24634	Content access	reserved for internal use (audit proxy SSL)	LOCKSS Poller Service
24640	Web replay	ServeContent Web replay engine and OpenURL resolver	LOCKSS Poller Service
24641	Web replay	Pywb Web replay engine	Pywb
24642	Web replay	reserved for future use (OpenWayback)

9.5.1. LOCKSS 2.0-beta2 Port Changes

Almost all network ports used in the LOCKSS stack changed in LOCKSS 2.0-beta2 compared to earlier "alpha" and "beta" versions of LOCKSS 2.0, which impacts firewall rules, browser bookmarks, scripts, and more. The mapping from prior port to current port is shown below.

Pre-2.0-beta2 Port	2.0-beta2 Port	Category	Description
24602	24620	Internal	PostgreSQL
24603	n/a	Internal	Solr (no longer used)
24606	24621	Internal	ActiveMQ
24610	24611	API	LOCKSS Repository Service REST API
24620	24612	API	LOCKSS Configuration Service REST API
24621	24602	Web UI	LOCKSS Configuration Service Web UI
24630	24613	API	LOCKSS Poller Service REST API
24631	24603	Web UI	LOCKSS Poller Service Web UI
24640	n/a	API	LOCKSS Metadata Extraction Service REST API (merged into the LOCKSS Metadata Service)
24641	n/a	Web UI	LOCKSS Metadata Extraction Service Web UI (merged into the LOCKSS Metadata Service)
24650	24615	API	LOCKSS Metadata Service REST API
24651	24605	Web UI	LOCKSS Metadata Service Web UI
24660	24614	API	LOCKSS Crawler Service REST API
24661	24604	Web UI	LOCKSS Crawler Service Web UI
24670	24630	Content access	Content proxy
24672	24631	Content access	Audit proxy
24674	24632	Content access	UDP ICP server
24675	24616	API	LOCKSS SOAP Compatibility Service SOAP API
24680	24640	Web replay	ServeContent
24681	24641	Web replay	Pywb

---

Footnotes

[1]

In LOCKSS 2.0-beta1 and "alpha" versions of LOCKSS 2.0, this range was previously 24600-24699.

[2]

Exceptions include:

• The LCAP (LOCKSS audit and repair) port retains its historical value of 9729 [4].

• The OpenWayback port (if in use) is 8080 [3].

• The ICP port (if in use) is UDP (called out as UDP).

[3]

This port is not currently configurable.

[4]

During migration from LOCKSS 1.x to 2.x, a second, temporary LCAP port is in use, by default port 9739.