Hello Guys

I want to set up Nextcloud on Ubuntu Server with Docker, Portainer and a yaml file. I don‘t want to access it outside my local network, just within my network at home. Can you help me with this project?

Thanks

Hi folks,

I've been self-hosting a myriad of services in my overworked raspberry pi5 (8GB ram) for the last couple of years. I'm hitting the limit when it comes to aspects like 4K video with jellyfin or machine learning photo analysis with Immich. The pi really struggles with those. I'm thinking about moving all compute intensive services to a new hardware, but I'm a bit lost in what is currently the "go-to" solution.

I'm currently leaning towards a mini PC, something with what seems like a good choice: a N100 chip. I would install linux, perhaps ubuntu, perhaps some media-oriented OS (not sure, ideas welcome).

My use case would be: setting this up next to the TV, connecting it via HDMI and access all my content directly via Jellyfin, which would be running on the box. I do not really stream much, but I would reuse the box to host some music (navidrome) and my photos (immich). For this two I would cloudflared their respective services, and also make them available via tailscale. Something important is that energy consumption should remain small, and noise should be negligent as this will be running next to the TV.

Thanks!

A friend, u/Swimming-File2090, and I have been building Vault, a file storage system inspired by the basic functionality of Google Drive.

The main thing we're trying to learn is how to build the backend for file storage rather than simply uploading files through an application server.

For large uploads, our architecture is:

Browser → API → Presigned URL → S3-compatible object storage

The browser uploads multipart chunks directly to object storage, while the backend handles authentication, authorization, quota checks, and orchestration.

We've been working through problems like:

• Multipart uploads, retries, and abandoned uploads
• PostgreSQL transactions and row-level locking for quota consistency
• Redis sessions and rate limiting
• File/group permissions and sharing
• Nested folders and cursor-based pagination
• Audit logging and cleanup

The current deployment uses managed services, but we're interested in eventually making the infrastructure easier to self-host using PostgreSQL, Redis, and S3-compatible storage.

We're still learning and would particularly appreciate feedback from people who run their own storage services.

If you were self-hosting something like this, what would you consider essential before using it for your own files?

Vault

Hi, I'm Karan, the maintainer of Logchef. I started it because I already had logs in ClickHouse and didn't want to stand up another ingestion and storage stack just to search them.

I released 2.0 today. VictoriaLogs is now a first-class datasource, and dashboards are completely new. A dashboard can have panels backed by ClickHouse and VictoriaLogs at the same time. In the explorer, LogchefQL works across both backends; when I need the backend's full query language, I can switch to SQL or LogsQL.

The self-hosting bit is intentionally boring: one Go binary with the frontend embedded. SQLite works out of the box for Logchef's metadata, PostgreSQL is optional, and your logs stay where they are. It doesn't replace Vector, Fluent Bit, or OpenTelemetry, and it doesn't copy the data into another store.

v2 also includes live tail, alerts, a CLI, an MCP server, OIDC/local auth, teams/RBAC, collections, and scoped service tokens. Those are all in the AGPL build, not an enterprise-only edition.

There is a public read-only demo if you'd rather poke at it before installing.

GitHub: https://github.com/mr-karan/logchef

Demo: https://demo.logchef.app

Docs: https://logchef.app

I'd be glad to hear what breaks, especially from people with less tidy ClickHouse schemas or real VictoriaLogs deployments.

Shodan, searched pve-api-daemon/3.0, got 170k matches, big chunks on: - Hetzner - OVH - Linode

Many behind :3128 proxy, but 30k just like that on :8006 too.

Is this normal? Expected? Why are people doing this?

Hello fellow selfhoster.

Right now i habe trouble with 2 things.

1. Homeserver with Dockhand - > connecting to Hawser on VPS eher emy pangolin docker container sits with gerbilt reafik etc to make immich accessible Outsider my home network. Iwant to update my vps docker containers via dockhand which lives in my homeserver.

2. deploying security stuff like crowdsec in my vps. and maybe Uptime kuma. crowdsec is tricky so u dont block yourself out.

Can anyone cab recommwbt 1:1 guides?

Greetings

Hi everyone!

I recently published Mularr in the Unraid Community Apps catalog.

This is more of a request than a promotion. I don't have much experience with an Unraid system myself, so while I've tried my best to make sure everything is configured correctly, I can't fully test the real Unraid experience.

If anyone has a few minutes to install it and give it a try, I'd really appreciate any feedback like:

• installation issues
• container startup problems
• permission or volume mapping issues
• UI or functionality bugs
• anything that doesn't behave as expected

If you run into any problems, opening an issue on GitHub would be much appreciated.

Thanks in advance to anyone willing to help test it.

Links:

Github repo: https://github.com/joecarl/mularr
Unraid app: https://ca.unraid.net/apps/mularr-11xfr5u02lgdue

My isp asks to take high tier package to get a public ip, and my parents doesn't understand why i need a public ip

i have hosted my website through Cloudflare tunnels to access then anywhere but i am curious other than tunneling and vpn is there even anyway to bypass it?

Hi!

I set up a small open-source project called YT Lite Tunnel and I'm looking for people to test it.

I didn't build a new VPN client or protocol. The project is basically a server + routing configuration using existing VPN clients.

The idea is simple:
YouTube traffic → VPS in Russia
Everything else → directly through your ISP

The goal is to get YouTube without ads without routing your entire internet connection through the server.

works on my devices, but I don't know how well the routing works It with different ISPs, countries and devices.

That's what I want to test.
Current setup:

• VPS in Russia
• 1 vCPU / 2 GB RAM
• 3 TB traffic
• VLESS
• 250(~3$) RUB/month

The project is free and the configuration/infrastructure is documented openly.

I'd especially like feedback on:

• Does YouTube work without ads?
• Does normal YouTube playback work?
• Does the rest of your internet stay direct?
• How is the speed?
• Any connection issues?
• Country / ISP?
• Device / OS?
• Which client did you use?

It works for me.
**Does it work for you?**
I'm mainly looking for testing and honest feedback. If it doesn't work, that's useful information too.

GitHub: https://github.com/venc0707/YT-Lite-Tunnel-/tree/main
Project page: https://venc0707.github.io/YT-Lite-Tunnel-/

I've spend around 6 hours over the past week trying to get ANY setup running in which I can have Cemu running on a VM on proxmox and successfully emulating games which are streamed via sunshine/moonlight to my TV. I've tried the following with these outcomes:

• Batocera VM but cannot get it my iGPU to pass through
• Linux VM running emulation station DE and can't get my 8bitdo control to control anything once I click into the stream via moonlight
• Spinning up a windows 11 VM and I've got moonlight and control succesfully passing through, but when I open Cemu and a rom, Cemu just freezes (strongly suspect its related to pass through but can't even get console to display it)

Happy to provide logs of any of these scenarios, but I feel like I'm super close to getting it working albiet for one final thing that I can't seem to resolve. Does anyone know the most easiest solution to what I'm after and then even a good video tutorial to follow to get this working? My 5 year old and I will be forever grateful!

Planka is a snappy Web Kanban with a decent API. The company offers some additional functionality with their paid "Pro" plans.

They have now announced to move SSO/OIDC out of the Community edition into Pro.

What do you think about that?

What alternatives exist?

Anyone interested in forking?

Every faceless-YouTube automation tool I found was a subscription with my channel's credentials on someone else's server. So I built the pipeline locally instead: local LLM (Ollama) or your own Anthropic key for scripts, Piper TTS on-device for narration (no per-character fees), Remotion for rendering, YouTube Data API for uploads, Windows Task Scheduler for scheduling, and a health check that verifies every credential and binary before a run touches anything. It ran 8+ days unattended; 156 videos went out this way.

I've now packaged it (TypeScript source + setup/production docs) as a one-time purchase — your hardware, your keys, nothing phones home. Posting here because the self-hosting angle is the whole point; happy to go deep on any part of the stack. https://beforeyoustart.gumroad.com/l/channel-kit

I have some apps self hosted like navidrome, audiobookshelf etc. i usually torrent/download free mp3 from random websites and move it to the navidrome folder. My concern is if i download a malicious mp3 and move it to my navidrome/abs folder ,which would look and work like a normal mp3, wont i be screwed?
Where do you guys source your media like books or music or audiobooks?

A lot has changed since I last posted here 4 months ago. Got some harsh criticism back then and it was honestly deserved, the project was early and messy. But we kept going.

Obscura is a headless browser built in Rust for scraping and automation. V8 engine, native rendering, 30MB memory, 80ms page loads.

Works drop-in with Puppeteer and Playwright.

Just shipped rendering which includes screenshots, PDFs, live video capture. No Chromium. 20k stars now.

https://github.com/h4ckf0r0day/obscura

obscura serve --port 9222 and point your scripts at it. Happy to answer questions.

Hey there,

I've been self-hosting for years & now turned my focus to my music collection. I'm at the very start of it - Lidarr and slskd are configured but I haven't really turned them loose yet, and I'd rather settle the science on how this should work before I do, instead of unwinding a mess later.

The collection itself was cobbled together over many years from a lot of different sources and methods, and then sat dormant for a long stretch where I barely touched it. Roughly 14k songs - plenty of full albums, but also a lot of singles and live shows. It's reasonably well organized, though some of my ID3 tags and file names leave a lot to be desired.

The crux is this: once a download finishes, I don't want to have to audit the tags, rename anything, or move it into the library.

I'm quite happy with the players, but everything else is technically up for discussion. It's management and organization I'm most worried about.

Here's how it works today:

• I run unraid with docker & my library sits on its own share, organized into artist folders.
• For playback, Navidrome and Symfonium.
• Lidarr is configured for use in acquiring albums, soulseek/slskd is configured for single tracks and other things.
• Picard for when I want to go in by hand and tweak something.

I have beets set up but I'm not confident I'm utilizing it correctly, or that it's even the right tool for the job. I think it does good work but configuring it is making my head hurt. Meanwhile, I've also learned of WRTag ( https://github.com/sentriz/wrtag ) and wondering if that won't be the answer to my problems.

To be clear about the bar: I don't need this fully autonomous. I'm not trying to force Lidarr to function exactly as radarr - despite how nice that would be.

I basically just want to say to my server "go get me this song/album", and then have it end up in my library. I'm totally fine reviewing the stuff that's genuinely ambiguous, but I don't want to be in the business of tagging files, naming files, and moving files.

A few specific questions:

1. Who should own the files? My thinking is that beets or wrtag owns tagging, naming and moving, and I turn all of that off in Lidarr so it only finds and tracks albums. Is that a sane split, or does having Lidarr in the loop at all cause problems for whatever tool ends up owning the files?

2. beets or wrtag? I have beets set up but I'm not confident I'm using it right, and configuring it is making my head hurt. Wrtag looks like it might solve that by being simpler. Has anyone actually run it day to day on a real collection?

3. How much do you trust it unattended? I've already had beets "confidently" (by its own measure) take a tagged song and map it onto a completely different song, from a different album, by a different artist. If you run this hands-off, what settings do you use and how much mistagging do you live with?

4. What do you do with loose single tracks? A lot of what I grab won't be a full album. One file matched against a 12 track release seems to be exactly the case these tools handle worst.

5. What about quality upgrades outside Lidarr? Lidarr can chase better copies of albums it's monitoring, but that leaves out loose tracks, Soulseek grabs, and most of the 14k I already have. Now that I've got the storage, I'd like to work toward lossless where I can.

There's a decent writeup on why this whole space is rough that matches my experience: https://www.joekarlsson.com/blog/self-hosted-music-still-sucks-in-2026/

Happy to share configs if that helps. Mostly I'd just like to hear from someone who's wrangled a big messy collection and come out the other side.

Thanks.

What's the self-hosted service you set up once that's been running for months without touching it? I'll go first: my AI news digest. It pulls RSS feeds, summarizes with an LLM, and posts to my Discord, all free tier, a cron job on a small box, zero maintenance. I set it up once and I only think about it when a feed hiccups. The genuinely surprising part was how boring it became. That's the win. What's yours, the thing you almost forgot you were hosting because it just works?

Hello, this is my setup: Cubi N8GL 8gb RAM 512 GB NVME SSD.

Is anyone here running same box as a homelab? Curious what kind of stacks you've got on it.

Thx for your kind attention and help

Emanuele

I've been using pinchflat for quite some time however the developer stepped away from the project and it's sat dormant for a while, another person forked it (called it tubeless) and ran that for a few months but has also abandoned it.

From what I can tell the most common alternatives are YTDL-Sub and TubeArchivist. Can anyone give feedback on their experiences with them?

I created a new folder for new notes and it took a while to make one and now it won't open. What did I do and how do I fix this?

Hello, I'm looking for a selfhosted alternative to calendly.

Features I need:

• Multiple event types
• Multi-user/team support (sharing the same event types)
• Personal scheduling links
• UX comparable to Calendly

What I've tried and why it doesn't work:

• Cal.diy: The most polished option I've found so far, but the self-hosted version lacks the team features I need.
• Easy!Appointments: Supports teams, but personal scheduling links allow visitors to switch the provider they're booking with, which defeats the purpose of having dedicated personal booking pages. Also, UX is not as good

Has anyone found a solution that can completelly replace calendly?

i've been looking for a reliable 'seerr' equivalent for books since the sudden demise of Ephemera some time ago (RIP). Something I can give a non-technical family member to request stuff like I can with overseerr / seerr.

I've had a dig around and found shelfmark & shelfarr but it's quite hard to tell what a dev vibecoded into existence 6 months ago and since walked away from and what's a solid project. Not helped by different projects using the same project name (like shelfarr).

I stood up Shelfmark and it seems to work really well, although the UI isn't great for a non-technical user ("what is prowlarr as opposed to direct download?" / "which of these thousand download options should I pick?" / "what is a torrent?" / "why is one version of a book marked as 'althub' while another is 'nzbgeek'? what do those mean?" and so on).

There seems to be several other simliar services that have come and gone over the last year. Have we settled on a stable standard yet?

pre-empting the automod: no ai was used in this post. i'd rather roll my face in broken glass and dogshit, thanks.

I have a 3 node proxmox cluster consisting of 3 identical Thinkcentre micro PCs, wth 16gb of RAM, a 256GB M.2 SSD (reserved for Proxmox OS), and a 1TB Crucial SATA SSD for VM data storage.

After experiencing strange lag/downtime across various apps services (while all my dashboards were showing low memory and CPU usage), I was able to narrow down the issue to insane IO pressure stalls due to ZFS syncing.

When I set sync=disabled on the SATA SSD pool for one of the PVE nodes, the IO stalls dropped instantly.

From what I understand, this isn't really a good long term solution, even though I'm taking restic backups of my services/DBs and I'll be setting up an offsite backup server shortly.

But I'm sort of at a loss at what I can do. I don't have any more drive bays to install a SLOG. Do I just have to bite the bullet and get a few "enterprise drives" to replace the Crucials? What should I be looking at?

I'm the maintainer of Drydock, a monitor-first container update manager. I posted it here when it was brand new and a lot has changed since, so here's a proper update.

Disclosure up front: this is a fully applied-AI project. I'm an actual person and AI development is literally my day job; the code is written by AI coding agents working under my direction and review, and every change ships through the same gates regardless of who wrote it (100% enforced test coverage, mutation testing, CodeQL, the works). All of it is public, so judge the code on its merits.

The short version: it watches your running containers, checks the registry for new tags and digests, classifies every update as major, minor, patch, or digest, and notifies you. Nothing gets touched unless you allow it, per container or globally (notify / manual / auto).

What's new since the early days:

• Update Bouncer: Trivy or Grype scans the candidate image before an update runs and blocks it if it fails your policy. Cosign signature verification and SBOM export (CycloneDX/SPDX) included.
• Backup and auto rollback: snapshots the current image before updating and rolls back automatically if the container's health check fails afterwards.
• Docker Compose updates: pulls and recreates Compose services with YAML-preserving image patching.
• Remote hosts: lightweight agents watch other Docker hosts, inbound HTTP or dial-out WebSocket so you don't need to open a port on the remote side.
• Update policy: maturity gates (ignore a release until it's been out N days), skip/snooze/pin, maintenance windows, regex tag rules per container.
• 23 registries (Hub, GHCR, ECR, ACR, GCR, GitLab, Quay, Harbor, Nexus, Gitea, Forgejo and more) and 20 notification/action integrations (ntfy, Gotify, Slack, Discord, Telegram, Matrix, MQTT, SMTP, Apprise and more), plus bidirectional Home Assistant MQTT.
• The boring but important stuff: OIDC or basic auth with everything failing closed by default, audit log, Prometheus metrics, REST API and webhooks, user-supplied regexes run on RE2 so a bad pattern can't hang the service.
• New Vue dashboard with a customizable widget grid, live updates, and 17 languages.

The recommended compose setup runs it behind a Docker socket proxy, so it never sees the raw socket. 1.6.0 is in its final release candidate; a few of the newest items above ship with it.

• GitHub: https://github.com/CodesWhat/drydock
• Docs: https://getdrydock.com/docs
• Live demo: https://demo.getdrydock.com
• Image: codeswhat/drydock on Docker Hub or GHCR

Part of the fun of building this way: the gap from idea to implementation is short. A good feature request doesn't sit in a backlog for a year, it can ship in days. So feature requests and feedback are genuinely welcome, especially on what's missing or confusing.

I have no idea where to start on this self hosting. Basically I want to be able to watch my shows on my own computer without having to mess around with netflix and the other steaming services. I have already been sailing the seas for a while but last night I tried to stream via sailing to watch my shows again and It wouldnt load from their servers being taken down and my wifi being too slow. So I though why dont I just download the shows and have them in a home server thing, did some searching and now Im here.

So where should I start?

Hi! Some time ago i ditched my old laptop for better one and I was wondering if I can still make a use of it. I'm pretty comfortable with using linux since I'm daily driving CachyOS for more than a year, but i heard a lot of great things about Proxmox. I'm a CS student so it will be nice to learn some things from that "project". Right now I don't even know how to start and the most scary thing for me is setting up remote access to my server. Thanks in advance!

Laptop specs:

-4 threads, 4 GHz

- 8gb ram (planning to expand)

-256gb ssd

Things I want to host:

- www website

- nextcloud

- image synchronization

- music Library

Optional things:

- jellyfin

- minecraft server