Setting up nextcloud in docker

  • The initial setup doesn't require the SWAG part.

    That is why port 450:443 is there.

    After having it setup locally, then it's time to make the changes for remote access.

  • The only thing about setting up Nextcloud locally is that when you introduce Swag you have to remember to set the reverse proxy .conf file to include the local AND the remote address in the trusted domains array. Example here. I couldn’t figure why I could access remotely but not locally until I saw this little rid-bit. You could access locally before setting up Swag. Why not after? Duh, me!

    System Backup Typo alert: Under the Linux section the command should be sudo umount /dev/sda1 NOT sudo unmount /dev/sda1

    Backup Data Disk to Backup Disk on Same Machine: In a Scheduled Job:rsync -av --delete /srv/dev-disk-by-uuid-f8814ed9-9a5c-4e1c-8830-426968c20ea3/ /srv/dev-disk-by-uuid-e67439d5-00a3-4942-bd5f-b84ab86aa850/ Don't forget trailing slashes, and BE CAREFUL. (HT: Getting Started with OMV5)

    Equipment - Thinkserver TS140, NanoPi M4 (v.1), Odroid XU4 (Using DietPi): PiHole

  • Anyone know an easy way of updating the Linuxserver docker version of Nextcloud? I'm stuck on Nextcloud 23.02, there have ben two versions since and docker updates but still same Nextcloud version. I know there are guides to manually update but they don't look that easy.

    Inwin MS04 case with 315 W PSU

    ASUS Prime H310i-Plus R2.0 board

    Two port PCI-E SATA card

    8GB Kingston DDR4

    Intel Pentium Coffee Lake G5400 CPU

    Samsung Evo M.2 256GB OS drive

    4x4TB WD Red NAS drives + 5TB Seagate drive - MergerFS pool

    Seagate 4TB USB drive - SnapRAID parity x 2

    Seagate 5TB USB drive

  • Anyone know an easy way of updating the Linuxserver docker version of Nextcloud? I'm stuck on Nextcloud 23.02, there have ben two versions since and docker updates but still same Nextcloud version. I know there are guides to manually update but they don't look that easy.

    That's weird, I updated to 23.04 this morning w/ the GUI no problem.


    You can try executing this command


    docker exec -it nextcloud updater.phar


    (this of course assumes your nextcloud container is named nextcloud)

  • This did the job where the Nextcloud web interface just gave error messages - thanks very much.

    Inwin MS04 case with 315 W PSU

    ASUS Prime H310i-Plus R2.0 board

    Two port PCI-E SATA card

    8GB Kingston DDR4

    Intel Pentium Coffee Lake G5400 CPU

    Samsung Evo M.2 256GB OS drive

    4x4TB WD Red NAS drives + 5TB Seagate drive - MergerFS pool

    Seagate 4TB USB drive - SnapRAID parity x 2

    Seagate 5TB USB drive

  • Just to add that the download of the Nextcloud update took the best part of an hour on a fast fibre connection using this method in case you're thinking it isn't happening.

    Inwin MS04 case with 315 W PSU

    ASUS Prime H310i-Plus R2.0 board

    Two port PCI-E SATA card

    8GB Kingston DDR4

    Intel Pentium Coffee Lake G5400 CPU

    Samsung Evo M.2 256GB OS drive

    4x4TB WD Red NAS drives + 5TB Seagate drive - MergerFS pool

    Seagate 4TB USB drive - SnapRAID parity x 2

    Seagate 5TB USB drive

  • Just to add that the download of the Nextcloud update took the best part of an hour on a fast fibre connection using this method in case you're thinking it isn't happening.

    Sounds like you've got something else going on, or maybe NC's servers were having issues... Like I said, the upgrade took me about 5min tops from the GUI (and my experience w/ the docker command in the past has been similar)

  • Just to add that the download of the Nextcloud update took the best part of an hour on a fast fibre connection using this method in case you're thinking it isn't happening.

    Although I run it via the Web GUI, just made the update now and it took less than 5m.


    If using the docker version (in my case from Linuxserver), first, update the image to the latest (either via docker pull or via portainer).

    Restart the container and go to the Nextcloud settings and update from there.


    All status is shown on the browser.

  • That's a good point actually... Are you using the :latest tag on your nextcloud image?

  • That's a good point actually... Are you using the :latest tag on your nextcloud image?

    Yes, 😉

  • Hi I'm sorry for the late reply I've been very busy, I tried what you said and it takes me to this page

  • I dont have the email address error anymore because i changed to KM0201s method. My current error is a PHP error in my nextcloud logs which you can see in one of my later posts

  • That's how I always do it.. but I think maacom's tutorial is a little different.

    I followed your tutorial for this one I believe.


    My current situation:


    When I access from outside my network I get this:

    Hi I'm sorry for the late reply I've been very busy, I tried what you said and it takes me to this page



    When I check nexcloud logs I get this:



    And I can't access nextcloud interface.

  • That looks fine


    Start w/ getting it to work locally, don't worry about swag, we'll cross that bridge when it's working locally

    Yup I just got to step 11 in your guide and I can still access it fine via my ip:450.


    I deployed swag and checked all my logs, no errors reports! Although nextclouddb seems to be stuck on this step and hasnt sent over a "DONE".



    here's my swag logs


    I'll carry on with the steps now, fingers crossed

  • That's a normal ending of a log for mysql/mariadb. Mine has ended w/ that forever..

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!