Unable to visit web frontend: UnicodeConversionError

Hi all,

First post on this forum: I’m Ruben :smiley:
I’ve been running akkoma since ~January on https://social.kedara.nl without issues.

Now, out of the blue, the web interface is not loading any more. I see the following via docker logs:

11:59:27.599 [error] #PID<0.1689.0> running Pleroma.Web.Endpoint (connection #PID<0.1688.0>, stream id 1) terminated
Server: 116.202.96.116:80 (http)
Request: GET /%C0
** (exit) an exception was raised:
    ** (UnicodeConversionError) incomplete encoding starting at <<192>>
        (elixir 1.15.4) lib/string.ex:2586: String.to_charlist/1
        (flake_id 0.1.0) lib/flake_id.ex:93: FlakeId.flake_id?/1
        (pleroma 3.15.2) lib/pleroma/user.ex:1237: Pleroma.User.get_cached_by_nickname_or_id/2
        (pleroma 3.15.2) lib/pleroma/web/fallback/redirect_controller.ex:27: Pleroma.Web.Fallback.RedirectController.redirector_with_meta/2
        (pleroma 3.15.2) lib/pleroma/web/fallback/redirect_controller.ex:5: Pleroma.Web.Fallback.RedirectController.action/2
        (pleroma 3.15.2) lib/pleroma/web/fallback/redirect_controller.ex:5: Pleroma.Web.Fallback.RedirectController.phoenix_controller_pipeline/2
        (phoenix 1.7.20) lib/phoenix/router.ex:484: Phoenix.Router.__call__/5
        (pleroma 3.15.2) lib/pleroma/web/endpoint.ex:5: Pleroma.Web.Endpoint.plug_builder_call/2

After restarting, I could acces the web frontend but got this error:

My version is v3.15.2

Any ideas what might cause this and how to fix it?

Thanks and best,
Ruben

Forgot to mention: API access via Moshidon seems to work fine.

I’m not sure what’s causing this to happen on your timeline instead of only on user profile pages, but you discovered a bug which should get fixed by #906 - deps: upgrade flake_id to fix crash - AkkomaGang/akkoma - Akkoma Development
Thanks for the report!

Moshidon and other MastoAPI apps shouldn’t be affected as API endpoints only ever deal with (valid) IDs, not freeform user handles

1 Like

Thank you for letting me know and great to hear it’s been fixed already. I’m pretty sure this is the cause, because my timeline started to function again. Probably because the problem post dropped off.
Have a nice day! ~ Ruben