CAP Service returns 503 service unavailable when run through app router

[arunkrishnamoorthy1988]

I am learning CAP and i am struck with the following issue. Seeking community help to help me fix and learn. I created a CAP service (sample bookshop srv) and deployed the application to BTP. While executing the app router locally, i can see the data is fetched correctly and data is displayed in the UI5 application. But after deploying to BTP, when i run the app router i get the error, Service Unavailable.

the service call returns 503 service unavailable when executed through App router, and 401 unauthorized when running the service instance. I did not define any restriction in my CAP Service.

I tried deleting the services and deploy it again. I tried adding a role in the xs-security.json and assigned the role to my user. It did not work. I have attached the mta.yaml, xs-app.json, xs-security.json file. i appreciate if someone can help.

Thanks,

Arun K

mta.txt xs-app.txt xs-security.txt

[Epena]

Hello, perhaps it would help us to help you if you provided a repo with your code.

Regards.

[arunkrishnamoorthy1988]

Hi Edgar,

The code is in the repository link.

https://github.com/arunkrishnamoorthy/cap-local-auth-setup.git

Regards,
Arun K

[rgadirov]

This blog post is already old, but what helped me with the exact 503 message after deployment to BTP CF, even with App Router and correct setup was, that it looks for the destination not on subaccount upper level but within the CF Space and the service instance itself. So you have to specify the explicite destination for destination service instance in the corresponding UI. Afterwards, it can connect via destination and cloud connector.