Table of Contents
This chapter contains advanced configuration related to PaperCut's internal web server (powered by Apache Jetty). The configuration options mentioned here should generally only be used as a reference for specific requirements, as some changes could negatively impact on system functionality.
PaperCut will listen on all available network interfaces by default. If your server has multiple IP addresses (i.e. is multi-homed), PaperCut will accept connections to all these addresses. Alternatively, it may be configured to listen on a single, defined interface. To configure PaperCut to listen on a single network interface:
Open [app-path]/server/server.properties in a text editor.
Add a new line:
server.listen-interface=1.2.3.4
where 1.2.3.4 is the (static) IP address of the network interface for PaperCut to
listen on.
Restart the service PaperCut Application Server
PaperCut can publish an IP address to some external components (e.g. MFD devices) to allow them to establish a connection to the PaperCut server. If your system has multiple IP addresses (i.e. is multi-homed) then PaperCut will chose one of these. In some cases this IP might be incorrect (e.g. an IP on an inaccessible/private subnet) and then these other components will fail to connect.
To resolve this you can configure the network address (e.g. IP or DNS name) that PaperCut publishes
to these external components. To do this use the Config Editor (see the section called “Using the Config Editor”)
to change the system.network-address to your chosen address.
© Copyright 1999-2013. PaperCut Software International Pty Ltd. All rights reserved.