this post was submitted on 07 Jun 2026
18 points (90.9% liked)

Selfhosted

60543 readers
1220 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the link in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post. )

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
18
Caddy touble in Docker (lemmy.zip)
submitted 1 month ago by W3dd1e@lemmy.zip to c/selfhosted@lemmy.world
18 comments fedilink hide all child comments
 

Howdy! Sorry if this is a supid question. I've been trying to get this working for like 5 days and I've been researching and reading docs, but I'm just not getting it. I'm fairly new to selfhosing and I'm trying to set up Jellyfin remote access on my NAS. My NAS is a QNAP product running QTS (which I absolutely hate). QTS uses their own weird version of Docker.

When I start Caddy with a docker compose file, I get an error that port 443 is in use and the container can't be started. If I create a container in the Container Station app directly from the Docker Image, it starts up fine. Container Station handles environment variables in a dumb way so I am having trouble specifying the Caddyfile location when I do it that way.

Does anyone know why it works fine in that way but not the other? Both use port 443 but when I do it in a docker compose file, it says the port is in use but when I do it the other way, it doesn't and starts fine.

Note: I know you can do this with Tailscale also, but I want to use my custom domain to make it easier for sharing in the future.

you are viewing a single comment's thread
view the rest of the comments
[–] billwashere@lemmy.world 1 points 1 month ago (1 children)

This probably doesn’t help you much right now but I have a QNAP as well. And I too despise the QTS software. But I found out that TrueNAS can run on it pretty easily. I have an NVME drive on a usb-c enclosure that I installed trueNAS on and it boots fine into it. If I ever wanna go back it’s just a remove the boot drive and reformat (the ZFS pools are compatible unfortunately).

[–] W3dd1e@lemmy.zip 1 points 1 month ago (1 children)

Actually I’ve been strongly considering swapping the OS to TrueNAS but I’ve heard some people have trouble with getting the fans to work once they switched over. If you’ve had a good experience I’m willing to give it a shot.

[–] kylian0087@lemmy.dbzer0.com 2 points 1 month ago

Their is a driver to get fans working or at least usable. https://github.com/0xGiddi/qnap8528

To build the driver you usually have to enable Dev mode on truenas scale. I did not want to this so I made a container which can build the driver for you. This way you do not need to enable Dev mode and their for remove the write protection on the host OS. https://github.com/kylian-002/Truenas-qnap8528-module