Error when Kubernetes app is not running

[Helmchen-Lord]

Description

I have installed Homepage on my Truenas Scale server (Truecharts) and have configured my individual apps in services.yaml, which also run on the same server as Homepage. This works fine, but if one of the apps I have configured in services.yaml is not running, I can no longer access the Homepage website and only get the error "TypeError: u.status is undefined"

Here is an example from services.yaml

• Apps:
  • netdata:
    icon: netdata
    href: https://netdata.web.lan
    namespace: ix-netdata
    app: netdata
    widget:
    type: netdata
    url: https://netdata.web.lan

kubernetes.yaml: "mode: default"

It doesn't matter whether I define a widget for the app in the yaml or not.
Only the following error is written in the log, but it also occurs when all apps are running and the homepage is displayed correctly:

2024-05-15 18:13:15.123068+02:00[2024-05-15T16:13:15.122Z] [33mwarn[39m: Failed to update prerender cache for /en [Error: EROFS: read-only file system, open '/app/.next/server/pages/en.html'] { 2024-05-15 18:13:15.123122+02:00errno: -30, 2024-05-15 18:13:15.123130+02:00code: 'EROFS', 2024-05-15 18:13:15.123173+02:00syscall: 'open', 2024-05-15 18:13:15.123180+02:00path: '/app/.next/server/pages/en.html' 2024-05-15 18:13:15.123185+02:00}

homepage version

v0.8.13 (986a181, May 6, 2024)

Installation method

Other (please describe above)

Configuration

No response

Container Logs

No response

Browser Logs

Something went wrong.
TypeError: u.status is undefined

l@https://homepage.web.lan/_next/static/chunks/pages/index-13ff1c2d6f3e37ec.js:1:71550
div
div
li
M@https://homepage.web.lan/_next/static/chunks/pages/index-13ff1c2d6f3e37ec.js:1:36329
ul
J@https://homepage.web.lan/_next/static/chunks/pages/index-13ff1c2d6f3e37ec.js:1:40392
div
3980/L<@https://homepage.web.lan/_next/static/chunks/1486-4892647c2bdc88fd.js:1:78657
div
l@https://homepage.web.lan/_next/static/chunks/1486-4892647c2bdc88fd.js:1:107390
14614/k<@https://homepage.web.lan/_next/static/chunks/1486-4892647c2bdc88fd.js:1:96931
14614/M<@https://homepage.web.lan/_next/static/chunks/1486-4892647c2bdc88fd.js:1:95614
l@https://homepage.web.lan/_next/static/chunks/1486-4892647c2bdc88fd.js:1:107390
3980/C<@https://homepage.web.lan/_next/static/chunks/1486-4892647c2bdc88fd.js:1:76607
div
$@https://homepage.web.lan/_next/static/chunks/pages/index-13ff1c2d6f3e37ec.js:1:40892
div
div
ge@https://homepage.web.lan/_next/static/chunks/pages/index-13ff1c2d6f3e37ec.js:1:60240
n@https://homepage.web.lan/_next/static/chunks/pages/index-13ff1c2d6f3e37ec.js:1:17128
75182/Y<@https://homepage.web.lan/_next/static/chunks/pages/_app-b877b7641e51de94.js:1:90769
ve@https://homepage.web.lan/_next/static/chunks/pages/index-13ff1c2d6f3e37ec.js:1:58246
div
div
div
we@https://homepage.web.lan/_next/static/chunks/pages/index-13ff1c2d6f3e37ec.js:1:67874
a@https://homepage.web.lan/_next/static/chunks/pages/_app-b877b7641e51de94.js:1:16145
a@https://homepage.web.lan/_next/static/chunks/pages/_app-b877b7641e51de94.js:1:15788
s@https://homepage.web.lan/_next/static/chunks/pages/_app-b877b7641e51de94.js:1:16704
u@https://homepage.web.lan/_next/static/chunks/pages/_app-b877b7641e51de94.js:1:15216
75182/Y<@https://homepage.web.lan/_next/static/chunks/pages/_app-b877b7641e51de94.js:1:90769
90753/t.default<@https://homepage.web.lan/_next/static/chunks/pages/_app-b877b7641e51de94.js:1:14467
l@https://homepage.web.lan/_next/static/chunks/pages/_app-b877b7641e51de94.js:1:1248
n@https://homepage.web.lan/_next/static/chunks/pages/_app-b877b7641e51de94.js:1:5712
r@https://homepage.web.lan/_next/static/chunks/main-b752bfcc638d3cc1.js:1:6992
Y@https://homepage.web.lan/_next/static/chunks/main-b752bfcc638d3cc1.js:1:9236
ie@https://homepage.web.lan/_next/static/chunks/main-b752bfcc638d3cc1.js:1:11878

Troubleshooting

[glime-ai[bot]]

Thanks for posting a discussion about homepage here on GitHub. Homepage now uses a fancy new AI tool thanks to our friends at Glime, so the answer below is the AI bot's attempt to answer your question. If you feel it's sufficient you can mark the answer and close this post, otherwise feel free to leave it open of course!

Thanks for using Homepage! ❤️

---

Based on the error message "TypeError: u.status is undefined" and the provided context, it seems that the issue is related to the Homepage application trying to access a property of an undefined object. This typically happens when the application expects an object to be returned from an API call or a similar operation, but instead, it receives undefined, possibly because the service is not running or not reachable.

Given that the error occurs when one of the apps configured in services.yaml is not running, it's likely that the Homepage application is attempting to retrieve the status of the service and failing because it cannot establish a connection to the service's API or endpoint.

To troubleshoot this issue, you can follow these steps:

1. Ensure that all services listed in services.yaml are running and accessible from the Homepage application. If a service is down, Homepage might not be able to retrieve its status, leading to the error you're seeing.

2. Check the configuration of each service in services.yaml to ensure that the URLs and any other required parameters are correct. Incorrect configurations can prevent Homepage from communicating with the services.

3. Look at the Homepage container logs to see if there are any additional error messages that might indicate what's going wrong when trying to access the services.

4. If the issue persists, consider opening a GitHub issue or discussion on the Homepage repository to seek help from the developers or the community. Provide as much detail as possible, including the version of Homepage you're using, the installation method, and any relevant configuration files or logs.

Remember to check the documentation and any recent updates or changes that might affect how services are configured or interacted with in Homepage.

This comment was generated by Glime.

[shamoon]

Can you post a screenshot of what you see?

If youre going to have services dynamically going on / off, perhaps using annotations (I think basically equivalent to docker labels) might work better instead of using services.yaml.

[Helmchen-Lord]

Here is the output from the API call:
https://homepage.web.lan/api/kubernetes/status/ix-netdata/netdata
Error 404 "no pods found with namespace=ix-netdata and labelSelector=app.kubernetes.io/name=netdata"

If the app is running, "running" is returned.

Here are the configs as a zip file (I have changed the IPs, PW etc.):
Homepage.zip

[shamoon]

I cant exactly reproduce this, perhaps because Im not really running a k8s cluster to test against, so Im not certain where the error is arising. One last weird request, if you can look in the browser console at the error and click the location in the js file and send a screenshot of that, perhaps I can track it down.

[Helmchen-Lord]

I normally use Firefox on Fedora 40, but I tried to open Homepage on Chrome (Edge) and I got a different error:
TypeError: Cannot read properties of undefined (reading 'includes')

Here are the errors from Edge:

Is that what you mean?
Position highlighted in index-13ff1c2d6f3e37ec.js:

Or this in the framework-95233f837b560043.js:?

I can't really find the right location in Firefox.

[shamoon]

Aha yes I think thats helpful!

Ok, whenever you have a chance please try out the main image (i.e. not latest)

[Helmchen-Lord]

It seems to be working, thank you!
I can't test it 100% as I can't select the branch with Truecharts, so I had to create a custom app but that worked and offline apps are now shown as offline.

[github-actions[bot]]

This discussion has been automatically closed because it was marked as answered. See our contributing guidelines for more details.