Network and firewall requirements for software activation (for IT administrators)
This article is for IT and network administrators whose users run software that is licensed through SOLO Server, the licensing service operated by SoftwareKey. Your software vendor may have sent you here because the software cannot activate, or cannot check its license, from inside your network. Everything your firewall, proxy, or web filter needs to allow is listed below.
Quick reference: allow outbound HTTPS (TCP port 443) from the user's computer to secure.softwarekey.com (or the address your software vendor gave you), by host name rather than IP address, and exclude that host from SSL/TLS inspection. No inbound rules, no other ports, and no UDP are required. Some software vendors use their own licensing server address instead, such as a subdomain of softwarekey.com in their own name or a server on their own domain. If your software vendor gave you a different licensing server address, use their address everywhere this article says secure.softwarekey.com.
What does the software need to reach?
| Requirement | Value |
|---|---|
| Destination host | secure.softwarekey.com (or the address your software vendor gave you) |
| Protocol and port | HTTPS on TCP 443 |
| Direction | Outbound only, initiated by the user's computer |
| Inbound rules | None. The licensing server never connects to your network. |
| TLS versions | TLS 1.2 or TLS 1.3 (TLS 1.0 and 1.1 are refused by the server) |
| DNS | The computer must be able to resolve the host name through public DNS |
| Port 80 (HTTP) | Not required. Some applications retry over plain HTTP if HTTPS fails (see below). |
Allowing your software vendor's own website is not enough on its own. The licensing traffic goes to secure.softwarekey.com (or the licensing server address your software vendor gave you), not to the vendor's own domain, so that host needs its own allow rule.
Should we allow the host name or an IP address?
Use the host name (secure.softwarekey.com) in firewall, proxy, and web filter rules wherever your equipment supports it. The IP address behind the host name can change, for example during a failover to a disaster recovery site, and a rule pinned to an old IP address will silently start blocking activations.
If your equipment can only filter by IP address, resolve the current address with nslookup secure.softwarekey.com and plan to update the rule if activations start failing. Current service status, including any planned changes, is on the SoftwareKey System Status page, which you can subscribe to.
If your web filter works by URL rather than host, allow the whole host ( https://secure.softwarekey.com/*) rather than a single path. The software calls several different service addresses on that host.
When does the software contact the licensing server?
The software contacts SOLO Server when a user:
- Activates the software on a computer.
- Deactivates the software, for example to move a license to another computer.
- Checks the license status, which many applications do periodically while they run (at startup or on a schedule the software vendor sets).
Because of the periodic license check, the software needs ongoing access, not just access on the day it is first activated. If access is allowed only temporarily for activation and then removed, the software may later report that it cannot validate its license.
What about SSL/TLS inspection?
Exclude secure.softwarekey.com from SSL/TLS inspection (also called HTTPS inspection, SSL decryption, or deep packet inspection). This is the most common cause of activation failures on networks where a browser can reach the site without trouble.
An inspecting firewall or proxy replaces the server's certificate with one it signs itself. Browsers accept that because your organization installed the inspection root certificate in the browser's trust store, but licensed applications do not always use the same trust store as the browser. The application then rejects the connection as untrusted, and the user sees a general "cannot connect" or "activation failed" error rather than anything mentioning certificates.
Also avoid certificate pinning for this host. The SOLO Server certificate is issued by a public certificate authority and is renewed every few months, and the issuing certificate authority can change. A rule that pins today's certificate will break at the next renewal.
What if our network requires a web proxy?
If computers on your network can only reach the internet through an explicit web proxy, the licensed application has to be able to use that proxy, and support for this varies by application. The most reliable options, in order:
- Allow direct outbound HTTPS from user computers to secure.softwarekey.com, bypassing the proxy for this one host.
- If traffic must go through the proxy, do not require proxy authentication for secure.softwarekey.com. Many applications cannot answer a proxy login prompt (an HTTP 407 response), even when a browser on the same computer can.
- If neither is possible, ask your software vendor how their application is configured to use a proxy server, including proxy authentication.
A transparent (intercepting) proxy that does not decrypt HTTPS normally needs no special handling beyond allowing the host.
What about guest Wi-Fi, hotels, and captive portals?
Networks that show a sign-in or terms page before allowing internet access (hotels, airports, conference centers, guest networks) block the software until that page has been completed. Have the user open a web browser, complete the sign-in page, and then activate the software.
How do we test whether the network allows licensing?
In a web browser: close all browser windows, open a new one, and go to https://secure.softwarekey.com. If the computer can reach SOLO Server, the page shows only the text OK. If anything else appears (a block page, a certificate warning, a login prompt, or a timeout), the network is not allowing the connection.
A browser test passing does not prove the application will work, because the browser may use a proxy or trusted inspection certificate that the application does not. These commands test the path more directly. If your software vendor uses a different licensing server address, substitute it for secure.softwarekey.com in the browser test and in each command.
On Windows (PowerShell):
<code>nslookup secure.softwarekey.com Test-NetConnection secure.softwarekey.com -Port 443 Invoke-WebRequest https://secure.softwarekey.com/ -UseBasicParsing
On macOS or Linux (Terminal):
<code>nslookup secure.softwarekey.com curl -v https://secure.softwarekey.com/
How to read the results:
- If
nslookupfails, the computer cannot resolve the host name. This is a DNS problem, not a firewall port problem. - If
nslookupsucceeds but the connection test fails or times out, outbound TCP 443 is blocked, or traffic is required to go through a proxy. - If the connection succeeds but
curl -vshows a certificate issued by your own firewall or proxy instead of a public certificate authority, SSL/TLS inspection is active for the host. Add the exclusion described above. - If every test succeeds and the application still cannot activate, send the results and the exact error message to your software vendor.
What if the computer cannot be given internet access at all?
Some applications support offline activation (also called manual activation), where the activation is completed from a different computer that does have internet access. Whether this is available depends on the application, so ask your software vendor. Periodic license checks may still require a connection, depending on how the vendor configured the software.
Common questions
Does the licensing server ever connect into our network?
No. All communication is started by the user's computer, outbound, on TCP port 443. No inbound firewall rules or port forwarding are needed.
Do we need to open port 80?
No. Licensing works over HTTPS on port 443, and you can leave outbound port 80 blocked.
Applications always try HTTPS first. Depending on the application and the licensing client it was built with, some applications retry the same request over plain HTTP on port 80 if the HTTPS attempt fails. In some applications that retry can be turned off by the software vendor; in others it cannot. So:
- If you see port 80 traffic to secure.softwarekey.com, it usually means the HTTPS attempt failed first. Check for SSL/TLS inspection, a proxy, or a blocked port 443 rather than opening port 80.
- If your policy prohibits unencrypted outbound traffic, keep port 80 blocked. The retry is then refused, and the application reports a connection error instead of communicating over HTTP. Activation over HTTPS is not affected.
Is the activation traffic encrypted?
When the HTTPS connection succeeds, yes: the software communicates with SOLO Server using TLS 1.2 or TLS 1.3, the same transport encryption a web browser uses. If an application falls back to plain HTTP after a failed HTTPS attempt (described above), that request is not protected by TLS. Blocking outbound port 80 to secure.softwarekey.com prevents the fallback. For details on how a specific application protects its licensing data, ask your software vendor.
Who do we contact if activation still fails?
Contact the software vendor whose product you are activating, and include the results of the tests above and the exact error message. The vendor can confirm which licensing server address their software uses and can contact SoftwareKey if needed.