I can't connect a Server to Azure ARC

Arthur Marinho Liporase Fragoso 0 Reputation points
2023-10-11T18:58:26.8333333+00:00
When I try to run the script it gives the error:


Invoke-WebRequest : The underlying connection was closed: Could not establish trust relationship for the SSL/TLS
secure channel.
At line:23 char:5
+     Invoke-WebRequest -UseBasicParsing -Uri "https://gbl.his.arc.azure.com/log"  ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebExc
   eption
    + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand
Azure Arc
Azure Arc
A Microsoft cloud service that enables deployment of Azure services across hybrid and multicloud environments.
412 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Rohit Singh 10 Reputation points
    2024-02-15T13:37:20.65+00:00

    Hey! We faced a similar issue in some of our on prem servers. Took a long time but we finally had a solution (or workaround). Please try below and let me know if it worked. :)

    1. Check whether all the azure root CAs are installed on the servers. You can find them here: https://video2.skills-academy.com/en-us/azure/security/fundamentals/azure-ca-details?tabs=root-and-subordinate-cas-list#root-certificate-authorities
    2. Use MMC on the machine to verify you have Digicert Global Root CA, Digicert Global Root G2, Digicert Global Root G3, Digicert Global Root G4.
    3. import whichever certificate is missing (import both in "Current user" as well as "Local machine")
    4. run the Arc onboarding script
    5. if the script doesn't work, get the "AzureConnectedMachineAgent.msi" from a working server/browser and install the agent manually.
    6. if you use proxy, use "azcmagent config set proxy.url "proxy.com:port" " command to set it.
    7. now run the "azcmagent connect" command to connect your machine to ARC.
    2 people found this answer helpful.

  2. Mohamed Elshal 0 Reputation points
    2024-07-28T05:31:24.27+00:00

    Had the exact same issue. when I used PowerShell through cmd the script ran, and the server was successfully onboarded.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.