Hey y'all!
I'm very new to OMV and hosting media in general. In the good 'ole days I used to watch my movies on my computer by myself, but now that I've got a family I decided to dabble in hosting my own media.
I'm on a fresh install of OMV4 with Docker - I have 3 containers; Jellyfin, Deluge and Docker.
Jellyfin is working like a dream on LAN (I'm highly recommending it if you haven't tried it out) -- but I'd like to share my library with a few friends as well (over WAN).
So to do this, I tried setting up Nginx and Traefik and another service which I can't remember what's called, but they were all too complicated for a beginner like myself, without any step-by-step guide on YouTube for me to follow. I spend around 5 days reading documentation and reinstalled OMV at least 8 times - to no avail.
After reading around on reddit.com/r/jellyfin I found out that Caddy is supposedly much easier than using the services previously mentioned - and I was relieved with the thought that I might actually be able to pull this off.
So here we go -- I'll try to write it as best as I can remember and add the logs that I know of.
The Domain
- First of all I read that Caddy does not work with DuckDNS, so I bought a domain from Namecheap (the domain extension was .casa so it didn't cost an arm and a leg).
- I moved the name servers of mydomain.casa to Cloudflare.
- Then I added a "record" in Cloudflare's DNS management tab - this was an "A record" where sub.domain.casa pointed to my WANIP:8096 (for Jellyfin).
The Container
- I went ahead and grabbed the abiosoft/caddy container in Docker.
- I set it up with these variables.
- Created a file using Sublime Text containing
and saved it as Caddyfile (without an .extention like .conf or .txt)
4. I then moved said Caddyfile to /etc/
Where It Fails
After running the container I can access 192.168.1.120:2015 -- where I'm greeted by a Caddy "FTP-like" interface.
The Caddy container log is returning this,
Activating privacy features... done.
2019/08/21 23:38:23 [INFO][cache:0xc0001ca190] Started certificate maintenance routine
Serving HTTP on port 2015
http://0.0.0.0:2015
2019/08/21 23:38:23 [INFO] Serving http://0.0.0.0:2015
2019/08/21 23:38:24 [NOTICE] Sending telemetry: we were too early; waiting 20h40m13.892845682s before trying again
2019/08/21 23:46:33 [INFO] SIGTERM: Shutting down servers then terminating
2019/08/21 23:46:33 [INFO][cache:0xc0001ca190] Stopped certificate maintenance routine
Alles anzeigen
Accessing mydomain.casa with any sub.domain combo isn't working, just a "host-error" Cloudflare landing page.
Honestly guys. I feel really stupid. I've tried so hard. I've fallen asleep in my chair reading documentation on all of these services. To put it mildly; I'm frustrated.
If I had an inkling of what i was doing wrong I'd try it out immediately, but the problem is I don't even have that, so I don't know where to begin.
Thanks in advance guys.