Request failed with status code 503. Change logging level to debug your issue

[Mahmood99]

Hello everyone, I face this issue.

I followed this  https://github.com/SAP/open-ux-tools/tree/main/packages/deploy-tooling#configuration-with-logging-en...  and tried with log: 5 and verbose: true  in my ui5.yaml but it is the same.

ui5.yaml file

specVersion: "3.1"
metadata:
  name: logoutplugin
type: application
server:
  customMiddleware:
    - name: fiori-tools-proxy
      afterMiddleware: compression
      configuration:
        ignoreCertError: false # If set to true, certificate errors will be ignored. E.g. self-signed certificates will be accepted
        ui5:
          path:
            - /resources
            - /test-resources
          url: https://ui5.sap.com
    - name: fiori-tools-appreload
      afterMiddleware: compression
      configuration:
        port: 35729
        path: webapp
        delay: 300
    - name: fiori-tools-preview
      afterMiddleware: fiori-tools-appreload
      configuration:
        component: logoutplugin
        ui5Theme: sap_horizon

Have someone an idea to solve it? 

Thank You.

[jlong]

Hi,

 

Assuming your issue is related to an on-premise system, please refer to these guides;

 

https://github.com/SAP-samples/fiori-tools-samples/tree/main/misc/onpremise

 

https://ga.support.sap.com/dtp/viewer/index.html#/tree/3046/actions/45995:48363:53594:48366:52526

 

In most cases, HTTP 503 is cause by either SSL Certificates, local proxy blocking inbound requests from BTP or the virtual host defined is not exposing the correct paths. 

 

To enable debug there are a couple of ways;

 

1. Run the following command;

 

DEBUG=* npm run deploy

 

2. Update your ui5-deploy.yaml with verbose logging;

  customTasks:
    - name: deploy-to-abap
      afterTask: generateCachebusterInfo
      configuration:
        verbose: true<div>However, this wont provide much detail since its your SAP Cloud Connector logs that you need to review why its failing.<div>Hopefully the above guides provide some insight to your issue.<div>John</div></div></div>

[jlong]

Hi,

 

Assuming your issue is related to an on-premise system, please refer to these guides;

 

https://github.com/SAP-samples/fiori-tools-samples/tree/main/misc/onpremise

 

https://ga.support.sap.com/dtp/viewer/index.html#/tree/3046/actions/45995:48363:53594:48366:52526

 

In most cases, HTTP 503 is cause by either SSL Certificates, local proxy blocking inbound requests from BTP or the virtual host defined is not exposing the correct paths. 

 

To enable debug there are a couple of ways;

 

1. Run the following command;

 

DEBUG=* npm run deploy

 

2. Update your ui5-deploy.yaml with verbose logging;

  customTasks:
    - name: deploy-to-abap
      afterTask: generateCachebusterInfo
      configuration:
        verbose: true<div> <div>However, this wont provide much detail since its your SAP Cloud Connector logs that you need to review why its failing.<div>Hopefully the above guides provide some insight to your issue.<div>John</div></div></div></div>