New 502 Bad Gateway on 2.0 Authorization?

[Peter Albrecht]

Hi everyone,

Last week, I successfully implemented the authorization and data retrieval process using the synthetic data in the CMS Blue Button sandbox. Everything was working smoothly.

However, yesterday and today, I started encountering a 502 Bad Gateway error during the authorization process. Specifically, after passing the synthetic credentials and reaching the confirmation screen, the error occurs when I click "connect."

From my server logs, it looks like the authorization sessions are going through without any issues, so I'm not sure if this is a problem on my end. I haven't made any changes to the code that was previously working—just trying to figure out if this might be an issue with the sandbox environment.

Has anyone else experienced this, or does anyone have any insights into what might be happening?

--Pete

[Max]

We are experiencing the same issue at the same authorization step.

Max.

[Developer Group for CMS Blue Button API]

Hello - 

We have reached out to Pete and Max individually and resolved their issues. However, if anyone encounters similar errors, please let us know by responding to this post or contacting us directly at BlueBu...@cms.hhs.gov.

Best,

The Blue Button 2.0 Team

[Peter Albrecht]

I wanted to reconnect on this because I am not sure if it was 100% resolved, or it may have returned.  

I still get a 502 Bad Gateway in my web browser but I do not get it if I do the entire process in an Incognito tab.  

My guess is something is stored in the cache and because I have done so many authorization tests there are some errors going on in the background.

Just bringing this back up in case someone has a solution.

--Pete

[Developer Group for CMS Blue Button API]

Hello Peter -

Thanks for flagging this, we will reach out to you individually to get more info on reproducing this issue. 

Best,

-The Blue Button 2.0 Team

[Michael Albrecht]

Hello, I'm encountering the 502 Bad Gateway error when doing the Postman test with the Client ID and Client Secret. 

-Michael

[Developer Group for CMS Blue Button API]

Hello - 

Thanks for flagging this, we will reach out to you individually to get more info on reproducing this issue. 

Best,

-The Blue Button 2.0 Team

[Developer Group for CMS Blue Button API]

Hi Everyone,

Our team has released a fix for the issue, which should resolve the errors that you reported. If you have any additional questions, please let us know, and thank you for your patience.

Best,

-The Blue Button 2.0 Team