I’m a self-hosting enthusiast, and I’m learning the hard way, so I appreciate your patience as I navigate through this.
I’ve been on the hunt for a video hosting solution that offers categories and tags, and I’ve heard great things about MediaCMS. It seems like the perfect fit for what I need.
After some trial and error, I finally got it up and running. The only hiccup I’m facing now is with logging into the admin panel. I keep getting an error 500. I checked out some similar issues on github, but it doesn’t seem to apply to my situation, and there isn’t a solution posted. Plus, it looks like the developer is not very active on the issues.
I was wondering if anyone else has encountered this problem before and might have some insights to share.
Here’s some additional info:
I cloned the repository from https://github.com/mediacms-io/mediacms and made some edits to the docker-compse.yaml file to suit my preferences, mainly adjusting the volume paths.
You can check it out here.
The service takes a bit of time to start, but eventually it does and I can access the landing page. However, when I try to sign in, I just get a “Server Error (500)” message.
I’ve checked the logs but haven’t found anything useful.
Has anyone who uses MediaCMS encountered this issue before?
Can someone reproduce and help me clear this out?
Thanks a lot for your assistance!
I have one container exited, mediacms_migrations, but I noticed it stopped right after the stack’s setup and thought it would be used only for startup.
Here are the logs for it
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
Thanks for your answer. I’m not sure what to look for in the browser’s logs but here it is.
I have logs for all containers here:
celery_beat
celery_worker
db. A lot of errors here, but I think I recall reading somewhere in the issues that it doesn’t matter. I’d have to double check that.
redis
web
I have one container exited,
mediacms_migrations, but I noticed it stopped right after the stack’s setup and thought it would be used only for startup. Here are the logs for itIt looks like db is fried, I’d assume all the permission errors prevent it from running normally. Is there a healthcheck configured?