# Error 500 when activating plugins (asset not found in the load path.)

**URL:** https://meta.discourse.org/t/error-500-when-activating-plugins-asset-not-found-in-the-load-path/397370
**Category:** Support
**Tags:** unsupported-install, hosting
**Created:** [March 1, 2026, 11:42am UTC](https://meta.discourse.org/t/error-500-when-activating-plugins-asset-not-found-in-the-load-path/397370 "2026-03-01T11:42:44Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![Jagster](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagster/32/192154_2.png) [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [March 1, 2026, 2:05pm UTC](https://meta.discourse.org/t/error-500-when-activating-plugins-asset-not-found-in-the-load-path/397370/2 "2026-03-01T14:05:25Z")

</div>

My **bet** is translator plugin is eithet broken or shouldn’t use anymore 🤷‍♂️ Do not use it in app.yml?

> [@Discourse Translator](https://meta.discourse.org/t/discourse-translator/32630/446):
>
> The Discourse AI provider on the translator plugin has been moved to Discourse AI itself. This simplifies configuration by a lot, and allows us to tap on Discourse AI’s LLM usage / persona functionalities. As for the functions moved to Discourse core, they were all experimental features that had been in heavy development from the beginning of this year. Our team has decided to conclude this experiment. It was a successful one and we are seeing many requests for first-class multilingual support. …

---

_[View the full topic](https://meta.discourse.org/t/error-500-when-activating-plugins-asset-not-found-in-the-load-path/397370)._