Version 5.0.6 gets 502 errors on all actions

[bserem]

Hello!

With version 5.0.6 (current latest) we can't issue any commands:

platform environment:info --environment dev enable_smtp false

                                                                                                                                                 
  [ServerException]                                                                                                                              
  Server error response [url] https://eu.platform.sh/api/projects/gpud3nq4vgqui [status code] 502 [reason phrase] Bad Gateway [message] Upstrea  
  m not found (this may be temporary) 

Same goes for ssh, db:dump and backup commands. They all trigger the same response to all of our team.

Version 5.0.0 does work

Thanks

[akalipetis]

Hey @bserem - converted this to a discussion, as it seems like a local misconfiguration - I'll create an issue if a bug comes out of the debugging process.

This seems to be related to your project's or user's local configuration.

Could you please share here the contents of the .platform/local/project.yaml file in your local repository? Also, what is the output of running the following command inside and outside of your project?

platform self:config | grep base_url

[bserem]

Hey @akalipetis

Here are the info you requested:

$ cat .platform/local/project.yaml -p
id: XXXXXX
host: eu.platform.sh
alias-group: XXXXXX

I redacted the alias, as it's the clients name, and the ID

$ platform self:config | grep base_url
    base_url: 'https://api.platform.sh'

Happy to help any way I can.

[pjcdawkins]

@bserem If you and your clients could change that eu.platform.sh to api.platform.sh then the project(s) should continue to work with the latest version (ahead of the proper fix in the next release via platformsh/legacy-cli#1392)

e.g.

sed -i 's/api.platform.sh/eu.platform.sh/' .platform/local/project.yaml

[pjcdawkins]

@bserem thanks for reporting this, @akalipetis and I chatted some more and it does actually seem like a bug / regression, which we should be able to fix via platformsh/legacy-cli#1392

[akalipetis]

@bserem the issue should be resolved in the CLI version 5.0.7

[bserem]

I confirm that things are smooth with 5.0.7

I'll let you know if I see anything strange. Thanks

[akalipetis]

Thanks, I'll go on and close this one.