Best Practices for Port Management in Retail Pro Prism

Retail Pro Prism installation components require access to various ports. If these ports are blocked by firewall or used by another program or process, the RP Prism components will not operate properly.

Required Open Ports

Make sure the following ports are open on any firewalls in use on machines or devices running RP Prism and/or RIL Oracle and RIL Prism Management.


Open Port Requirement


80 and 443



Prism License Server


RIL License Service



50025 (v1.14.7 and earlier)

  • In Prism 1.14.7 and earlier, there is a dedicated Centrals service that uses port 50025 and requires it be open.  The Centrals server should be at the root installation, not at the store, so in Prism 1.14.7, port 50025 should be open at the ROOT level. There is no need to keep port 50025 open on the Prism 1.14.7 store network. 
  • In Prism 2.x, the dedicated Centrals service is removed and instead Centrals is handled by the POSv1 and Common services. Prism 2.x doesn't require a specific port to be open EXCEPT port 80 on the store web server. If port 80 on the store web server is not open or is being used by something else, Prism and the Centrals Server will be unable to establish connectivity through a REST connection.

Prism Proxy

443 (outgoing connection to Apache) and 8080-8089 (configurable, depends on number of Proxies) 


5671, 5672

RabbitMQ (erl.exe)

4369,5671-5672,25672, 35672-35682,53793, 61613, 61614

RabbitMQ Console




Prism DSC

9090, 9091




If Another Process is Using a Port

If you receive an error that the machine is unable to start the Apache server, it is a good idea to check if Port 80 is in use by something other than Apache.­­­

Retail Pro Prism uses the Apache web server running on port 80 to "serve up" RP Prism web pages. Occasionally, other software installed on the same computer can use port 80, in effect preventing the Apache web service from starting.

To check if port 80 is in use and what process is using it, go to the command prompt and run the following command: Netstat -n -a -o

This command will display a list of ports being used and the Process ID (PID) numbers associated with the processes using the ports.

We can then determine which PID is using a particular port by visiting the "Processes" tab in the Windows Task Manager. 

Some common chat programs such as Skype may use ports 80 or 443 and prevent Apache from starting. 

If Microsoft IIS (Internet Information Server) was installed, it may show up as Process ID 4 which is the system process. If this is present, go into Services and disable the World Wide Web service which runs IIS.

Published on Mar 9, 2020 in Best Practices


Find Another Article