unable to access the puppet status API after upgrade the PE from 2019.1.0 to 2019.5.0

[Vinay Korrapati]

Hi Team,

we are unable to access the puppet status API after upgrade the PE from 2019.1.0 to 2019.5.0.

uri:  http://<hostname>:8123/status/v1/services

getting: 502 bad gateway.

Port is opened and In PE Console node group,  in the puppet_enterprise::profile::console class, console_services_plaintext_status_enabled is true.

Followed the https://puppet.com/docs/pe/2019.5/status_api_authenticating.html, but no luck.

Appreciate your suggestions. 

Regards

Vinay

[Rebecca Robinson]

Hi Vinay,

Since this is PE, I would open a ticket with support. I do believe that was changed due to the following reasons and docs may also need to be updated. 

https://puppet.com/security/cve/CVE-2020-7943/

Regards,

Becca

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/03c26581-5561-4e73-99cd-0ea6653bed51o%40googlegroups.com.

[Vinay Korrapati]

Hi Rebecca,

Thanks for your response. Do we have any workaround or fix for this issue ? 

Regards

Vinay

On Thursday, July 16, 2020 at 5:30:31 PM UTC+5:30, Rebecca Robinson wrote:

Hi Vinay,

Since this is PE, I would open a ticket with support. I do believe that was changed due to the following reasons and docs may also need to be updated. 

https://puppet.com/security/cve/CVE-2020-7943/

Regards,

Becca

On Thu, Jul 16, 2020, 6:50 AM Vinay Korrapati <vina...@gmail.com> wrote:

Hi Team,

we are unable to access the puppet status API after upgrade the PE from 2019.1.0 to 2019.5.0.

uri:  http://<hostname>:8123/status/v1/services

getting: 502 bad gateway.

Port is opened and In PE Console node group,  in the puppet_enterprise::profile::console class, console_services_plaintext_status_enabled is true.

Followed the https://puppet.com/docs/pe/2019.5/status_api_authenticating.html, but no luck.

Appreciate your suggestions. 

Regards

Vinay

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to puppet...@googlegroups.com.

[Rebecca Robinson]

Hi Vinay,

This might help.  https://puppet.com/docs/pe/2019.5/release_notes_pe.html#resolved_issues_pe_x-5

Since this is Puppet Enterprise, you can reach out to support at https://support.puppet.com

To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/138fd7b3-b6ca-45f6-9188-8ce7d96c5c0do%40googlegroups.com.

[Vinay Korrapati]

Hi Rebecca,

As per the link, issue got resolved in 2019.5 version. But getting the 502 bad gateway error while accessing the status API.

wget http://<hostname>:8123/status/v1/services

--2020-07-16 13:35:44--  http://<hostname>:8123/status/v1/services

Resolving <hostname>(<hostname>)... 127.0.1.1

Connecting to <hostname> (<hostname>)|127.0.1.1|:8123... connected.

HTTP request sent, awaiting response... 502 Bad Gateway

2020-07-16 13:35:44 ERROR 502: Bad Gateway.

Regards

Vinay

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/138fd7b3-b6ca-45f6-9188-8ce7d96c5c0do%40googlegroups.com.