Skip to content

Troubleshooting entry for missing index page and "Cannot GET /" #2132

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.

Sign up for GitHub

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

Merged
merged 8 commits into from
Oct 9, 2025
Merged

Troubleshooting entry for missing index page and "Cannot GET /" #2132

Changes from all commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
6046fa9
Troubleshooting entry for "Cannot GET /"
swaldmann Oct 2, 2025
aaf75bd
Wording, links to Node and Java
chgeo Oct 7, 2025
69214f4
Note on health status
chgeo Oct 7, 2025
2482fc2
Merge remote-tracking branch 'origin/main'
chgeo Oct 7, 2025
c3fb533
Update get-started/troubleshooting.md
smahati Oct 7, 2025
602aaf6
Avoid redundant config keys
chgeo Oct 8, 2025
ad56097
Merge branch 'main' into ts-cannot-get
chgeo Oct 8, 2025
039e58f
Merge branch 'main' into ts-cannot-get
swaldmann Oct 9, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 10 additions & 2 deletions get-started/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -626,8 +626,7 @@ Now you can build the archive with:
mbt build -t gen --mtar mta.tar -e less.mtaext
```

::: warning
This approach is only recommended
::: warning Not recommended for production deployments
- For test deployments during _development_. For _production_ deployments, self-contained archives are preferrable.
- If all your dependencies are available in _public_ registries like npmjs.org or Maven Central. Dependencies from _corporate_ registries are not resolvable in this mode.
:::
Expand Down Expand Up @@ -768,7 +767,16 @@ If you receive an error response `404 Not Found: Requested route ('<route>') doe

:::

### Why do I get a _404 Cannot GET /_ error?

For security reasons, the **index page is not served in production** by default in both [Node.js](../node.js/cds-server#toggle-generic-index-page) and [Java](../java/developing-applications/configuring#production-profile).

If you try to access your backend URL, you will therefore see a _404 Cannot GET /_ error.
This also means you **cannot use the `/` path as a health status indicator**. See the [Health Checks guide](../guides/deployment/health-checks) for the correct paths.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sjvans I have added a note on the health status checks. Please augment if needed.


Only if absolutely required and you understand the security implications to your application, you can enable this page in your deployment.

Learn more about the generic index page in [Java](../java/developing-applications/properties#cds-indexPage) and in [Node.js](../node.js/cds-server#toggle-generic-index-page).{.learn-more}

## CAP on Kyma

Expand Down