Selfhosted

40246 readers

558 users here now

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
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Trouble running MediaCMS: “Server Error (500)” on logging in. (lemmy.ml)

submitted 7 months ago* (last edited 7 months ago) by Tiritibambix@lemmy.ml to c/selfhosted@lemmy.world

16 comments fedilink hide all child comments

Hey there!

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!

you are viewing a single comment's thread
view the rest of the comments

[–] N0x0n@lemmy.ml 2 points 7 months ago* (last edited 7 months ago) (2 children)

Here is something you can work on. You could try to mount your volumes as named volume as per this docker-compose file, so that docker takes care of permissions and ownership of the files.

If I understand it correctly you want to use an external drive or a drive partition ? You can't directly use those partitions as named volume. You can also mount a SAMBA/CIF mounted volume from your external drive/drive partition or NFS (read here).

Do not change this part in the docker-compose I shared above. This files needs to be located where It can find it.

    volumes:
      - ./deploy/docker/local_settings.py:/home/mediacms.io/mediacms/deploy/docker/local_settings.py

This is what I would give a try. Apart from that, I can't help you any further, maybe someone else would come up with a better idea :/.

This seems like a stupid permission issue ˆˆ'. Hope you will find your way arround !

[–] Tiritibambix@lemmy.ml 2 points 7 months ago

Okay so I tried again, but only changing port. It worked. I really wish I could figure out this permission issues and bond volumes. Thanks again for your help :)

[–] Tiritibambix@lemmy.ml 1 points 7 months ago

Still no luck, but thanks for trying :)