Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

501 Bad Gateway on the Northwind Service #22

Closed
js1972 opened this issue Oct 30, 2020 · 8 comments
Closed

501 Bad Gateway on the Northwind Service #22

js1972 opened this issue Oct 30, 2020 · 8 comments

Comments

@js1972
Copy link
Contributor

js1972 commented Oct 30, 2020

Hi. I have used this sample (the fiori one) a few weeks ago and it was working fine. I am testing it again and have pulled the lastest master branch but it is unable to reach the OData service. the app fails with 502 Bad Gateway when it tries to read the $metadata. Any ideas?

I have created another test application using fiori-tools and connected it to the Northwind OData service. I notice that this does not work anymore either and gives certificate errors in the browser console unless I make this setting in the fiori-tools-proxy:

configuration:
        ignoreCertError: true

...in which case its starts working.

I'm wondering if something is wrong with the https://services.odata.org certificate. Are you able to run this app and fetch data ok today?

@IObert
Copy link
Contributor

IObert commented Oct 30, 2020

Hi,

this is really strange. Which sample are we talking about? I'll test it then.

@js1972
Copy link
Contributor Author

js1972 commented Oct 30, 2020

Sorry. It's the fiori one.

@IObert
Copy link
Contributor

IObert commented Oct 30, 2020

I just tested the managed Fiori app and you are right. It seems that the Northwind service currently has issues. You can also see that here: https://services.odata.org/V2/Northwind/Northwind.svc/

Screen Shot 2020-10-30 at 10 59 00

I'd assume Microsoft will fix this soon and therefore I wouldn't do a change in the repo now. But that's definitely worth having an eye on, thanks for bringing this up!

@IObert
Copy link
Contributor

IObert commented Oct 30, 2020

Seems like the issue has already been reported here: OData/odataorg.github.io#255

@js1972
Copy link
Contributor Author

js1972 commented Oct 30, 2020

Sap-managed fiori.

@js1972
Copy link
Contributor Author

js1972 commented Oct 30, 2020

I think it's a bad cert on the north wind service because it won't work when running locally unless I say ignore cert errors in the ui5.yaml file. So it seems the destination can't handle it though....

@js1972
Copy link
Contributor Author

js1972 commented Nov 2, 2020

Closing - Microsoft seem to have fixed the cert issue. Unfortunately when I go back through all the incidents for the service it seems that it regularly gets these issues. ;-(. This is the sort of thing that always happens when you are doing a demo of course!

Thanks for your help.

@js1972 js1972 closed this as completed Nov 2, 2020
@IObert
Copy link
Contributor

IObert commented Nov 2, 2020

I'm glad it's working again. Tip: You can also use the ES5 system in case you run into an issue with Northwind in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants