---
title: "Common Name Does Not Match"
slug: "common-name-does-not-match"
updated: 2024-04-04T08:28:55Z
published: 2024-04-04T08:28:55Z
canonical: "kb.pharos.com/common-name-does-not-match"
---

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

# Common Name Does Not Match

The following error occurs for the Omega when testing the EDI connection against a server enabled with SSL

Common Name Does Not Match

---

The name or the IP Address in the URL needs to be the same as the common name used in the certificate.

Example:

Certificate Common Name: collector

Omega URL : [https://192.168.2.172/pharosedi/pedi.wsdl](https://192.168.2.172/pharosedi/pedi.wsdl)

To make this work you need to change the URL to

[https://collector/pharosedi/pedi.wsdl](https://collector/pharosedi/pedi.wsdl)

## Related

- [Print jobs are deleted when queue names do not match Windows printer names exactly.](/print-jobs-are-deleted-when-queue-names-do-not-match-windows-printer-names-exactly.md)
- [Uniprint: Getting the error "The printer name is invalid" when attempting to add a queue in Uniprint](/uniprint-getting-the-error-the-printer-name-is-invalid-when-attempting-to-add-a-queue-in-uniprint.md)
- [Configure the MobilePrint listening port and use a certificate with a name different than the hostname](/configure-the-mobileprint-listening-port-and-use-a-certificate-with-a-name-different-than-the-hostname.md)
- [The numbers of workstations which have the Blueprint tracker installed do not match the number of workstations seen by the Blueprint Analyst](/the-numbers-of-workstations-which-have-the-blueprint-tracker-installed-do-not-match-the-number-of-workstations-seen-by-the-blueprint-analyst.md)