Selfhosted

46146 readers

466 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 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Anyone else having linkding problems? (self.selfhosted)

submitted 4 weeks ago by drhoopoe to c/selfhosted@lemmy.world

4 comments fedilink hide all child comments

I've been running a docker-based linkding instance on one of my servers for a couple years now, using it with the linkding firefox extension, and it's been awesome. I'm still able to access the page and use it to go to links normally, but, as of yesterday, when I try to bookmark something with the extension it throws an "Internal Server Error" and fails to save it. Same thing happens when I try to add a bookmark "manually" via the linkding page.

I've restarted the docker instance and made sure the alpine VM it's on (via proxmox) is up to date, but to no avail. Other containers on the VM seem to be working fine. Portainer says the container is healthy. The full error message is "Error saving bookmark: Request error: Internal Server Error." Anyone had the same problem?

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

[–] Xanza@lemm.ee 3 points 4 weeks ago* (last edited 4 weeks ago) (1 children)

Everything seems fine with 1.39.1. What's the docker log say? Also which version?

[–] drhoopoe 9 points 4 weeks ago (1 children)

Thanks, but I'm an idiot. I dug around a little and realized I was low on disk space and running a badly outdated version. All good now.

[–] Xanza@lemm.ee 5 points 4 weeks ago (1 children)

bookmarks

low on disk space

Goddamn boy, how many links you got? A million? lol

[–] drhoopoe 1 points 3 weeks ago

Lol, a lot, but not that many. Mostly docker shit filling up /var from containers I'd tried running or run for a while and got bored of. Just needed a good docker prune -a --volumes.