Closed roladdhp closed 4 days ago
Appears the issue is with Self-Signed Certificates. The documentation does not explain this or this could still be an error with the code. However, taking the Self-Signed Certificate and issuing Add-OVApplianceTrustedCertificate with the unsigned certificate prior to running the New-OVExternalRepository command results in the repository being added. Again the documentation needs to reflect this.
I will wait for additional comments before closing the case.
The error message is an error from the appliance itself, not the Cmdlets use. By default, self-signed certificates are never trusted, because the Issuer and Common Name are the same value. The Issuer needs to be trusted in order to use self-signed certs. This issue wouldn't have been with the Cmdlet. This issue should be closed.
Thank you.
Closing this request. Documentation should have a footnote where certificates are used that non-trusted certificates must be added to the trusted store on the appliance. It makes sense, but not clear when working through the command. This is something that becomes trivial, once you have gone through the pain once :-).
Sorry one more comment. The error message should be more clear that the certificate is not trusted or known by the appliance, versus that it can't connect to the webserver.
Again thank you.
I'm having issues with the New-OVExternalRepository command and need help with it unable to connect to the webserver. Below is a detail description of the environment, process and error. Please advise.
Working with Windows 2022, PowerShell 7 (7.4.1), HPEOneView.860 POSH Lib, IIS Windows 2022. OneView for Synergy Ver 870.
Exported BASE64 Self-Signed IIS certificate and saved it to the local directory. IIS has one application called repository which holds the firmware bundle that I wish to access. I can manually access the website (with invalid certificate https: (crossed out), from localhost and from remote client I can manually access the website from the UI of the Synergy OneView Appliance.
However, from the command line this fails. 1) connect to OVMgmt (successful) 2) define and set $remoteserver as ("XX.XX.XX.XXX") and $directory as "repository" 3) New-OVExternalRepository -Name "Synergy_Repo" -Hostname $remoteserver -Directory $directory -Certificate (Get-Content -Path .\webervercert.cer -Raw) 4) New-OVExternalRepository -Name "Synergy_Repo" -Hostname $remoteserver -Directory $directory -Certificate (Get-Content -Path .\webervercert.cer -Raw) -Credential (Get-Credential)
Error:
New-OVExternalRepository: Unable to communicate with the webserver. Verify the webserver address is correct and verify the connectivity between the appliance and the webserver.
Verbose Output from the Command: