Pleroma frontend: internal server error

Support apps
,
1

What type of hardware are you using: Other(?)
What YunoHost version are you running: 11.3.0
What app is this about: Pleroma

Describe your issue

When I try to use the pleroma instance frontend, I get:
{“errors”:{“detail”:“Internal server error”}}

Other clients work, so it seems to be a front-end only issue.

And yes: I DID mess with the frontend. I must have botched the installation of Mangane. But now I can’t access the frontend, nor the old admin-panel, all return “Internal server error”. Deleting the Mangane directory did not fix it.

Unfortunately, I couldn’t find any useful log other than that 500 code.

Share relevant logs or error messages

{my IPv6 address} - - [11/Nov/2024:03:50:44 +0000] “GET / HTTP/2.0” 500 45 “-” “Mozilla/5.0 (X11; Linux x86_64; rv:131.0) Gecko/20100101 Firefox/131.0”

2

Have you tried to turn back to default frontend?
If it’s the case, have you still the error?

3

Look at this doc, it can help… But in French.

In short :

sudo su pleroma -s $SHELL -lc "/var/www/pleroma/live/bin/pleroma_ctl frontend install mangane --ref dist --build-url https://github.com/BDX-town/Mangane/releases/latest/download/static.zip"

Done

4

That’s my issue: how do I get back to the default front-end?
The doc uses the admin FE to do so, but I can’t access that either.

5

Try to stop and restart Pleroma from the YNH admin…

6

You can also remove Mangane manualy from the CLI.

Command:

sudo rm -fr /home/yunohost.app/pleroma/static/frontends/mangane/

This does’nt modify Pleroma, just remove the Mangane files…

7

I tried both of the above (already tried restarting the service with systemctl before), still no luck.

8

Have you tried to visit your instance in private mode and/or do a ctrl-cap-R (to empty the cache of your browser?

9

Sooo! Not sure what did it but after a system upgrade (regular, not Yuno 12), I actually tried to access the old admin panel from a different browser (Chromium, usually I’m on FF), and it worked!

There, I saw that somewhat the default Pleroma-FE was proposed for… installation!!
I clicked “install”, and that fixed it!

What I think happened: after botching the Mangane installation, I must have accidentally deleted the default front-end, thus no way to recover it except from the admin panel. Access to the admin FE was not working but probably because of a cache issue.

I didn’t suspect the 2 would fail for a different reason, so I may have skipped some basic checks! But all in all, it was a cache issue, just not where I thought.

So thank you!

1 Like
10

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.