search

davestephens / ansible-nas

Build a full-featured home server or NAS replacement with an Ubuntu box and this playbook.
MIT License
3.14k stars 477 forks source link

Update to Nextcloud 18 #239

Open ckoehler opened 4 years ago

ckoehler commented 4 years ago

Is there a reason we are still on 14?

ckoehler commented 4 years ago

I just upgraded from 14 through all major versions, one by one, to 18, and everything is still working fine.

codemeister64 commented 4 years ago

+1

allthestairs commented 4 years ago

I removed the version tag from Nextcloud back when 15 was the current version and have had successful automatic upgrades since then. If you believe in automatic Docker image updates and don't mind unpredictable upgrade timing you can enable automatic updates with something like Watchtower, remove the version tag and Nextcloud will (probably) handle upgrading itself fine as part of its startup process.

This is not a good default solution though, since there is no guarantee the next time someone re-creates the Nextcloud container that it won't skip two versions and fail the update process.

bcurran3 commented 4 years ago

I'm using the latest now as well. I think I tried to incremental upgrade to 15 and it was hosed, so I just deleted it all and reinstalled with latest. I wasn't using it as I didn't have Traefik and SSL up and running yet. Now that's done and I'm using :latest with no problems.

bcurran3 commented 4 years ago

v19 is the current version now: https://hub.docker.com/_/nextcloud

I'm pretty frustrated with NextCloud. The Windows client tries to auth forcibly on 443 (https://fqdn:443). This then fails because it hits traefik on 443. (I think, it's been months since I looked at this.) Using IP worked from what I remember but that's not a good solution when I'm not on my LAN.

(Technically this is an issue with the NextCloud Windows client and should be brought up to those devs, but I'm voicing my frustration here in hopes that there's some oversight on my part and maybe someone can share a solution to me on configuring traefik differently - maybe traefik 2.0 will solve the problem? I dunno.)

I've had great success and happiness with OwnCloud.

ckoehler commented 4 years ago

Hm seems to work for me, but I did also update to Traffic 2.

bcurran3 commented 4 years ago

Good to know. To verify: You're using the NextCloud Desktop Client (v3 was just released which still doesn't work for me).

Would love to get Traefik 2 running. I honestly thought it would be a higher priority and merged into Ansible-NAS by now. Maybe you could do a PR to add it? :)

ckoehler commented 4 years ago

Hm maybe not v3, but I am using the windows client. No issues.

Sorry, no PR. It’s a lot of work to change all the labels and I only changed the ones I actually use.

bcurran3 commented 4 years ago

Later versions of 2.x or v3, doesn't matter - neither work for me. :(

Understood and thanks.

EDIT: Did you have it working with Traefik 1.7? Also maybe you could past in your yml file or the Traefik labels and I might be able to run with that as a start for converting to 2.0 without having to spend hours reading. (My brain works very well with working template examples and slows down considerably when it has to read pages of documentation.) :)

No rush! No pressure. I'm not jumping on this right away.

ckoehler commented 4 years ago

Well, thinking about it, I am actually forwarding both 443 and 80 to my server, so NC forcing the port isn’t a problem for me. That’s probably why it works.

ckoehler commented 4 years ago

I posted it in the Traefik 2.0 issue: https://github.com/davestephens/ansible-nas/issues/142

bcurran3 commented 4 years ago

Cool. Thanks!

bcurran3 commented 4 years ago

Well, thinking about it, I am actually forwarding both 443 and 80 to my server, so NC forcing the port isn’t a problem for me. That’s probably why it works.

I think we're talking about different environments. If you're on your LAN accessing NC there is no firewall or port forwarding involved, that would be for remote access.

Anyways, doesn't really matter. It's my problem with my setup. Might be fixed by upgrading to Traefik v2. Might be able to fixed by changing something in my current config. Just https://nextcloud.mydomain.com:443/ doesn't get me to a NextCloud instance - correction: I just tried and it does! But the client doesn't auth correctly using that. OK. Probably something in my NC setup then. Back to the drawing board! Thanks for the assist.

davestephens commented 3 years ago

There is sort-of-a-PR open to address this: https://github.com/davestephens/ansible-nas/pull/393

My current thinking is to set the container to latest and ensure that Watchtower keeps it up to date. Result - no stupid upgrade dances in the future...

Would appreciate opinions!