Re: Cloudstack 4.16 - GUI unable to submit SSL
I not sure related to this or not, I ssh login to Console Proxy , and
seems port 443 is not listening there .
Is there anyway I can can check in the console proxy, see if the cert is
properly deploy to the console proxy vm.
On Mon, Jan 10, 2022 at 5:31 PM Suresh Anaparti <
suresh.anapa...@shapeblue.com> wrote:
> Hi,
>
> I could see a related issue created here
> https://github.com/apache/cloudstack/issues/5634
>
> If you have the similar issue with Letsencrypt certs, you add more details
> there. Otherwise, please create a new issue with the details.
>
>
> Regards,
> Suresh
>
> On 08/01/22, 11:59 AM, "Hean Seng" wrote:
>
> hi. Suresh
>
> I am gemnerating Letsenctyp and instll the cert using the API .
> I running.time as show in the shapeblue document. It successfully
> running
> the API
>
>
> "customcertificate": {
>
> "message": "Certificate has been successfully updated, if its the
> server certificate we would reboot all running console proxy VMs and
> secondary storage VMs to propagate the new certificate, please give a
> few
> minutes for console access and storage services service to be up and
> working again"
>
> }
>
> }
>
>
>
> running 2time, first time is chain + root
> second time is cert. perm and privatekey pkcs8
>
> after upload, destroy and let it rebuild the console proxy , after
> all
> up, it seems https://ip-.domain in console cannot load as expected
>
>
>
>
> On Wed, Jan 5, 2022 at 8:12 PM Suresh Anaparti <
> suresh.anapa...@shapeblue.com> wrote:
>
> > Hi,
> >
> > You can check the certificate configuration process through API/cmk
> here:
> > https://www.shapeblue.com/securing-cloudstack-4-11-with-https-tls/
> >
> >
> > Regards,
> > Suresh
> >
> > On 05/01/22, 4:55 PM, "Hean Seng" wrote:
> >
> > Any body know how to use the API to upload this cert for console
> proxy,
> > Otherwise this 4.16 is not workable . This function seems no
> > alternative to make it work
> >
> >
> >
> >
>
>
>
> > On Mon, Jan 3, 2022 at 4:08 PM Hean Seng wrote:
> >
> > > Is there anyway to manual update it before 4.16.1 release ,
> > otherwise the
> > > SSL cannot be install.
> > >
> > > On Mon, Jan 3, 2022 at 3:06 PM Suresh Anaparti <
> > > suresh.anapa...@shapeblue.com> wrote:
> > >
> > >> Good, thanks for the update Pearl!
> > >>
> > >>
> > >> Regards,
> > >> Suresh
> > >>
> > >> On 03/01/22, 12:31 PM, "Pearl d'Silva" <
> pearl.dsi...@shapeblue.com>
> > >> wrote:
> > >>
> > >> Hi,
> > >>
> > >> This seems to be an issue in 4.16.0 but has been
> addressed with:
> > >> https://github.com/apache/cloudstack/pull/5682/ and should be
> > available
> > >> in 4.16.1.
> > >>
> > >> Thanks,
> > >> Pearl
> > >>
> > >> [
> > >>
> >
> https://opengraph.githubassets.com/a85d63087cbc026a03525dcc5d491e900913e0ad6e2b09a6dd8eb27f392c60a8/apache/cloudstack/pull/5682
> > >> ]
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> On Sun, Jan 2, 2022 at 11:55 PM Hean Seng >
> > wrote:
> > >>
> > >> > Hi
> > >> >
> > >> > I am using Cloudstack 4.16 , Ubuntu 20 for Mgmt server.
> > >> >
> > >> > Infrastructure ->. Summary -> SSL Certification
> > >> >
> > >> > Entering all the SSL detail, and click submit , but the
> > click has
> > >> no
> > >>
Re: Cloudstack 4.16 - GUI unable to submit SSL
Hi,
I could see a related issue created here
https://github.com/apache/cloudstack/issues/5634
If you have the similar issue with Letsencrypt certs, you add more details
there. Otherwise, please create a new issue with the details.
Regards,
Suresh
On 08/01/22, 11:59 AM, "Hean Seng" wrote:
hi. Suresh
I am gemnerating Letsenctyp and instll the cert using the API .
I running.time as show in the shapeblue document. It successfully running
the API
"customcertificate": {
"message": "Certificate has been successfully updated, if its the
server certificate we would reboot all running console proxy VMs and
secondary storage VMs to propagate the new certificate, please give a few
minutes for console access and storage services service to be up and
working again"
}
}
running 2time, first time is chain + root
second time is cert. perm and privatekey pkcs8
after upload, destroy and let it rebuild the console proxy , after all
up, it seems https://ip-.domain in console cannot load as expected
On Wed, Jan 5, 2022 at 8:12 PM Suresh Anaparti <
suresh.anapa...@shapeblue.com> wrote:
> Hi,
>
> You can check the certificate configuration process through API/cmk here:
> https://www.shapeblue.com/securing-cloudstack-4-11-with-https-tls/
>
>
> Regards,
> Suresh
>
> On 05/01/22, 4:55 PM, "Hean Seng" wrote:
>
> Any body know how to use the API to upload this cert for console
proxy,
> Otherwise this 4.16 is not workable . This function seems no
> alternative to make it work
>
>
>
>
> On Mon, Jan 3, 2022 at 4:08 PM Hean Seng wrote:
>
> > Is there anyway to manual update it before 4.16.1 release ,
> otherwise the
> > SSL cannot be install.
> >
> > On Mon, Jan 3, 2022 at 3:06 PM Suresh Anaparti <
> > suresh.anapa...@shapeblue.com> wrote:
> >
> >> Good, thanks for the update Pearl!
> >>
> >>
> >> Regards,
> >> Suresh
> >>
> >> On 03/01/22, 12:31 PM, "Pearl d'Silva"
> >> wrote:
> >>
> >> Hi,
> >>
> >> This seems to be an issue in 4.16.0 but has been addressed
with:
> >> https://github.com/apache/cloudstack/pull/5682/ and should be
> available
> >> in 4.16.1.
> >>
> >> Thanks,
> >> Pearl
> >>
> >> [
> >>
>
https://opengraph.githubassets.com/a85d63087cbc026a03525dcc5d491e900913e0ad6e2b09a6dd8eb27f392c60a8/apache/cloudstack/pull/5682
> >> ]
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> On Sun, Jan 2, 2022 at 11:55 PM Hean Seng
> wrote:
> >>
> >> > Hi
> >> >
> >> > I am using Cloudstack 4.16 , Ubuntu 20 for Mgmt server.
> >> >
> >> > Infrastructure ->. Summary -> SSL Certification
> >> >
> >> > Entering all the SSL detail, and click submit , but the
> click has
> >> no
> >> > responding .
> >> > Clecking the MGMT log, and nothing seems processed .
> >> >
> >> > Tried on both Chrome, Safari and same issue .
> >> > Tried the same SSL to Cloudstack 4.15 , and it has no issue
> >> submitting the
> >> > SSL
> >> >
> >> > Anybody facing the same issue ?
> >> >
> >> >
> >> > --
> >> > Regards,
> >> > Hean Seng
> >> >
> >>
> >> --
> >> This message is intended only for the use of the individual or
> entity
> >> to
>
Re: Fix Policy Based Routing for private gateway static routes
Hi Vivek, If you have configured the ACL list of private gateway and the issue still exists, could you file an issue on github ? -Wei On Mon, 10 Jan 2022 at 09:00, Vivek Kumar wrote: > PG is configured with default_allow ACL policy, no custom policy is > applied. > > > Vivek Kumar > Sr. Manager - Cloud & DevOps > IndiQus Technologies > 24*7 O +91 11 4055 1411 | M +91 7503460090 > www.indiqus.com > > > > On 10-Jan-2022, at 1:17 PM, Wei ZHOU wrote: > > > > Hi Vivek, > > > > Could you please configure an ACL list (e.g. default_allow) on the > private > > gateway ? > > > > -Wei > > > > On Mon, 10 Jan 2022 at 04:29, Vivek Kumar .invalid> > > wrote: > > > >> Hey Wei, > >> > >> No PG doesn’t have any ACS rules. > >> > >> > >> Vivek Kumar > >> Sr. Manager - Cloud & DevOps > >> IndiQus Technologies > >> 24*7 O +91 11 4055 1411 | M +91 7503460090 > >> www.indiqus.com > >> > >> > >>> On 09-Jan-2022, at 6:20 PM, Wei ZHOU wrote: > >>> > >>> Hi Vivek, > >>> > >>> Does the private gateway have any ACL rule ? > >>> > >>> -Wei > >>> > >>> On Sun, 9 Jan 2022 at 07:07, Vivek Kumar >> .invalid> > >>> wrote: > >>> > Hello Folks, > > Below issue was supposed to be fixed after 4.13 but looks like it’s > >> still > there is current release. I have faced this issue in 4.15.2 > > https://github.com/apache/cloudstack/pull/3604 < > https://github.com/apache/cloudstack/pull/3604> > > > > Vivek Kumar > Sr. Manager - Cloud & DevOps > IndiQus Technologies > 24*7 O +91 11 4055 1411 | M +91 7503460090 > www.indiqus.com > > > > -- > This message is intended only for the use of the individual or entity > to > which it is addressed and may contain confidential and/or privileged > information. If you are not the intended recipient, please delete the > original message and any copy of it from your computer system. You are > hereby notified that any dissemination, distribution or copying of > this > communication is strictly prohibited unless proper authorization has > >> been > obtained for such action. If you have received this communication in > error, > please notify the sender immediately. Although IndiQus attempts to > sweep > e-mail and attachments for viruses, it does not guarantee that both > are > virus-free and accepts no liability for any damage sustained as a > result > of > viruses. > > >> > >> > >> -- > >> This message is intended only for the use of the individual or entity to > >> which it is addressed and may contain confidential and/or privileged > >> information. If you are not the intended recipient, please delete the > >> original message and any copy of it from your computer system. You are > >> hereby notified that any dissemination, distribution or copying of this > >> communication is strictly prohibited unless proper authorization has > been > >> obtained for such action. If you have received this communication in > >> error, > >> please notify the sender immediately. Although IndiQus attempts to sweep > >> e-mail and attachments for viruses, it does not guarantee that both are > >> virus-free and accepts no liability for any damage sustained as a result > >> of > >> viruses. > >> > > > -- > This message is intended only for the use of the individual or entity to > which it is addressed and may contain confidential and/or privileged > information. If you are not the intended recipient, please delete the > original message and any copy of it from your computer system. You are > hereby notified that any dissemination, distribution or copying of this > communication is strictly prohibited unless proper authorization has been > obtained for such action. If you have received this communication in > error, > please notify the sender immediately. Although IndiQus attempts to sweep > e-mail and attachments for viruses, it does not guarantee that both are > virus-free and accepts no liability for any damage sustained as a result > of > viruses. >
Re: Fix Policy Based Routing for private gateway static routes
PG is configured with default_allow ACL policy, no custom policy is applied. Vivek Kumar Sr. Manager - Cloud & DevOps IndiQus Technologies 24*7 O +91 11 4055 1411 | M +91 7503460090 www.indiqus.com > On 10-Jan-2022, at 1:17 PM, Wei ZHOU wrote: > > Hi Vivek, > > Could you please configure an ACL list (e.g. default_allow) on the private > gateway ? > > -Wei > > On Mon, 10 Jan 2022 at 04:29, Vivek Kumar > wrote: > >> Hey Wei, >> >> No PG doesn’t have any ACS rules. >> >> >> Vivek Kumar >> Sr. Manager - Cloud & DevOps >> IndiQus Technologies >> 24*7 O +91 11 4055 1411 | M +91 7503460090 >> www.indiqus.com >> >> >>> On 09-Jan-2022, at 6:20 PM, Wei ZHOU wrote: >>> >>> Hi Vivek, >>> >>> Does the private gateway have any ACL rule ? >>> >>> -Wei >>> >>> On Sun, 9 Jan 2022 at 07:07, Vivek Kumar > .invalid> >>> wrote: >>> Hello Folks, Below issue was supposed to be fixed after 4.13 but looks like it’s >> still there is current release. I have faced this issue in 4.15.2 https://github.com/apache/cloudstack/pull/3604 < https://github.com/apache/cloudstack/pull/3604> Vivek Kumar Sr. Manager - Cloud & DevOps IndiQus Technologies 24*7 O +91 11 4055 1411 | M +91 7503460090 www.indiqus.com -- This message is intended only for the use of the individual or entity to which it is addressed and may contain confidential and/or privileged information. If you are not the intended recipient, please delete the original message and any copy of it from your computer system. You are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited unless proper authorization has >> been obtained for such action. If you have received this communication in error, please notify the sender immediately. Although IndiQus attempts to sweep e-mail and attachments for viruses, it does not guarantee that both are virus-free and accepts no liability for any damage sustained as a result of viruses. >> >> >> -- >> This message is intended only for the use of the individual or entity to >> which it is addressed and may contain confidential and/or privileged >> information. If you are not the intended recipient, please delete the >> original message and any copy of it from your computer system. You are >> hereby notified that any dissemination, distribution or copying of this >> communication is strictly prohibited unless proper authorization has been >> obtained for such action. If you have received this communication in >> error, >> please notify the sender immediately. Although IndiQus attempts to sweep >> e-mail and attachments for viruses, it does not guarantee that both are >> virus-free and accepts no liability for any damage sustained as a result >> of >> viruses. >> -- This message is intended only for the use of the individual or entity to which it is addressed and may contain confidential and/or privileged information. If you are not the intended recipient, please delete the original message and any copy of it from your computer system. You are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited unless proper authorization has been obtained for such action. If you have received this communication in error, please notify the sender immediately. Although IndiQus attempts to sweep e-mail and attachments for viruses, it does not guarantee that both are virus-free and accepts no liability for any damage sustained as a result of viruses.
