Failed to get cmg metadata 0x87d00231 - CMG stopped servicing clients overnight Between 10pm and 11pm last night it appears our CMG stopped servicing clients. Locationservices.log indicates "Failed to get CMG metadata 0x87d00231" and if I restart the smsagent service while internet connected I'm seeing what looks like it's referencing a certificate error:

 
CMG Connection point. CMG status is ready and connection point is in Connected status. On the client machine--> Control panel--> Configuration Manager-->Network tab shows the Internet-based MP FQDN correctly which is the CMG. Assigned the new MP site system to the boundary group and confirmed that the client is able to identify the available MPs.. Tracker

We had the wrong root cert in our CMG properties which is why the client didn’t register properly with PKI once that was replaced and the client restarted, it registered fine. Reply Justin Chalfant on August 8, 2021 at 11:01 AMJan 4, 2017 · You are right regarding the security concerns but actually it's a POC server and after that we will replicate to a production environment. And regarding the certificate the CRLis listed on the server and client certificate as below screenshots. Clients failed to connect to CMG MP in the cloud, Site is configured to E-http Client are AAD hybrid. Thanks LocationServices.log: MapNLMCostDataToCCMCost() returning Cost 0x1 LocationServices 27/06/2021 09:28:14 2088 (0x0828)Unexpected response status code is NameResolutionFailure. For more information, Configuration version of the CMG service should be 1. Failed to get CMG service metadata. For more information, There is no CMG connection point configured to connect to the CMG service. There is no site system roles enabled for the CMG service. The CMG connection analyzer tool fails when testing the CMG channel for a management point that uses a replica database. Errors resembling the following are recorded in the CCM_STS.log Return code: 500, Description: Failed to get info from DB, System.Data.SqlClient.SqlException (0x80131904): Invalid object name 'fn_GetUserResourceMapping'.Apr 9, 2021 · Good afternoon Team. I hope you are well. I have a question, in my client we are installing the client via client push, at the end gives me as code 0 but the client still does not register. When reviewing the log file… Mar 5, 2020 · One of our stations fails to connect to SCCM, the log errors are: RegTask: Failed to send registration request message. Error: 0x87d00231. RegTask: Failed to send registration request. Error: 0x87d00231. If this is related then the MP is set to HTTP. Prajwal Desai is a Microsoft MVP in Intune and SCCM. He writes articles on SCCM, Intune, Windows 365, Azure, Windows Server, Windows 11, WordPress and other topics, with the goal of providing people with useful information.Successfully queued event on HTTP/HTTPS failure for server 'CMG.CLOUDAPP.NET'. CcmMessaging 08-02-2022 9.41.45 AM 23900 (0x5D5C) Post using domain\user security context failed due to Integrated Windows Authentication failure CcmMessaging 08-02-2022 9.41.45 AM 23900 (0x5D5C)Jun 27, 2021 · 1st and foremost you're absolutely welcome. 2nd, if all you need for the time being is an image in wim format than forget about combining ConfigMgr and MDT. You honestly don't need to combine them at this point. SCCM is your deployment and management tool. MDT is the imaging tool. Hell, you don't... Sep 17, 2020 · We have a customer that has a functional ConfigMgr (CB 2006) environment with a newly configured CMG and Co-Management enabled. All of the CMG related settings and EHTTP settings are enabled. Machines that are Hybrid-AD joined and already have the ConfigMgr client are able to communicate and download software from the CMG. Sounds like you need to reconfigure it to use HTTPS. We've resolved this, apparently it was becuase we needed to use /mp: https://SCCMServer.FQDN for an install parameter. We were missing the "https://" previously.Jun 27, 2021 · 1st and foremost you're absolutely welcome. 2nd, if all you need for the time being is an image in wim format than forget about combining ConfigMgr and MDT. You honestly don't need to combine them at this point. SCCM is your deployment and management tool. MDT is the imaging tool. Hell, you don't... by MrOarsome Issue with CMG and clients authenticating via Hybrid Azure AD: Failed to send registration request message. Error: 0x87d00231 I have gone through the steps of setting up a CMG with with SCCM CB 1906 and all seems to be behaving. However, when my test clients seem to be unable to connect to the CMG service.Sep 30, 2020 · Unfortunately, 0x87d00231 is a fairly generic error message that pretty much just means “something went wrong”. If you Google it, you will see a variety of solutions ranging from reinstalling the client to checking your PKI environment is functioning correctly or checking the health of your Management Point (s). Oct 28, 2022 · In the Configuration Manager console, go to Administration > Site Configuration > Servers and Site System Roles, and then select <SiteSystemName> in the right pane. In the bottom pane, right-click Software Update Point and then click Properties. On the General tab, specify or verify the WSUS configuration port numbers. SCCM CMG Failed to sign in to Azure – Symptoms. One of the first step to configure the Cloud Management Gateway is to configure the Azure Services. This step consists of creating the connection to the Azure Tenant and create 2 Web Applications, the ConfigMgr Server Application, and ConfigMgr Client Application.Sep 17, 2020 · We have a customer that has a functional ConfigMgr (CB 2006) environment with a newly configured CMG and Co-Management enabled. All of the CMG related settings and EHTTP settings are enabled. Machines that are Hybrid-AD joined and already have the ConfigMgr client are able to communicate and download software from the CMG. In here your CMG certificate chain should include the correct certificate chain. as you can see in the illustration, the issuer of this certificate can’t be found, and as such our trust is broken. To fix the issue, copy and import your missing root certificate(s) to the Azure cloud management gateway server.Error: 0x87d00231 ClientIDManagerStartup 08/11/2022 5:48:12 PM 5540 (0x15A4) RegTask: Failed to send registration request. Error: 0x87d00231 ClientIDManagerStartup 08/11/2022 5:48:12 PM 5540 (0x15A4) [RegTask] - Sleeping for 60 seconds ...Jul 22, 2019 · My lab recently started playing up when I noticed clients weren’t receiving any new policies. TDLR (it’s not even that long!): a while ago I moved my SUP/WSUS off host from the site server that also hosted a MP. ERROR: TaskManager: Task [AnalyticsCollectionTask: Service MyServicecmg] has failed. Exception Microsoft.WindowsAzure.Storage.StorageException, The remote server returned an error: (404) Not Found.. We have attempted to delete and recreate the CMG multiple times but come across the same issue.Hi, I have configured a CMG and deployed to PKI certificate to Client for authentication. However still clients not get registered through CMG. Please help. Location Service ...In here your CMG certificate chain should include the correct certificate chain. as you can see in the illustration, the issuer of this certificate can’t be found, and as such our trust is broken. To fix the issue, copy and import your missing root certificate(s) to the Azure cloud management gateway server.May 19, 2020 · Failed to get ConfigMgr token with Azure AD token. Status code is '401' and status description is 'CMGConnector_Unauthorized'. A possible reason for this failure is the CMG connection point failed to forward the message to the management point. by MrOarsome Issue with CMG and clients authenticating via Hybrid Azure AD: Failed to send registration request message. Error: 0x87d00231 I have gone through the steps of setting up a CMG with with SCCM CB 1906 and all seems to be behaving. However, when my test clients seem to be unable to connect to the CMG service.Failed to get ConfigMgr token with Azure AD token. Status code is '403' and status description is 'CMGConnector_Un-authorizedrequest'. A possible reason for this failure is the CMG connection point failed to forward the message to the management point. The management point returned the following error: 'Un-authorizedrequest'.Note: Non-Microsoft link, just for the reference. Uncheck the check box of Clients check the CRL for site systems from Site Properties. Reinstalled client with /NoCRLCheck CCMHOSTNAME=InternetFQDN with SMSSite code switches. If the response is helpful, please click "Accept Answer" and upvote it. Note: Please follow the steps in our ...Hi All, I uncheck the check box from Site Properties which disable CRL check. I reinstalled client with SMSMP and /NoCRLCheck switches and Client is now appearing in the Console as Active.Unexpected response status code is NameResolutionFailure. For more information, Configuration version of the CMG service should be 1. Failed to get CMG service metadata. For more information, There is no CMG connection point configured to connect to the CMG service. There is no site system roles enabled for the CMG service. Hello guys, Since two days ago, our Windows 10 client computers stopped reporting currently logged on users and are showing offline, although they're..Sep 30, 2020 · Unfortunately, 0x87d00231 is a fairly generic error message that pretty much just means “something went wrong”. If you Google it, you will see a variety of solutions ranging from reinstalling the client to checking your PKI environment is functioning correctly or checking the health of your Management Point (s). Below are the result from the CA. [Green] CMG in ready state. [Red] Connect to the CMG service to see if it's running. [Red] Check configuration setting of the CMG service is up to date. [Yellow] Check connection status of CMG connection points. [Green] Check CMG enabled site systems roles. [Red] testing the CMG channel for management point.Jul 15, 2019 · Once the device token works, the request is sent to internal MP via CMG to get a CCM token. Client must get a CCM token successfully before accessing internal resources. CCM_STS.log available on the Management Point enabled for CMG traffic is a good place to know if CCM token was issued successfully. ProcessRequest - Start CCM_STS The Application Catalog role configured an IIS redirect on the default web site so that all requests to the server were getting redirected to the Application catalog. Simply disabling the redirect and restarting IIS was enough to get our client install working across the CMG using AAD authentication with no PKI required.Failed to verify that the given file is a valid installation package. 782-2146893560: 2148073736: 0×80090108: Failed to access all the provided program locations. This program will not retry. 783-2146893562: 2148073734: 0×80090106: Failed to verify the executable file is valid or to construct the associated command line. 784-2146893564: ...Post to https:///ccm_system/request failed with 0x87d00231. LOCATIONSERVICES: Unable to retrieve AD site membershipMost clients (I didn't check all) look ok (packages are being downloaded and installed). This is one primary site (ad domain) with one MP and few DPs . Clients are installed via push wizard. What i did: client reinstall (ccmsetup.exe /uninstall and also try with ccmclean.exe from sms2003 pack) telnet to MP port 80 (is ok) delete client account ...Sep 30, 2020 · Unfortunately, 0x87d00231 is a fairly generic error message that pretty much just means “something went wrong”. If you Google it, you will see a variety of solutions ranging from reinstalling the client to checking your PKI environment is functioning correctly or checking the health of your Management Point (s). However, I've hit a wall when switching the MP over to HTTPS. The clients still continue to use HTTP! For the record, the overall Client Security settings are still set to 'HTTP or HTTPS' (without Enhanced HTTP turned on). From CCMEVAL I can see that it clearly tries to use HTTP. Client is set to use HTTPS when available. The current state is 480.Dec 16, 2022 · Thought id throw 2 cents in here, Brilliant mark up Prajwal, been a fan for awhile. if your running an earlier version of SCCM – Ver 2107. MS came back with a workaround (and officially confirmed it as a bug still present in 2107). Cloud Management Gateway - client side problems. SOLVED It seems like it solved itself or by me rebooting the primary site server and/or the CMG. CMG is set up in our CM 1910 env by using a public wildcard certificate. That is all green in the console, as well as the CMG connection point. We are using Enhanced HTTP and hope to use AAD identity ...I have set up a cloud management gateway in my MECM Environment. PKI Infrastructure is also in place, and it is working as expected. The MECM clients function fine when communicating with the local MP (on-premises MP); however, clients cannot discover a…I’m paranoid. We recently upgraded our site to ConfigMgr 2002, first fast ring, then the hotfix. We also installed a Cloud Management Gateway, re-worked our Boundary Groups to handle VPN better, added a second Management Point and generally made a butt-load of changes to our environment to help our remote clients have access to content more easily.One of our stations fails to connect to SCCM, the log errors are: RegTask: Failed to send registration request message. Error: 0x87d00231. RegTask: Failed to send registration request. Error: 0x87d00231. If this is related then the MP is set to HTTP.This article describes an issue in which content can't be downloaded from a cloud management gateway (CMG) that functions as a cloud distribution point (DP), and you receive an WINHTTP_CALLBACK_STATUS_FLAG_CERT_CN_INVALID error message. Original product version: Configuration Manager (current branch) Original KB number: 4495265 SymptomsThe Application Catalog role configured an IIS redirect on the default web site so that all requests to the server were getting redirected to the Application catalog. Simply disabling the redirect and restarting IIS was enough to get our client install working across the CMG using AAD authentication with no PKI required.ClientIDManagerStartup 3/16/2018 9:13:33 AM 7968 (0x1F20) CCM Identity is in sync with Identity stores ClientIDManagerStartup 3/16/2018 9:13:33 AM 7968 (0x1F20) Begin searching client certificates based on Certificate Issuers ClientIDManagerStartup 3/16/2018 9:13:33 AM 7968 (0x1F20) Certificate Issuer 1 [CN=Entrust Root Certification Authority ...When running the CMG validation checker All checks are successful except the last one and it reports the following error: Succeed to get ConfigMgr token with Azure AD token. Failed to refresh MP location. Status code is ‘500’ and status description is ‘CMGConnector_InternalServerError’. A possible reason for this failure is the CMG ...Sep 17, 2020 · We have a customer that has a functional ConfigMgr (CB 2006) environment with a newly configured CMG and Co-Management enabled. All of the CMG related settings and EHTTP settings are enabled. Machines that are Hybrid-AD joined and already have the ConfigMgr client are able to communicate and download software from the CMG. Jul 20, 2018 · Failed to get ConfigMgr token with Azure AD token. Status code is ‘503’ and status description is ‘CMGConnector_ServiceUnavailable’. A possible reason for this failure is the CMG connection point failed to forward the message to the management point. The management point returned the following error: ‘ServiceUnavailable’. However, I've hit a wall when switching the MP over to HTTPS. The clients still continue to use HTTP! For the record, the overall Client Security settings are still set to 'HTTP or HTTPS' (without Enhanced HTTP turned on). From CCMEVAL I can see that it clearly tries to use HTTP. Client is set to use HTTPS when available. The current state is 480.Posts about 0x87d00231 written by Leldance40k. I am torn between two lines of thought. It’s down to the “No CRL checking” option being set on the Config Manager site server; whilst this may bypass some CRL “stuff”, it’s needed for to get other things going. Oct 3, 2022 · Choose the certificate type. Globally unique name. Issue the certificate. Create a DNS CNAME alias. Next steps. Applies to: Configuration Manager (current branch) The first step when you set up a cloud management gateway (CMG) is to get the server authentication certificate. The CMG creates an HTTPS service to which internet-based clients ... we set up a testing environment for bitlocker purposes and because of new features for bitlocker we updated yesterday from 1910 to 2002. Update was done fine but now our 3 clients dont contact SCCM anymore. we tried to install new ccm client manually but ccmsetup.log shows a lot of errors. After checking PKI we solved on problem and clients can ...Apr 10, 2019 · Failed to get ConfigMgr token with Azure AD token. Status code is '403' and status description is 'CMGConnector_Un-authorizedrequest'. A possible reason for this failure is the CMG connection point failed to forward the message to the management point. The management point returned the following error: 'Un-authorizedrequest'. Apr 9, 2021 · Good afternoon Team. I hope you are well. I have a question, in my client we are installing the client via client push, at the end gives me as code 0 but the client still does not register. When reviewing the log file… I think the issue is with client to MP communication. Are you using any proxy within the network is blocking traffic on port 80 ?. Because i see that when you browse through the URL that you specified, you get ERROR_WINHTTP_CONNECTION_ERROR. What's in the ClientIDManagerStartup.log ?. Can you upload that file ?.Jun 27, 2021 · 1st and foremost you're absolutely welcome. 2nd, if all you need for the time being is an image in wim format than forget about combining ConfigMgr and MDT. You honestly don't need to combine them at this point. SCCM is your deployment and management tool. MDT is the imaging tool. Hell, you don't... Oct 27, 2018 · Expert-led, virtual classes. Microsoft Virtual Academy. Free Windows Server 2012 courses. Microsoft Official Courses On-Demand. MCSE Cloud Platform and Infrastructure. MCSE: Mobility. MCSE: Data Management and Analytics. MCSE Productivity. Find technical communities in your area. [ccmsetup] Failed to get MDM_ConfigSetting instance, 0x80041010_Cloud Management Gateway - client side problems. SOLVED It seems like it solved itself or by me rebooting the primary site server and/or the CMG. CMG is set up in our CM 1910 env by using a public wildcard certificate. That is all green in the console, as well as the CMG connection point. We are using Enhanced HTTP and hope to use AAD identity ...Apr 29, 2021 · When running the CMG validation checker All checks are successful except the last one and it reports the following error: Succeed to get ConfigMgr token with Azure AD token. Failed to refresh MP location. Status code is ‘500’ and status description is ‘CMGConnector_InternalServerError’. A possible reason for this failure is the CMG ... Jan 15, 2021 · Specify a name and select Cloud Management, click Next. In this step, the Azure Administrator will be required to create the web app and native client app. Click on Browse for the Web app. Click on Create. Click the Sign in and provide Azure administrator credentials. Default names do just fine. Unfortunately, 0x87d00231 is a fairly generic error message that pretty much just means “something went wrong”. If you Google it, you will see a variety of solutions ranging from reinstalling the client to checking your PKI environment is functioning correctly or checking the health of your Management Point (s).Nov 9, 2022 · Error: 0x87d00231 ClientIDManagerStartup 08/11/2022 5:49:12 PM 5540 (0x15A4) RegTask: Failed to send registration request. Error: 0x87d00231 ClientIDManagerStartup 08/11/2022 5:49:12 PM 5540 (0x15A4) [RegTask] - Sleeping for 60 seconds ... Locationservices.log indicates "Failed to get CMG metadata 0x87d00231" and if I restart the smsagent service while internet connected I'm seeing what looks like it's referencing a certificate error: Successfully queued event on HTTP/HTTPS failure for server 'CMG.CENTRALUS.CLOUDAPP.AZURE.COM'.Connect to the CMG service to see if it's running. Failed to connect to the CMG service. Unexpected response status code is NameResolutionFailure. For more information, see SmsAdminUI.log. Check configuration settings of the CMG service is up to date. Configuration version of the CMG service should be 5. Failed to get CMG service metadata.CMG stopped servicing clients overnight Between 10pm and 11pm last night it appears our CMG stopped servicing clients. Locationservices.log indicates "Failed to get CMG metadata 0x87d00231" and if I restart the smsagent service while internet connected I'm seeing what looks like it's referencing a certificate error: However, I've hit a wall when switching the MP over to HTTPS. The clients still continue to use HTTP! For the record, the overall Client Security settings are still set to 'HTTP or HTTPS' (without Enhanced HTTP turned on). From CCMEVAL I can see that it clearly tries to use HTTP. Client is set to use HTTPS when available. The current state is 480.we set up a testing environment for bitlocker purposes and because of new features for bitlocker we updated yesterday from 1910 to 2002. Update was done fine but now our 3 clients dont contact SCCM anymore. we tried to install new ccm client manually but ccmsetup.log shows a lot of errors. After checking PKI we solved on problem and clients can ...Apr 14, 2020 · Cloud Management Gateway Choices. In most ways, a Cloud Management Gateway (CMG) in Microsoft Endpoint Configuration Manager (ConfigMgr) greatly simplifies any organization’s path to managing their Internet-connected Windows systems. Namely, you don’t have to worry about adding any on-premises infrastructure. Apr 2, 2020 · Hi, for info, there is an order. We recently had issues with some our servers in the DMZ, most used the token, however we had a couple that already had certs on them using their FQDN which wouldn’t register in the console. If so, please check if the SSL certificate common name (host name field) is correct and the hostname the client is connecting to is matched with the certificate's subject or subject alternate name. It is recommended that we could check the certificate and use the FQDN of the server in the Common Name section.Specify a name and select Cloud Management, click Next. In this step, the Azure Administrator will be required to create the web app and native client app. Click on Browse for the Web app. Click on Create. Click the Sign in and provide Azure administrator credentials. Default names do just fine.Jun 2, 2021 · Hello guys, Since two days ago, our Windows 10 client computers stopped reporting currently logged on users and are showing offline, although they're.. Error: 0x87d00231 ClientIDManagerStartup 11/20/2017 3:58:37 PM 2888 (0x0B48) RegTask: Failed to send registration request. Error: 0x87d00231 ClientIDManagerStartup 11/20/2017 3:58:37 PM 2888 (0x0B48)My lab recently started playing up when I noticed clients weren’t receiving any new policies. TDLR (it’s not even that long!): a while ago I moved my SUP/WSUS off host from the site server that also hosted a MP.Oct 3, 2022 · Client verifies the CMG server authentication certificate: PKI certificate: Client requires the root CA of the CMG certificate in its local store. Third-party certificate: Clients automatically validate a certificate with its root CA published on the internet. CMG, CMG connection point, and management point validate Azure AD and CCM tokens. Oct 28, 2022 · In the Configuration Manager console, go to Administration > Site Configuration > Servers and Site System Roles, and then select <SiteSystemName> in the right pane. In the bottom pane, right-click Software Update Point and then click Properties. On the General tab, specify or verify the WSUS configuration port numbers. Hi, I have installed in our environment SCCM CMG and the client is unable to receive software updates. This is what I see in WUAHandler.log: Its a WSUS Update Source type ({A4BF5916-DF74-44C1-BF58-68AE14A43278}), adding it. …Jun 2, 2021 · Hello guys, Since two days ago, our Windows 10 client computers stopped reporting currently logged on users and are showing offline, although they're.. The Application Catalog role configured an IIS redirect on the default web site so that all requests to the server were getting redirected to the Application catalog. Simply disabling the redirect and restarting IIS was enough to get our client install working across the CMG using AAD authentication with no PKI required.Today I wanted to share with you a series of short videos that offer tips on how to address and mitigate common issues you might encounter when setting up the cloud management gateway (CMG) as part of your Configuration Manager environment. Before we begin, a quick reminder that the Microsoft Endpoint Manager admin center can be accessed ...This check looks at the following settings: In the Configuration Manager console, go to the Administration workspace, expand Site Configuration, and select the Sites node. Select a site, and then in the ribbon select Properties. Switch to the Communication Security tab. Configure one of the following options: This check occurs every 25 hours, when the SMS Agent Host service starts or when it detects a network change. When the client connects to the site and learns of a CMG, it automatically updates this valu e. After learning about CMG, Internet Management Point values will be updated. SCCM Client side log validation We had the wrong root cert in our CMG properties which is why the client didn’t register properly with PKI once that was replaced and the client restarted, it registered fine. Reply Justin Chalfant on August 8, 2021 at 11:01 AM

Jul 22, 2019 · My lab recently started playing up when I noticed clients weren’t receiving any new policies. TDLR (it’s not even that long!): a while ago I moved my SUP/WSUS off host from the site server that also hosted a MP. . Where is the fortune teller

failed to get cmg metadata 0x87d00231

Press J to jump to the feed. Press question mark to learn the rest of the keyboard shortcutsSounds like you need to reconfigure it to use HTTPS. We've resolved this, apparently it was becuase we needed to use /mp: https://SCCMServer.FQDN for an install parameter. We were missing the "https://" previously.Morning, I'm pushing out client to some of our DMZ servers. Client installation finished successfully as far as I can see from ccmsetup.log file. Investigating further, I noticed I kept getting the following in ClientIDManagerStartup.log: RegTask: Failed to send registration request message. Error: 0x87d00231.Since we are using Internal PKI cert on CMG, I have exported the Root certificate and imported into DMZ server, Installation went fine and client was able to communicate well after the installation. It received all policies and able to push software updates/apps. It works fine by changing the "UserCost" value as '0', after that CM client installation gets worked.Hi, I have configured a CMG and deployed to PKI certificate to Client for authentication. However still clients not get registered through CMG. Please help. Location Service ...SCCM 1806 onwards, you have a new in-console utility called CMG connection analyzer. This utility is for real-time verification to help CMG-related troubleshooting. The SCCM in-console utility checks the current status of the service and the communication channel through the CMG connection point to any management points that allow CMG traffic.MDM Session: Failed to get AAD Token for sync session User Token: (The parameter is incorrect.) Device Token: (Incorrect function.). Long story short, I kept removing Device Configuration profiles I had assigned to the device, and the policy causing the issue was to upgrade Pro to Enterprise using an MAK key using the “Edition upgrade” policy. Dec 16, 2022 · Thought id throw 2 cents in here, Brilliant mark up Prajwal, been a fan for awhile. if your running an earlier version of SCCM – Ver 2107. MS came back with a workaround (and officially confirmed it as a bug still present in 2107). Jan 4, 2017 · You are right regarding the security concerns but actually it's a POC server and after that we will replicate to a production environment. And regarding the certificate the CRLis listed on the server and client certificate as below screenshots. May 26, 2017 · MCSE Cloud Platform and Infrastructure. MCSE: Mobility. MCSE: Data Management and Analytics. MCSE Productivity. Find technical communities in your area. MSDN Forums. Security Bulletins & Advisories. Microsoft Community Forums. The first thing we checked here is the port 443 connectivity from this test machine to the CMG public IP using the port query UI tool. Port connectivity was fine, and it was listening for port 443 without any issue. After hours of troubleshooting, we identified that the PKI infrastructure has multiple CAs..

Popular Topics