What's the most common cause of Administrator Launcher failing to open?

An incompatible local Java version is the most common cause, particularly right after a general system Java update that wasn't checked against Mirth's specific version requirements first. The error usually names a class version mismatch directly in its message text, making it fairly easy to diagnose.

Does the launcher need the same Java version as the server?

Not necessarily identical, but it does need a Java version compatible with what your specific Mirth release supports for the client side, which can differ from what the server itself is running underneath, depending on the release and its documented requirements.

How do I trust a self-signed certificate in the launcher?

Import the certificate into the Java trust store the launcher relies on, using keytool -importcert, or accept the certificate through any trust prompt the launcher itself presents when first connecting to that server.

Can a firewall change break the launcher without changing the server?

Yes. The server can be running perfectly while a firewall change on the network path, or on the user's own machine, blocks the administrator port entirely, producing a connection failure that has absolutely nothing to do with the server's actual health or configuration.

Why does the launcher work for one user but not another on the same network?

This usually points to a difference on the individual machine — a different local Java version, a missing certificate trust entry, or a local firewall rule — rather than anything shared across the network that would affect every user equally.

Where does the Administrator Launcher store its cached settings?

This varies by operating system and launcher version, typically in a user-specific application data folder, and clearing that cache is often a genuinely useful troubleshooting step when the launcher behaves inconsistently after a version or server change on either end of the connection.

Mirth Connect Administrator Launcher Issues: The Fix

TL;DR

Mirth Connect Administrator Launcher failures usually come from one of four layers: an incompatible local Java version, an untrusted self-signed server certificate, a firewall blocking the administrator port, or a version mismatch between the launcher and server. Fix it by installing the Java version your Mirth release supports, trusting the server certificate in the launcher's Java trust store, opening the required port, or matching the launcher version to the server version. Prevent recurrence by documenting Java requirements, renewing certificates proactively, and updating the launcher alongside every server upgrade.

Quick answer

Mirth Connect Administrator Launcher issues usually stop you before you even reach the login screen — the launcher fails to open, throws a Java version error, or connects but immediately rejects the server's certificate. Because the launcher is separate software from the Mirth server itself, the cause is often on your machine rather than the server.

Below is what actually breaks the launcher, the fix for each cause, and how to keep it working through future upgrades. Our free Mirth Health Check can help trace whether it's the launcher, the network, or the server — part of the Mirth Connect support work we do for US healthcare teams.

What Causes Administrator Launcher Problems?

The launcher depends on a compatible local Java runtime, a trusted path to the server's certificate, and network access to the server's administrator port, and a failure in any one of these produces a different but often confusingly similar symptom at the login screen. Narrowing down which specific layer is actually failing, rather than guessing at random, is the fastest and most reliable way through this, since each layer needs its own distinct fix.

Administrator Launcher Running an Incompatible Java Version

If the Java runtime available to the launcher doesn't match what your Mirth version requires, it fails with an error like UnsupportedClassVersionErrorrather than opening at all. This is common after a general Java update on the user's machine.

Self-Signed Server Certificate Not Trusted by the Launcher

Many Mirth servers run with a self-signed certificate on the administrator port, and the launcher will refuse to connect until that certificate is explicitly trusted, either in the launcher itself or the underlying Java installation's trust store.

Firewall Blocking the Administrator Port

If a firewall change on the network or the local machine blocks the port the Administrator client uses to reach the server, the launcher will time out or show a connection-refused error even though the server itself is running fine.

Version Mismatch Between Launcher and Server

An Administrator Launcher built for one Mirth version can fail or behave unpredictably against a server running a different version, especially after the server has been upgraded without updating the launcher used to connect to it.

How to Fix Administrator Launcher Problems

Start by confirming which of the four causes matches the exact error shown, since a Java version problem and a certificate problem produce visibly different failure messages even though both stop you at the same login screen. The fixes below match the four causes in order, so apply the one that fits the specific message you're actually seeing, rather than trying every option in sequence and hoping something eventually works.

Install the Java Version Mirth Actually Supports

Check your specific Mirth release's documentation for its required or supported Java version, and install or switch to that version specifically rather than assuming the system default Java is compatible.

Trust the Server Certificate in the Launcher

Import the server's certificate into the Java trust store the launcher uses, or accept it explicitly if the launcher offers a prompt to do so. This step needs repeating whenever the server's certificate is renewed or replaced.

Open the Required Port in the Firewall

Confirm the administrator port with your Mirth documentation, then verify it's open on any firewall between the user's machine and the server, including local machine firewalls that are often overlooked during network-level checks.

Match Launcher Version to Server Version

Download and install the Administrator Launcher version that corresponds to your current server version, and repeat this step every time the server itself is upgraded, since the two are meant to move together.

How to Prevent Launcher Issues After Upgrades

Most Administrator Launcher problems surface right after some other change — a Java update, a certificate renewal, or a server upgrade — so prevention is mostly about treating the launcher as something that always needs updating alongside those changes, rather than something users only think about once it's already broken and blocking their day-to-day work. A short checklist covering all four habits below takes only minutes to run through.

Document the Supported Java Version for Each Mirth Release

Keep a record of which Java version each Mirth release actually requires, and check it before any general Java update rolls out across your organization's machines, since IT teams rarely know Mirth's specific version constraints without being told.

Keep a Valid Certificate on the Administrator Port

Renew the server's certificate before it expires and communicate the change to anyone connecting through the launcher, so they know to re-trust it rather than assuming the launcher is simply broken.

Maintain a Firewall Rule Reference for Required Ports

Document every port the Administrator Launcher needs to reach the server, and reference it whenever network changes are planned, so a routine firewall update doesn't unintentionally cut off administrator access for an entire team.

Update the Launcher Alongside Every Server Upgrade

Treat launcher updates as a required step in your server upgrade checklist, not an afterthought users handle on their own whenever they next notice a problem connecting after the fact.

When to call for help

If you've confirmed Java version, certificate trust, and network access and the launcher still won't connect reliably, a launcher/server version gap is the most likely remaining cause. Our free Mirth Connect health checkcan trace whether it's local, network, or server-side as part of the standard diagnostic.

Book a Free Health Check →

Have the exact error message? Send us the log, or check pricing for ongoing support plans.

Mirth Connect Administrator Launcher Issues: Causes and Fix