Browser Interface

The CirrusPrint server normally operates a private HTTP server, accessed by any web browser.  This interface is used to monitor the server and manage its configuration, and it also provides a link for browser users to launch the browser client.  The internal HTTP server is a private instance of the Apache or Nginx web server, launched with a special configuration file.  On dedicated CirrusPrint machines, this can be the only web server running, and it can listen on standard HTTP (80) and HTTPS (443) ports.  If it is not a dedicated machine, then it can listen on ports 8482 and 8483 for these two services.  An additional port, 8484, bound to the local computer and therefore inaccessible from external systems, is used for the internal SCGI proxy service.

Note that it is possible to disable this private web server instance, and replace it with an external web server that has been properly configured.  In that case, you would use a different domain name, port, and path prefix, to communicate with the server.

You can connect to the following locations using the server's hostname or IP address:

Optionally, if configured and accessible through your firewall, you can use http://server:8482 to access a non-secure version of these pages.  Also, the port portion can be dropped in dedicated machine installations, as the web server will listen on default ports 80 and 443.

Upon installation, there is a private certificate used for HTTPS connections, so most browsers will prompt the user for approval before proceeding to the pages.  A public certificate can be configured in the configuration page.

Troubleshooting

If you are unable to connect to the browser interface, it may be because there was an error starting the web server that listens on the CirrusPrint ports.  Look in the current logs/server.*.csv file for indications of an error starting Apache or Nginx.

To manually change ports used by CirrusPrint, you can edit the config.ini file found in the CirrusPrint install directory.  There are two or three ports required and which must not conflict with other services on the machine:

[server] section:

listen=port (used for the SCGI server that runs behind the Apache or Nginx server)

[httpd] section:

port=port  (used for http access)

sslport=port (used for https access)

Also be aware of the allow= and sslallow= settings to make sure your from address is not being blocked.