Edge Encryption Proxy fails to connect with a warning "This proxy ***** is already registered in the ServiceNow instance".Issue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms Edge Encryption Proxy fails to connect with a warning "This proxy ***** is already registered in the ServiceNow instance". This issue is sometimes seen after an Edge Encryption Upgrade. Release All releases. Cause The warning occurs due to the GUID of edge encryption proxy being registered in ServiceNow. Resolution Use the following steps to resolve this issue: Shut down the proxy Delete the affected proxy record from the instance: https://{instance_name}.service-now.com/sys_encryption_proxy_list.do3. Remove GUID record on the proxy. Go to <proxy_installation_directory>/conf and delete edgeencryption.guid 4. Restart the proxy. The proxy restart will generate a new GUID and recreate an entry in the instance. This should fix the issue.