Nextcloud Swag logo page after setup

  • Hi all, I followed this process to install nextcloud.

    . I though I had done it properly but ended up with the issue in my screenshot. I used this script;


    version: "2.0"

    services:

    nextcloud:

    image: ghcr.io/linuxserver/nextcloud

    container_name: nextcloud

    environment:

    - PUID=1000

    - PGID=1000

    - TZ=America/Edmonton

    volumes:

    - /srv/dev-disk-by-uuid-957d6881-558a-4350-864d-3c03a1d7a2d4/appdata/nextcloud/config:/config

    - /srv/dev-disk-by-uuid-957d6881-558a-4350-864d-3c03a1d7a2d4/appdata/nextcloud/data:/data

    depends_on:

    - mariadb

    restart: unless-stopped

    mariadb:

    image: linuxserver/mariadb

    container_name: mariadb

    environment:

    - PUID=1000

    - PGID=1000

    - MYSQL_ROOT_PASSWORD=************

    - TZ=America/Edmonton

    volumes:

    - /srv/dev-disk-by-uuid-957d6881-558a-4350-864d-3c03a1d7a2d4/appdata/mariadb/config:/config

    restart: unless-stopped

    swag:

    image: linuxserver/swag

    container_name: swag

    cap_add:

    - NET_ADMIN

    environment:

    - PUID=1000

    - PGID=1000

    - TZ=America/Edmonton

    - URL=*********************************

    - SUBDOMAINS=wildcard

    - VALIDATION=duckdns

    - EMAIL=*******************************

    - DUCKDNSTOKEN=*************************************

    volumes:

    - /srv/dev-disk-by-uuid-957d6881-558a-4350-864d-3c03a1d7a2d4/appdata/swag/config:/config

    ports:

    - 443:443

    restart: unless-stopped

    networks:

    default:

    external:

    name: nextcloud


    Any ideas where I went wrong?

  • jjfire

    Changed the title of the thread from “Nextcloud installation problem” to “Nextcloud Swag logo page after setup”.
  • Almost sure that noone will watch the video just to know what you did (unless it was the one from the forum)


    See this guide and compare to what you did and see the errors/deviations:

    https://forum.openmediavault.o…g-OMV-and-docker-compose/


    Couple of pointers:

    Your PUID=1000 && PGUID=1000 need to to exist on your OS (most of the times, the PGUID is 100 which is the "users" group)

    To find what is your ID, just run in a terminal id <name of the user you want to run with docker>


    It's a good policy of hiding/mask the URL. Now, everybody who sees this knows your URL/IP.


    You don't give any info on how you are running the server, but if you're on RPi armhf, you should tag the image to alpine:

    image: linuxserver/mariadb:alpine

    Again, this is only if you're on a RPi with armhf.


    Other than that, it looks OK but it all comes down as to what you did.

  • jjfire

    Added the Label OMV 5.x
  • Also when you display your .yml file, copy and paste it into a code box (the </> button in the menu bar at the top of the post) so we can see the indentation of the file - because:

    1. Indentation does matter to the functionality of the file.
    2. It makes it easier to read for those looking for mistakes.

    Simple and sure backup and restore: In a Scheduled Job: rsync -av --delete /srv/dev-disk-by-label-SOURCE/ /srv/dev-disk-by-label-DESTINATION/ (HT: Getting Started with OMV5)
    Server Software: OMV 5 (current) - My Main Server: Thinkserver TS140, Nextcloud, Plex, Airsonic, Navidrome, Ubooquity, Digikam, & Heimdall - My Backup Machine: NanoPi M4 (v.1), Pi-Hole - Odroid XU4 (Using DietPi) - Testing/Playing: hc2, xu4, Pi 3B+, Odroid H2. Mac user converting to Linux, Debian 10 KDE.

  • jjfire

    Added the Label resolved

Participate now!

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