@cloudstack.apache.org
Onderwerp: Re: Console proxy SSL
Hi Jimmy,
The below article might help you, you are using the wildcard certificate right?
https://www.shapeblue.com/securing-cloudstack-4-11-with-https-tls/
-Jithin
From: Jimmy Huybrechts
Date: Wednesday, 8 November 2023 at 9:52 PM
To
Hi Jimmy,
The below article might help you, you are using the wildcard certificate right?
https://www.shapeblue.com/securing-cloudstack-4-11-with-https-tls/
-Jithin
From: Jimmy Huybrechts
Date: Wednesday, 8 November 2023 at 9:52 PM
To: users@cloudstack.apache.org
Subject: Console proxy SSL
Hi
See if you can get any inspiration from this guy:
https://leo.leung.xyz/wiki/CloudStack#Traefik (that's just the proxying
subsection, but best read the whole SSL thing).
---
Nux
www.nux.ro
On 2023-01-02 21:16, m...@swen.io wrote:
Hello everyone,
first of all a happy new year to all of you!
Hi,
Have you uploaded the SSL certificate in cloudstack ?
You can refer to
https://www.shapeblue.com/securing-cloudstack-4-11-with-https-tls/
-Wei
On Mon, 2 Jan 2023 at 22:18, wrote:
> Hello everyone,
>
>
>
> first of all a happy new year to all of you! :-)
>
>
>
> I am doing some kind of PoC
Message-
From: Andrija Panic
Sent: Thursday, July 1, 2021 4:22 PM
To: users
Subject: Re: Console Proxy & SSL
Hi Mike,
certificate for securing UI and the certificate for securing access to
Console of the VM (i.e. securing HTTPS access from browser to the public IP
of the CPVM/SSVM) a
I suggest you just do SSL for console proxy, and setup another server
with SSL cert and reverse proxy to your Management server .
On Fri, Jul 2, 2021 at 4:22 AM Andrija Panic
wrote:
> Hi Mike,
>
> certificate for securing UI and the certificate for securing access to
> Console of the VM (i.e.
Hi Mike,
certificate for securing UI and the certificate for securing access to
Console of the VM (i.e. securing HTTPS access from browser to the public IP
of the CPVM/SSVM) are 2 completely different things - and you can/should
use 2 different certificates.
Please read this article - it's very c
To help me with troubleshooting, could one of the developers let me know where
the wildcard certificate is loaded into the ssvm and consolevm? Is there a way
to verify the custom wildcard cert I’ve uploaded is where it should be? I’m
seeing this error in the ACS logs.
Should the CA wildcard ce
I had the exact same issue Konstantinos, but by URL encoding the
certificates they all were accepted and then functioned correctly.
- Ian
On Tue, May 6, 2014 at 10:29 AM, Konstantinos Karampogias <
konstantinos.karampog...@centralway.com> wrote:
> I was also able to upload the root certificate
I was also able to upload the root certificate and the intermediate
certificate using exactly
the script in this link
http://www.chipchilders.com/blog/2013/1/2/undocumented-feature-using-certificate-chains-in-cloudstack.html
I was not able to put my certificate and private key using the script,
bu
I was able to get it all to work using the API.
I followed Chip's advice
http://www.chipchilders.com/blog/2013/1/2/undocumented-feature-using-certificate-chains-in-cloudstack.html
The difference is is that I'm using my own CloudStack API wrapper in PHP
and the certificates and private key needed
Yes... I have changed manually id in keystore tables.
1 for root cert
2 for intermediate CA
3 for certificate
On Tue, May 6, 2014 at 10:47 AM, Amogh Vasekar wrote:
> Can you please outline the steps in uploading intermediate and root
> certificates? Specifically, was the "id" parameter set (1
Can you please outline the steps in uploading intermediate and root
certificates? Specifically, was the "id" parameter set (1 for root, 2 for
intermediate_ca_1 etc..)
Amogh
On 5/5/14 10:10 PM, "Gopala Krishnan" wrote:
>Amogh,
>
>Yes.. I am used Cloudstack 4.2 and uploaded root and intermediate
Amogh,
Yes.. I am used Cloudstack 4.2 and uploaded root and intermediate CA
certificate as per order. But still not console accessible.
Any idea?
On Sat, May 3, 2014 at 11:58 PM, Amogh Vasekar wrote:
> Hi,
>
> Which version are you on? Also, did you upload the root and intermediate
> certifi
Hi,
Which version are you on? Also, did you upload the root and intermediate
certificates (if any)?
Amogh
On 5/3/14 3:38 AM, "Gopala Krishnan" wrote:
>Hi,
>
>I have tried to change realhostip.com for console proxy. I have created
>SSL
>certificate with wildcard SSL and updated as per the cloud
Self-signed is fine, just need to store it in the keystone as described on
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Enabling+SSL+in+the+CloudStack+UI
On Nov 5, 2013, at 10:05 AM, Paulo Ricardo
wrote:
> Hello everybody,
>
> After I generate a new 2048-bit private key and generate
playing with it a bit, and before you do so... check the
formatting of the rows in the table before you change them.
>
> -Original Message-
> From: Pranav Saxena [mailto:pranav.sax...@citrix.com]
> Sent: Friday, June 21, 2013 9:41 AM
> To: users@cloudstack.apache.org
> S
4.1.0 for an impending
deployment next week, and this is the last roadblock.
Thanks again!
-WPR
-Original Message-
From: Pranav Saxena [mailto:pranav.sax...@citrix.com]
Sent: Friday, June 21, 2013 9:41 AM
To: users@cloudstack.apache.org
Subject: RE: Console Proxy SSL
You are getting a NPE
Ramsay [mailto:bram...@dynamicquest.com]
Sent: Friday, June 21, 2013 7:07 PM
To: users@cloudstack.apache.org
Subject: RE: Console Proxy SSL
>> Greetings,
>>
>> We just completed a clean install of 4.1.0. I was able to
>> successfully upload a custom certificate for
>> Greetings,
>>
>> We just completed a clean install of 4.1.0. I was able to successfully
>> upload a custom certificate for use by the console proxy machines in
>> our old
>> 4.0.1 environment, but now I cannot get it to work for the life of me
>> in 4.1.0.
>>
>> The UI just says "failed to
On Fri, Jun 21, 2013 at 08:33:44AM -0400, Billy Ramsay wrote:
> Greetings,
>
> We just completed a clean install of 4.1.0. I was able to successfully
> upload a custom certificate for use by the console proxy machines in our old
> 4.0.1 environment, but now I cannot get it to work for the life of
21 matches
Mail list logo