Initializing help system before first use

# Configuring an Xpress Insight Server - Desktop Edition Only

You need to configure an Xpress Insight server before you can publish to or otherwise interact with it.

The first time you try to publish to Xpress Insight, you will encounter a dialog box prompting you to provide configuration information.

In the dialog, review the list in the left-hand pane and select the appropriate server. If your planned server is not in the list, click Add and follow the prompts to add a new server. ifComplete the other fields and click Save to save your settings.

By default for Xpress Insight 4, if a locally-installed instance of Xpress Insight is active at the URL http://localhost:8860. You will need to enter your credentials in the form fields. Trial version user credentials are `admin/admin123` - contact your system administrator for details of other login options.

For Xpress Insight 5, the default URL is http://localhost:8080. After adding and selecting an Xpress Insight 5 URL, if Workbench detects that this Insight server is using a later version, the username and dialog boxes are removed and the credentials are picked from the OS credential store. See Providing the REST API Credentials.

## Troubleshooting Xpress Insight HTTPS Connections

If the Xpress Insight server is configured to use TLS connections ( `https:` rather than `http:`), some circumstances might cause a certificate error when you try to publish or otherwise connect from Xpress Workbench to Xpress Insight (see Publishing to Xpress Insight). This results in the error message `unable to verify the first certificate`. If this happens, try the following steps:

1. Make sure the security certificate, and any intermediate certificates for the Xpress Insight server, are present in the OS certificate store on the machine where Xpress Workbench is installed.
2. If that does not resolve the error, extract those certificates from the Xpress Insight server into a single .pem file (in ASCII text rather than binary format) and copy that to the file system of the machine where Xpress Workbench is installed. Then set the environment `NODE_EXTRA_CA_CERTS` to the full path to the .pem file. This will enable Xpress Workbench to find the certificates at run time.
3. If you still see the same error, or a "self-signed certificate" error, you can use a Workbench-specific override. Set the environment variable `WORKBENCH_EXTRA_CA_CERT_FILES`. For the value, specify a list of full paths to files, each one containing one certificate in ASCII format. These must be fully resolved paths and separated using the correct delimiter for your operating system (semicolon for Windows and colon for other OSs).
   Note: If you are deploying Workbench in its own Docker container, add the certificate files to the `workbench-config` volume. The environment variable must be set in the .env file, with the paths specified as /workbench-config/certificate_filename. Separate the paths using colons.

Parent Topic Working with Xpress Insight

© 2001-2026 Fair Isaac Corporation. All rights reserved. This documentation is the property of Fair Isaac Corporation (“FICO”). Receipt or possession of this documentation does not convey rights to disclose, reproduce, make derivative works, use, or allow others to use it except solely for internal evaluation purposes to determine whether to purchase a license to the software described in this documentation, or as otherwise set forth in a written software license agreement between you and FICO (or a FICO affiliate). Use of this documentation and the software described in it must conform strictly to the foregoing permitted uses, and no other use is permitted.