Q100459: Ports used by the Nuke Frame Server
This article explains which network ports are used by the Frame Server to connect between the host/master machine and the worker/slave processes.
The Frame Server allows Nuke to reduce render times by using multiple Nuke processes to distribute the work, either on the local machine, or on other machines on the network.
The Frame Server works by using network protocols to access other worker Nuke processes, which have the ports open and report to the main Nuke process as slaves, and tells those processes to render particular frames. The network protocols are used for both the local Nuke processes and the network based ones on other machines, so Nuke can be indiscriminate about how it uses the processes.
Nuke has a list of network ports it uses to connect to the worker processes, these are listed below:
APPLICATION_URL = "tcp://localhost:5558"
SERVER_CLIENT_URL = "tcp://*:5559"
SERVER_WORKERS_URL = "tcp://*:5560"
WORKER_SERVER_URL = "tcp://localhost:5560"
RENDER_PROGRESS_PUBLISH_URL = "tcp://*:5561"
The worker processes than randomly chose a port between 5562-5662 to use to connect to the main Nuke process.
If there are issues when trying to use the Frame Server, such as the worker processes not being able to connect to the host, allowing ports 5558-5662 through any firewalls or security software on the host Nuke machine and any worker machines should allow the Frame Server to work correctly.
More information about the Frame Server can be found here: Rendering Using the Frame Server
Other articles about troubleshooting the Frame Server can be found below:
If you are still seeing any issues after performing the steps outlined in this article, please open a Support ticket and let us know the problem you are encountering and the troubleshooting steps you have taken so far.
For more information on how to open a Support ticket, please refer to our Q100064: How to raise a support ticket article.
We're sorry to hear that!Please tell us why.