-
Beta Was this translation helpful? Give feedback.
Replies: 4 comments
-
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 information provided, it seems that the Immich widget within Homepage is functioning correctly and displaying the correct statistics, but the container logs are showing HTTP 404 errors when calling the old Immich API endpoint The error logs indicate that the system is still attempting to access the old endpoint, which no longer exists after the Immich update that changed the endpoint to The component.jsx of the Immich widget seems to have a version check to determine which endpoint to use, but despite your Immich server version being beyond v0.100, the logs suggest that the old endpoint is still being called. To resolve this issue, please ensure that you are using the latest version of the Homepage that includes the fix for the Immich widget endpoint. If you are already on the latest version, it's possible that there might be a caching issue or a problem with the version check logic in the widget. You can try the following steps to troubleshoot further:
If you need further assistance, you can also use the Homepage AI Bot for support by hitting the 'Ask AI' button on any page in the Homepage docs, opening a GitHub discussion, or checking out the #ai-support channel on Discord. This comment was generated by Glime. |
Beta Was this translation helpful? Give feedback.
-
This comes down to the time period before the version call has returned, during which that check is false. Its annoying but not that obvious how to solve unless we just add another option to the config, which would be fine I suppose |
Beta Was this translation helpful? Give feedback.
-
This discussion has been automatically closed because it was marked as answered. See our contributing guidelines for more details. |
Beta Was this translation helpful? Give feedback.
-
This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details. |
Beta Was this translation helpful? Give feedback.
This comes down to the time period before the version call has returned, during which that check is false. Its annoying but not that obvious how to solve unless we just add another option to the config, which would be fine I suppose