Client activation ports and SOLO Server IP address

All communication between our licensing clients implemented within your software use the same underlying technology as web browsers to communicate with SOLO Server Automation.  

The licensing clients will attempt initial communication over HTTPS and automatically fallback to communication over HTTP if there is a failure (unless your developers have configured it not to fallback to HTTP). While this setting is controllable by your development team during the implementation of the licensing client, we recommend that all customers use port 443 for encrypted communication with the central licensing server. 

DNS Name

When an IT department has to configure rules to allow connection to SOLO Server, sometimes they can use the DNS name rather than the IP Address.  It is recommended to use the DNS name if allowed as the IP Address can potentially change. 

• SOLO Server Shared URL: secure.softwarekey.com
• SOLO Server Custom URL: [your brand].softwarekey.com
• SOLO Server Dedicated URL or SOLO Server Self Hosted: [your SOLO Server domain name] (for example: secure.mysoloserver.com)

IP Address

If an IP Address is needed, the IP Address of SOLO Server is dependent on your SOLO Server Automation Package. You may ping your SOLO Server Host Name to retrieve the IP Address. Follow the steps below to ping SOLO Server.

IP Address for SOLO Sever Shared / Custom URL customers:

1. Click the Start button, type "cmd" (without the quotes) in the search bar, and press enter to open the Command Prompt.
2. Type the following command (for Shared URL or Custom URL):

• ping secure.softwarekey.com
• ping [your brand].softwarekey.com

IP Address for SOLO Sever Dedicated URL and SOLO Server Self-Hosted customers:

1. Click the Start button, type "cmd" (without the quotes) in the search bar, and press enter to open the Command Prompt.
2. Type the following command:
3. ping [your SOLO Server domain name] (for example: ping secure.mysoloserver.com)

Example IP Address

The IP Address of SOLO Server will be displayed in the command prompt window and will look similar to this output example:

Pinging secure.softwarekey.com [13.89.224.215] with 32 bytes of data:
Reply from 13.89.224.215: bytes=32 time=12ms TTL=242
Reply from 13.89.224.215: bytes=32 time=12ms TTL=242

In the above example output, the IP Address for secure.softwarekey.com is 13.89.224.215. 

Will the IP Address ever change?

It is always recommended to use the DNS name rather than the IP Address, but we recognize not everyone can use DNS for their proxy rules. If your customer must use an IP Address, use the above resources to identify the IP Address to provide your customer. We know it is important to try and avoid IP Address changes, but there may be certain circumstances that require it. In the unlikely event a circumstance requires us to fail-over to a geographically-distant disaster recovery site, this IP Address will likely change.  

We invite customers to visit our SoftwareKey System Status page, which has the ability to subscribe to receive updates on issues affecting the service.