---
title: "Why won't OmniaSST Decoder generate a valid key?"
slug: "why-wont-omniasst-decoder-generate-a-valid-key"
updated: 2024-12-18T06:19:11Z
published: 2024-12-18T06:19:11Z
canonical: "docs.telosalliance.com/why-wont-omniasst-decoder-generate-a-valid-key"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.telosalliance.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Why won't OmniaSST Decoder generate a valid key?

![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/ed6c2b8e-7f41-482b-b152-9b573d645d26-image.png?sv=2026-02-06&spr=https&st=2026-10-28T18%3A16%3A51Z&se=2026-10-28T19%3A16%3A51Z&sr=c&sp=r&sig=hcXPFa%2Fg2ioJvX8J9wIhoV06yn%2ByfFcVFAlPTrXmOPk%3D)

As of the most current version of SST, uMPX Decoder ships as a separate app. Both apps use port 8080, so SST will open instead of uMPX decoder if both apps are running. You need to quit SST or change uMPX Decoder to port 8081, or other custom port, to get it to launch. Once either of these steps are performed, the request code from uMPX decoder will work for OSSD.

## Let us know how we can help

If you have further questions on this topic or have ideas about improving this document, please [contact us](https://www.telosalliance.com/support-request).