Nextcloud with Letsencrypt using OMV and docker-compose - Q&A

Zitat von Agricola

All of this is because of how I started this journey in the OMV4 days with that pair of Nextcloud videos by TechnoDadLife. That is how he set up the conf files. I am just now getting my head around the wildcard method and sub.subdomains. That and KM0201 ’s posts above have me itching to try a paid domain without duckdns. As you say, with the wildcard method there is no limit to the number of sub.subdomains. I didn’t take your post as “the right way” or “my way” at all. I enjoy seeing the different approaches. They make me think. In fact I do think you guys have a superior way of subdomain layout so that you have one domain preceded with nextcloud. airsonic. ubooquity. Navidrome. etc.

If you don't use a generic top level domain (.com, .net, .org, and so on..) and you do don't pay for all their extras.. they are quite cheap. I got mine through domain.com. I used .xyz for the top level ( "mydomain.xyz").. and after declining all the stuff they try to upsell you (whois guard, SSL encryption, storage to host the website, and lots of other stuff), it was $3 for a year. If you don't pay attention you'll have about $100 in your cart when you go to check out. Delete all that and just get your domain for 1yr... and it's almost nothing to try if it's something that interests you.

Zitat von KM0201

it was $3 for a year

Did you check the cost for the second year?

Zitat von macom

Did you check the cost for the second year?

I think it was like $14, but this is a hobby project.. if they jack the price way up, I'll just register a new, cheaper domain... no big deal to me. Namecheap had tons of TLD suggestions that were as low as $2 for a year

Zitat von Soma

This way, how one would set the SWAG environment?

Code

  swag:
    environment:
      - PUID=1000
      - PGID=100
      - TZ=Europe/Lisbon
      - URL=mydomain.xyz
      - SUBDOMAINS=nextcloud,motioneye,bitwarden,etc
      - VALIDATION=http
#      - DUCKDNSTOKEN=xxxxxxxxxxxxxxxxxx
      - EMAIL=xxxxx@gmail.com

without the token of course, but yes. You also need www as a subdomain I think (I have it, that takes me to the swag park site). You could wildcard it and probably avoid adding all those subdomains, and just make sure your CNAME's are setup, and you'll be good

Zitat von Morlan

You don’t need www.

In the CNAME? Could've swore I read that was required... it may not be required though.

In the docker-compose.. No, probably not... but if you're having problems getting setup that's where the swag Success/Welcome screen is parked (http://www.yourdomain.xyz), so if it works, the proxy is working... so it's a good test.

Zitat von Soma

This way, how one would set the SWAG environment?

Code

  swag: 
    environment: 
      - PUID=1000 
      - PGID=100 
      - TZ=Europe/Lisbon 
      - URL=mydomain.xyz 
      - SUBDOMAINS=nextcloud,motioneye,bitwarden,etc 
      - VALIDATION=http 
#      - DUCKDNSTOKEN=xxxxxxxxxxxxxxxxxx 
      - EMAIL=xxxxx@gmail.com

I scratched my head at the duckdns line then I saw you had it commented out. I don’t know when, but I’m going to try this. I already have a domain name bought, but I don’t want to mess with a perfectly good Nextcloud install. Great snippet of code Soma .

Zitat von Agricola

I scratched my head at the duckdns line then I saw you had it commented out. I don’t know when, but I’m going to try this. I already have a domain name bought, but I don’t want to mess with a perfectly good Nextcloud install. Great snippet of code Soma .

When I got duckdns working again, I was a little ambivalent about trying this again and screwing up what was working... so it was really pretty easy to do w/o messing with my current nextcloud install.

I always have a virtualbox install for testing things, etc. Main thing is to make sure it's calling for it's own IP from the router (which is easy).

So I purchased my domain, logged in to my router, and all the ports that were forwarded for nextcloud to my server, I changed them and forwarded them to my virtual install. Some routers won't let you change IP's on these, and you have to delete the rule and create a new one (my old router you could, this one you can't), so I just took a screenshot of the port forwarding page and saved it. Deleted my forward ports for nextcloud to my server IP, and created them again, but pointed them at my virtual install.

Then I just took my stack from my server install, modified the volumes and other things relating to my domain.. and ran it on the virtual install. Made sure it all worked .

When it did and I saw how easy it was, I shutdown the virtual machine, went back to the router and changed my rules back to how they were originally. Deleted the nextcloud.subdomain.conf and made a new one from the .sample. Also went ahead and modified the config.php (backup your old one) with my new domains, etc. as presented in this thread Finally, I modified the swag portion of my stack and deployed.

It sounds more complicated than it actually was... but it was incredibly easy.

Did you execute the upgrade from (the app GUI) Nextcloud’s Settings/Overview tab, and if so, did you remove the file /config/nginx/site-confs/default before starting the upgrade? The upgrade will generate a new one.

Zitat von Andifront

Hi Agricola,

I made the upgrade from CLI (Solution 2 from this How-To)

After your hint I nevertheless tried the upgrade with deleting the mentioned file before. Same result.

Didn't Soma post something earlier in this thread about about an upcoming compatibility issue with Mariadb, if you weren't updated there earlier? I'm on 21.0.1.1 w/o issue.

What version of mariadb are you on?

I guess you could redeploy docker compose. There is an upgrade section farther down in the linuxserver/Nextcloud documentation.