When trying to connect Studio to a Definition Center, you encounter an error message: "The iRise Definition Center is not running on the host/port you specified. Please contact your administrator."
There are a few reasons that you might get this error while trying to login to the Definition Center from iRise Studio.
The most common reason is that you may have specified the Definition Center connection information incorrectly. Make sure that the values for the Definition Center, port and any other connection details are correct. The article How to connect iRise Studio to Definition Center describes the correct format.
Cloud SaaS Definition Center
If you get this error connecting to an iRise Cloud instance (i.e. the server name is [name].dc.irise.com) and you've checked the details are correct after following the article on connecting Studio, then check the below.
Check the certificate chain your browser is using when viewing your Definition Center. Login to the Definition Center via a browser and click on the lock (1).
We use a trusted 3rd party Certificate Authority (Symantec/Verisign) to sign TLS certificates. Studio will trust this CA by default. If you notice the certificate's root certificate is from an internal CA instead of our 3rd party CA, it's likely you're connecting to the internet via a proxy, and the proxy is inserting certificate(s) into the chain to inspect traffic. When this occurs, Studio does not trust the certificate signing authority and blocks the connection. This likely works in the browser, because your IT team has imported the root certificate into your computer/browser's trusted certificate store. However, Studio uses its own CA store, which does not trust your certificate. This is usually accompanied by the following error in your Studio log (access logs from the Help menu):
Caused by: javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
We can resolve this one of two ways:
- Your IT team can allow a direct connection to your cloud Definition Center (a proxy bypass).
- We can import your root certificate into Studio's trusted CA store. This method is a bit fragile, as this trusted certificate store is wiped out on every Studio install/upgrade. Instructions for this are contained within the last step of this article.
Please run this by your IT/security team. If that doesn't address your issue, please contact Support.
On Premise Definition Center
The following troubleshooting tips relates to an On Premise Definition Center (i.e. hosted by your company).
- Verify your Definition Center details with your iRise administrator, or contact Support and we can help you identify the correct settings.
- Check if your organization is using a proxy server (or PAC script). You can check this in your browser:
Chrome: Chrome menu > Settings > Show advanced settings > Network > Change proxy settings
Internet Explorer: Tools > Internet Options > Connections > LAN Settings
Firefox: Tools > Options > Advanced > Network > Settings
If you're using a proxy, there should be a proxy address and port. Add your proxy details. If you're using a PAC script, then consult with your IT/security team to determine the proxy details, or contact us and we can help you identify them.
- You may encounter this message if your organization is using TLS (https) and they are using a certificate from a non-trusted or internal certificate authority and the root and intermediate certificates haven't been imported on the Studio client, as per the section Non-trusted Certificate Authority - additional steps in the article TLS Setup for iRise Definition Center. You'll need to check with your iRise administrator or contact us for assistance.
- Check if the Definition Center service has been started - try logging on to the Definition Center via a browser. If you're unable to connect, contact your iRise administrator to have them start the Definition Center or let you know the reasons why the service is not running.
Hint: if you also use a browser to connect to the Definition Center, many of these details will be contained in the URL you use to access the Definition Center. For example, if you use TLS to connect to the Definition Center, the URL will start with https:// instead of http://. After that is the name (or IP address) of the Definition Center followed by either a colon or another forward slash. If you access the Definition Center on a port other than 80 (http) or 443 (https), that port number will follow the colon.
Cisco AnyConnect VPN Client
The Java that Studio uses introduced IPV6 support and uses IPV6 mapped IPV4 addresses. Current versions of the Cisco AnyConnect VPN client do not allow IPV6 traffic. If you are connected to your VPN using one of these versions of the Cisco AnyConnect VPN client and you encounter the error, this is usually accompanied by the following error in your Studio log (access logs from the Help menu):
Caused by: java.net.SocketException: Permission denied: connect
You'll need to add an additional parameter to the startup options for Studio. Here are instructions for making those modifications for both Windows and Mac Studio clients:
Close Studio if you have it open and edit the file in a text editor:
C:\Program Files (x86)\iRise\Studio\iRiseStudio.lax file
Search for the following text in the file. If you are using an editor that numbers lines it should be around line 68:
at the far end of that line add the following text:
Save the file, restart Studio and attempt to connect to your Definition Center. If you are still having troubles, contact us and include your studio log file.
On the Mac you will need to edit the
info.plist file for the program to add the same option to the startup parameters for the application. Make sure iRise Studio is closed. Open Finder and navigate to Applications. Find iRise Studio in the list and alternate click to get menu options. Select 'Show Package Contents'. Click the Contents folder, then double click the info.plist file in the right pane.
Search for 'JVMOptions' in the file and you will see a section that follows it with a number of <string> entries. Add one to the bottom of that with the following value:
When you are done editing the file that section should look like this:
Save the file and start Studio.