Open rubenz91 opened 2 years ago
Hello @rubenz91,
It sounds like a TLS issue, could you try running:
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
And then connecting to your Rubrik Cluster using Connect-Rubrik
to see if that makes any difference.
In case this is the issue, we've got this documented, for the installation of the module here:
Or head over to the official Microsoft documentation, also linked to in our documentation, on configuring TLS 1.2 for older systems:
Let me know if that helps!
I get a new error:
VERBOSE: Allowing self-signed certificates
VERBOSE: Gather API Data for Connect-Rubrik
VERBOSE: Gather API Data for Get-RubrikSoftwareVersion
VERBOSE: Selected 1.0 API Data for Get-RubrikSoftwareVersion
VERBOSE: Load API data for Get-RubrikSoftwareVersion
VERBOSE: Description: Retrieves software version of the Rubrik cluster
VERBOSE: Build the URI
VERBOSE: URI = https://xxxxx/api/v1/cluster/me/version
VERBOSE: Build the query parameters for <null>
VERBOSE: URI = https://xxxxx/api/v1/cluster/me/version
VERBOSE: Submitting the request
VERBOSE: Invoking request with a custom timeout of 100 seconds
VERBOSE: GET https://xxxxx/api/v1/cluster/me/version with 0-byte payload
Invoke-WebRequest : The request was aborted: Could not create SSL/TLS secure channel.
At C:\Windows\system32\WindowsPowerShell\v1.0\Modules\Rubrik\Private\Invoke-RubrikWebRequest.ps1:36 char:23
+ ... $result = Invoke-WebRequest -UseBasicParsing -TimeoutSec $rubrikOpt ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebExc
eption
+ FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand
What kind of output do you get when you run the following:
[Net.ServicePointManager]::SecurityProtocol
This is the results in both the server working and the one that is giving the messages I have posted here so far.
Tls, Tls11, Tls12
I've been looking at replicating the issue, but the only way I can get PowerShell 5.1 to generate this error on my end is when TLS isn't configured correctly. So I have come up with the following 3 things we can try:
# Enter your credentials & cluster name
$Credential = Get-Credential
$YourRubrikCluster = 'your.cluster.com'
$VerbosePreference = 'Continue'
$ErrorActionPreference = 'Stop'
& {
trap {$_.exception.tostring()}
[Net.ServicePointManager]::SecurityProtocol.value__
Connect-Rubrik -Server $YourRubrikCluster -Credential $Credential
[Net.ServicePointManager]::SecurityProtocol.value__
}
& {
trap {$_.exception.tostring()}
[Net.ServicePointManager]::SecurityProtocol.value__
Invoke-Webrequest -uri "https://$YourRubrikCluster/api/v1/vmware/vm?limit=1" -method get -header @{'Authorization' = 'Basic {0}' -f [System.Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes("$($credential.UserName):$($credential.GetNetworkCredential().password)"))} -UseBasicParsing
[Net.ServicePointManager]::SecurityProtocol.value__
}
& {
trap {$_.exception.tostring()}
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
[Net.ServicePointManager]::SecurityProtocol.value__
Connect-Rubrik -Server $YourRubrikCluster -Credential $Credential
[Net.ServicePointManager]::SecurityProtocol.value__
}
& {
trap {$_.exception.tostring()}
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
[Net.ServicePointManager]::SecurityProtocol.value__
Invoke-Webrequest -uri "https://$YourRubrikCluster/api/v1/vmware/vm?limit=1" -method get -header @{'Authorization' = 'Basic {0}' -f [System.Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes("$($credential.UserName):$($credential.GetNetworkCredential().password)"))}
[Net.ServicePointManager]::SecurityProtocol.value__
}
& {
trap {$_.exception.tostring()}
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls -bor [Net.SecurityProtocolType]::Tls11 -bor [Net.SecurityProtocolType]::Tls12
[Net.ServicePointManager]::SecurityProtocol.value__
Connect-Rubrik -Server $YourRubrikCluster -Credential $Credential
[Net.ServicePointManager]::SecurityProtocol.value__
}
& {
trap {$_.exception.tostring()}
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls -bor [Net.SecurityProtocolType]::Tls11 -bor [Net.SecurityProtocolType]::Tls12
[Net.ServicePointManager]::SecurityProtocol.value__
Invoke-Webrequest -uri "https://$YourRubrikCluster/api/v1/vmware/vm?limit=1" -method get -header @{'Authorization' = 'Basic {0}' -f [System.Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes("$($credential.UserName):$($credential.GetNetworkCredential().password)"))} -UseBasicParsing
[Net.ServicePointManager]::SecurityProtocol.value__
}
Hello,
So I recently upgraded on of our Brik and decided to update as well my 5.2 SDK that had been working without issues.
My environment is two Servers that function as the Gateway to connect to Rubrik. One of those servers is in passive state, meaning is waiting in case anything happens in the main one.
Upgrade was performed in both, but my passive one now is triggering the below code error when trying to run:
Connect-Rubrik XXXXXXX -Credential domain\user securepassword
Current Behavior:
Expected Behavior:
I'm expecting to go over and log on normally over Powershell
Steps to Reproduce:
Please provide detailed steps for reproducing the issue.
1- Automation System call to a powershell script 2- Powershell Script import the rubrik module and try to connect
Context:
Get-Module -ListAvailable Rubrik
$PSVersiontable.PSVersion