
In Spire Desktop version 3.9 and higher, you may see a certificate message when logging in using the server name or IP address. This behavior is expected.
If the message appears when logging in with your Hostname (for example, cooperative-river.spirelan.com), follow the steps below to resolve the issue.
When This Message Is Expected
If you log in using:
The Server Name, or
The IP Address
The certificate warning message is by design. Simply click Ignore to continue.
No further action is required.
When This Message Is NOT Expected
If you log in using your Hostname (for example, yourcompany.spirelan.com) and receive the certificate message, this indicates an issue with the API Server certificate.
Start by:
Restarting the Spire API Server Service from Windows Services.
If the issue persists, proceed with one of the resolution methods below.
Method 1: Recreate Certificate Files (Recommended First Step)
On the server, navigate to:
C:\ProgramData\Spire\ServerCreate a new folder named:
ArchiveMove the three existing files from the Server folder into the new Archive folder.
Restart the Spire API Service from Windows Services.
Open the following link on the server:
https://localhost:10880/setupLog in if prompted. The setup process will attempt to recreate the hostname and guide you through that portion of setup again.
Confirm that three new files are created in:
C:\ProgramData\Spire\ServerOnce confirmed, delete the Archive folder.
After completing these steps, test logging in again using your Hostname.
Method 2: Reinstall the Spire Server (Alternative Solution)
If Method 1 does not resolve the issue, perform the following:
Rename the folder:
C:\ProgramData\Spire\Server
toC:\ProgramData\Spire\ServerBURun the Spire Server Installer again.
When prompted, select the same Hostname you were previously using. A new certificate will be generated.
Test the login using your Hostname.
If everything works as expected, delete the folder:
C:\ProgramData\Spire\ServerBU
Following either method will regenerate the certificate files required for secure Hostname connections and eliminate the certificate warning message.
If the issue continues after completing both methods, please contact Spire Support for further assistance.