Replies: 1 comment
-
|
Hi @kelince! I'm Dosu and I’m helping the dify team. This is a known issue with self-hosted Dify deployments. The trial app feature on the Explore page is disabled by default, and the featured apps displayed may reference apps that don't exist in your local database. To resolve this:
However, since you're getting a 404 (not 403), this indicates the app data doesn't exist in your local database - the featured apps on the Explore page are referencing apps that weren't seeded during your local installation. This appears to be a limitation of self-hosted deployments where trial/featured app data may not be properly initialized. The same issue has been reported recently by other users on v1.13.0. To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Self Checks
Content
Version: Dify 1.13.0
Environment: Local Docker on Windows
Error: 'App not found' when viewing app details in the Explore page.
I have locally installed Dify version 1.13.0 via Docker. When I select an application on the Explore page and click on its details, an 'App not found' error is displayed. How can I resolve this issue?
Error log:
Request URL
http://localhost/console/api/trial-apps/1cb0aaf8-018c-4aa1-97c3-f3b487e813e9
Request Method
GET
Status Code
404 NOT FOUND (from service worker)
Referrer Policy
strict-origin-when-cross-origin
Beta Was this translation helpful? Give feedback.
All reactions