cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joshua Schaeffer <jschaef...@harmonywave.com>
Subject Re: Network error when uploading local ISO
Date Sat, 10 Jul 2021 07:38:31 GMT
Thanks for everyone's help on this. I was able to successfully upload a local ISO file after
following the blog post.

On 7/6/21 5:34 AM, Andrija Panic wrote:
> The default SSL might be the old *.realhostip.com - which is not to be used
> in any similar-to-production way - but yes, this is a good workaround to
> accept that browser warning, and later actions work fine
>
>
> On Tue, 6 Jul 2021 at 08:56, Vivek Kumar <vivek.kumar@indiqus.com.invalid>
> wrote:
>
>> I did the same way a long back..! If you are using any self signed
>> certificate for testing or something.!
>>
>>
>>
>>> On 05-Jul-2021, at 1:15 PM, Abishek Budhathoki <abckdc83@gmail.com>
>> wrote:
>>> If it may help,
>>> Please open the ssvm public IP https://192.41.41.161/ in the new tab of
>> the running browser and accept the certificate warning and try again
>> uploading the ISO.
>>> Faced the same issue at first while not using ssl for system vms.
>>> Thank You.
>>>
>>> On 2021/07/05 00:23:34, Joshua Schaeffer <jschaeffer@harmonywave.com>
>> wrote:
>>>> On 7/4/21 4:16 PM, Andrija Panic wrote:
>>>>> What's the value of your global config parameters:
>>>>>
>>>>> consoleproxy.url.domain
>>>> Empty/blank
>>>>> consoleproxy.sslEnabled
>>>> False
>>>>> secstorage.ssl.cert.domain
>>>> Empty/blank
>>>>> secstorage.encrypt.copy
>>>> False
>>>>> I expect last one or second to last one is wrong/not set - since your
>>>>> browser is showing the request POST being sent to HTTPS:<IP_ADDRESS>
(
>>>>> https://192.41.41.161) instead of <DNS_NAME> (https://192-41-41-161
>>>>> .<SSL_DOMAN_HERE.com>
>>>>>
>>>>> Best,
>>>>>
>>>>> On Fri, 2 Jul 2021 at 17:35, Joshua Schaeffer <
>> jschaeffer@harmonywave.com>
>>>>> wrote:
>>>> If this could be related to SSL/TLS then I should probably mention I
>> have set the ca.plugin.root.auth.strictness to "false". I can't remember
>> the exact error I get but I  know I got an error on a new install if I
>> didn't do this. I could turn it back on and check if that would provide
>> more info. I should also mention that I have not done any SSL/TLS at this
>> point except at the load balancer and that does SSL termination. Are there
>> any guides/documentation on how best to set these values?
>>>> --
>>>> Thanks,
>>>> Joshua Schaeffer
>>>>
>>>>
>>

-- 
Thanks,
Joshua Schaeffer


Mime
View raw message