# Swagger-ui not loading

**URL:** <https://meta.akkoma.dev/t/swagger-ui-not-loading/728>\
**Category:** Uncategorized\
**Created:** [22 May 2024 17:09 UTC](https://meta.akkoma.dev/t/swagger-ui-not-loading/728 "2024-05-22T17:09:40Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![diogenes](https://meta.akkoma.dev/letter_avatar_proxy/v4/letter/d/e47c2d/32.png) [@diogenes](https://meta.akkoma.dev/u/diogenes)\
**Post date:** [22 May 2024 17:09 UTC](https://meta.akkoma.dev/t/swagger-ui-not-loading/728/1 "2024-05-22T17:09:40Z")

</div>

Trying the route /akkoma/swaggerui/ does not show swagger-ui

Installation:  
`./docker-resources/manage.sh mix pleroma.frontend install swagger-ui --ref stable`

 ![image](https://meta-uploads.akkoma.dev/original/1X/f6a5d3def091b3c5ed82d9da621d68b0c9d921fe.png)

Admin-FE config:

 ![image](https://meta-uploads.akkoma.dev/original/1X/6a5ef17c7efa99f555f1791f9fb2c097cf1b208d.png)

Admin-Fe frontends:

 ![image](https://meta-uploads.akkoma.dev/original/1X/eece2f5a696c5392dfb503b9cd170fd89bfa7b02.png)

Please help me troubleshooting. I am using the docker installation.

---

<div class="post-metadata">

**Author:** ![ilja](https://meta.akkoma.dev/user_avatar/meta.akkoma.dev/ilja/32/146_2.png) [@ilja](https://meta.akkoma.dev/u/ilja)\
**Post date:** [22 May 2024 19:20 UTC](https://meta.akkoma.dev/t/swagger-ui-not-loading/728/2 "2024-05-22T19:20:32Z")

</div>

the endpoint isn’t working any more for some reason, see comment [Newbie wuestion: how to view complete list of endpoints supported by Akkoma 3.5.0? - #9 by ilja](https://meta.akkoma.dev/t/newbie-wuestion-how-to-view-complete-list-of-endpoints-supported-by-akkoma-3-5-0/269/9)

---

<div class="post-metadata">

**Author:** ![diogenes](https://meta.akkoma.dev/letter_avatar_proxy/v4/letter/d/e47c2d/32.png) [@diogenes](https://meta.akkoma.dev/u/diogenes)\
**Post date:** [22 May 2024 20:00 UTC](https://meta.akkoma.dev/t/swagger-ui-not-loading/728/3 "2024-05-22T20:00:11Z")

</div>

Thanks! At least it works using the FE Picker. That’s something 🙂

---

<div class="post-metadata">

**Author:** ![Oneric](https://meta.akkoma.dev/letter_avatar_proxy/v4/letter/o/a9a28c/32.png) [@Oneric](https://meta.akkoma.dev/u/Oneric)\
**Post date:** [22 May 2024 23:36 UTC](https://meta.akkoma.dev/t/swagger-ui-not-loading/728/4 "2024-05-22T23:36:48Z")

</div>

(now moved to the more fitting thread, sry)

From [the other thread](https://meta.akkoma.dev/t/newbie-wuestion-how-to-view-complete-list-of-endpoints-supported-by-akkoma-3-5-0/269/9)

> [@Newbie wuestion: how to view complete list of endpoints supported by Akkoma 3.5.0?](https://meta.akkoma.dev/t/newbie-wuestion-how-to-view-complete-list-of-endpoints-supported-by-akkoma-3-5-0/269/9):
>
> I’m not sure how to properly fix it, but I’ve been able to work around it, you can find it at [https://ilja.space/pleroma/swaggerui/](https://ilja.space/pleroma/swaggerui/) (note that you need to also use the last slash).
> 
> For anyone who can spend the time looking further into this problem, it seems that the `/akkoma` route isn’t properly used for some reason + it also seems to need a slash at the end (at least I have to when using the pleroma route, as I have done now). Here’s the diff I did to get it working on `/pleroma/swaggerui/`

The issue is `/akkoma` is an API route prefix, so the frontend plug skips over the request. Ironcially the thing which makes `/akkoma` an API prefix is the frontend picker browser UI added in [de64c6c](https://akkoma.dev/AkkomaGang/akkoma/commit/de64c6c54aaacc4123031f2e3d5bfb9fc9c517fe) while the preferred frontend override apparently (though no idea how) makes it accessible anyway?

---

<div class="post-metadata">

**Author:** ![diogenes](https://meta.akkoma.dev/letter_avatar_proxy/v4/letter/d/e47c2d/32.png) [@diogenes](https://meta.akkoma.dev/u/diogenes)\
**Post date:** [24 May 2024 01:03 UTC](https://meta.akkoma.dev/t/swagger-ui-not-loading/728/5 "2024-05-24T01:03:20Z")

</div>

Maybe instead of the route `/akkoma/swaggerui` we change it to `/swaggerui` at least would be no conflits, right?

---

<div class="post-metadata">

**Author:** ![ilja](https://meta.akkoma.dev/user_avatar/meta.akkoma.dev/ilja/32/146_2.png) [@ilja](https://meta.akkoma.dev/u/ilja)\
**Post date:** [29 May 2024 05:47 UTC](https://meta.akkoma.dev/t/swagger-ui-not-loading/728/6 "2024-05-29T05:47:42Z")

</div>

\*oma allows profiles to be fetched on `/<username>`, so adding something directly on the root will 100% cause conflicts there. Imo that’s a behaviour that should’ve never gotten in, but that’s another discussion (which also kinda relates to [#279 - Add /@\<username\> route - AkkomaGang/akkoma - Akkoma Development](https://akkoma.dev/AkkomaGang/akkoma/issues/279#issuecomment-6953) ).

---

<div class="post-metadata">

**Author:** ![diogenes](https://meta.akkoma.dev/letter_avatar_proxy/v4/letter/d/e47c2d/32.png) [@diogenes](https://meta.akkoma.dev/u/diogenes)\
**Post date:** [3 June 2024 06:04 UTC](https://meta.akkoma.dev/t/swagger-ui-not-loading/728/7 "2024-06-03T06:04:40Z")

</div>

Maybe the better solution is to use an subdomain for other FE?
