---
title: "Omega & iMFP devices cannot connect to the Blueprint EDI web service using SSL."
slug: "omega-imfp-devices-cannot-connect-to-the-blueprint-edi-web-service-using-ssl"
tags: ["Blueprint", "imfp", "omega", "device", "edi"]
updated: 2024-04-23T19:56:39Z
published: 2024-04-23T19:56:39Z
canonical: "kb.pharos.com/omega-imfp-devices-cannot-connect-to-the-blueprint-edi-web-service-using-ssl"
---

> ## 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.

# Omega & iMFP devices cannot connect to the Blueprint EDI web service using SSL.

Omega & iMFP devices cannot connect to the Blueprint EDI web service using SSL.

---

### **Problem**

1. The Omega and/or iMFP device has been configured to use SSL and tries to connect to the Blueprint EDI using the following address: [https://<servername>/PharosEDI/Pedi_ssl.wsdl](https://%3cservername%3e/PharosEDI/Pedi_ssl.wsdl).
2. A connection cannot be established with the Blueprint EDI web service.
3. No logging appears showing a connection attempt being made in the Blueprint EDI web service logging.
4. Despite this, the Blueprint Server Configuration EDI Service test passes.

---

### **Cause**

Blueprint 3.5 & 3.5 SP1 & related hotfixes do not support the 'Pedi_ssl.wsdl' address format out of the box. As such, calls made to that address will be rejected by Internet Information Services (IIS) prior to being delivered to Blueprint.

### **Resolution**

1. Support for this address format must be added to the Blueprint EDI web service configuration file. This file is located in the installation directory at the following relative path: Blueprint\Services\BediService\web.config.
2. Locate the line near the bottom of the web.config file that looks like the following: *<add virtualUrl="~/Pedi.(wsdl|asmx)" destinationUrl="~/BediService.asmx" ignoreCase="true"/>*
3. Replace that line with the following:

*<add virtualUrl="~/Pedi(_ssl)?.(wsdl|asmx)" destinationUrl="~/BediService.asmx" ignoreCase="true"/>*
4. Connection attempts using 'Pedi_ssl.wsdl' should now succeed.

## Related

- [Pharos Blueprint - Tracker and EDI Web Service tests fail](/pharos-blueprint-tracker-and-edi-web-service-tests-fail.md)
- [Lexmark iMFP fails to connect to the Blueprint EDI Service.](/lexmark-imfp-fails-to-connect-to-the-blueprint-edi-service.md)
- [Ricoh iMFP: Certificate error when connecting to the Pharos EDI](/ricoh-imfp-certificate-error-when-connecting-to-the-pharos-edi.md)
- [Blueprint EDI & Tracker Web Service fail with the error "Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'" error.](/blueprint-edi-tracker-web-service-fail-with-the-error-client-found-response-content-type-of-texthtml-charsetutf-8-but-expected-textxml-error.md)