[bug] admin-fe redirects to pleroma-fe with missing timeline #385
Labels
No Label
approved, awaiting change
bug
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs docs
needs tests
not a bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#385
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Your setup
From source
Extra details
Arch Linux
Version
develop
4a78c431cfPostgreSQL version
14.5
What were you trying to do?
Migrated from Pleroma to Akkoma as per documentation but admin-fe was just showing pleroma-fe without a timeline.
Cloned a fresh Akkoma at
4a78c43, copied overprod.secret.exs, installed admin-fe withMIX_ENV=prod mix pleroma.frontend install admin-fe, and restarted.Sadly it did the same.
What did you expect to happen?
admin-fe to show as per previous Pleroma installation.
What actually happened?
Essentially the normal pleroma-fe but with the timeline missing.
Mildly inconvenient since now I can't do any configuration as it's all db-based.
Logs
No response
Severity
I cannot use it as easily as I'd like
Have you searched for this issue?
putting odds of 2/1 on your ref being wrong
try adding
--ref stableto the adminFE installation commandor if you had that already, use --ref develop
--stabledidn't work.But
--developdid do an installation, thanks!Unfortunately now it just puts "Request failed with status code 404 - Not implemented" over every admin page and leaves them essentially blank; e.g. the users page shows no users.
Presumably there's something I've not twiddled to enable this but the documentation doesn't mention anything else to do.
the flag isn't
--develop, it's--ref developbut that makes it simple, you're serving stable adminfe on a develop install, which is awkward to get out of
your easiest path out of this is to do the following:
then you should be able to access your admin-fe
once you've done that, i recommend changing the
refofadmin-fetodevelopso this doesn't happen againAh, sorry, I was just shorthanding - I promise I did the actual
--ref developon the command line.I can access it fine - it's just throwing 404 Not Implemented errors on every page and not giving me anything to actually admin.
Looking at the network requests, it seems that the
/api/inhttps://social.rjp.is/api/pleroma/admin/users?page=1&filters=local,activeis causing the 404. Double-checked my nginx proxy against the supplied one to make sure it's not something weird left over from Pleroma.Just really confusing.
the steps above are to remove the error, you have a version mismatch, as stated
I followed those steps. Just to be sure, I removed any trace of admin-fe from
instance/static/frontendsand ran those steps again.Specifically:
Restarted Akkoma just to be sure and I'm still getting the 404 Not Implemented errors all over the admin pages.
ok i just looked at your instance
you're still using pleroma's frontends, nothing has been updated to our builds
just
MIX_ENV=prod mix pleroma.config delete pleroma frontendsand reinstall the FEsAha, that worked. And I guess that also explains why the
--ref stabledidn't download because it was using the Pleroma git (via the database) to fetch instead of the Akkoma git.Thank you kindly. I'll try and make some time tomorrow for a documentation patch to highlight this for anyone else migrating from Pleroma.