Yes git worked fine. Deleted the .git folder as you suggested. Correct that I don't want a git mirror in this case. I'll keep you comment for future reference.

ok thanks. I'm never sure what can co-exist with OMV without causing issues. Will give the above a try.

I would like to use a 'git clone https://...' command from an SSH terminal to download files to a Nextcloud app folder. I'm leery of installing GIT directly on my OMV OS drive. I'm guessing running GIT under a docker container might be safer. If someone could confirm this and provide further links/guides for me to investigate that would be much appreciated. I already have docker installed running several apps, such as Nextcloud and Navidrome, and have no issues, and would like to keep it that way (!).

```

Client: Docker Engine - Community

Version: 24.0.5

API version: 1.43

Go version: go1.20.6

Git commit: ced0996

Built: Fri Jul 21 20:35:38 2023

OS/Arch: linux/arm64

Context: default

Server: Docker Engine - Community

Engine:

Version: 24.0.5

API version: 1.43 (minimum version 1.12)

Go version: go1.20.6

Git commit: a61e2b4

Built: Fri Jul 21 20:35:38 2023

OS/Arch: linux/arm64

Experimental: false

containerd:

Version: 1.6.22

GitCommit: 8165feabfdfe38c65b599c4993d227328c231fca

runc:

Version: 1.1.8

GitCommit: v1.1.8-0-g82f18fe

docker-init:

Version: 0.19.0

GitCommit: de40ad0

```

```

root@raspberrypi:/# dpkg -l | grep openmediavault

ii openmediavault 6.5.6-1 all openmediavault - The open network attached storage solution

ii openmediavault-compose 6.9.9 all OpenMediaVault compose plugin

ii openmediavault-cputemp 6.1.3 all cpu temperature plugin for openmediavault

ii openmediavault-flashmemory 6.2 all folder2ram plugin for openmediavault

ii openmediavault-ftp 6.0.5-1 all openmediavault FTP-Server plugin

ii openmediavault-keyring 1.0.2-2 all GnuPG archive keys of the openmediavault archive

ii openmediavault-omvextrasorg 6.3.1 all OMV-Extras.org Package Repositories for OpenMediaVault

ii openmediavault-sharerootfs 6.0.3-1 all openmediavault share root filesystem plugin

ii openmediavault-symlinks 6.0.4 all OpenMediaVault symlinks plugin

```

Thanks for the feedback. I'm somewhat cautious about giving containers access to system files/directories on my SD card, but will dig some more...

I'm running OMV6 on a Pi4. I installed docker with these instructions a while back and it works just fine:

omv6:docker_in_omv [omv-extras.org]

The above instructions specifiy the creation of 3 folders:

/SSD/appdata

/SSD/docker

/SSD/compose

which I have done.

https://nginxproxymanager.com/…hosting-your-home-network provides the following YML template (I use Docker-Compose, and not Portainer):

version: '3.8'

services:

app:

image: 'jc21/nginx-proxy-manager:latest'

restart: unless-stopped

ports:

- '8080:80'

- '8181:81'

- '4433:443'

volumes:

- ./data:/data

- ./letsencrypt:/etc/letsencrypt

I changed the ports for now to avoid some conflicts, and I'm guessing I need to set the volumes to:

volumes:

- /SSD/appdata/nginx-proxy-manager:/data

- ./letsencrypt:/etc/letsencrypt <-- not sure what to set this to.

My main question is how to map the letsencrypt volume. Would:

/SSD/appdata/letsencrypt:/etc/letsencrypt

be OK??

ok, re-did this from scratch, followed instructions from macom, and this this time things worked!. Many thanks.

R.

Ok thanks will give that a try. ... no luck. Will try the other guides again.

I'm trying to run NextCloud (Docker container) on a Raspberry Pi 4B, 64-bot, 8GB RAM) running Open Media Vault 6, over an encrypted https connection. I'm getting that above error (B504 - Bad gateway nginx when typing https://my.domain.name.com/nextcloud/ (not my actual domain name) on a browser (both Windows PC and iPhone).

I'm using DynuDNS as my DDNS provider, have for some time, no issues there. NextCloud was working fine with http access before I converted the setup to run https. For http access (internal network only) I was using port 8080 off my internal Raspberry Pi IP address (192.168.1.25:8080) at the time with no issues.

After adding swag, no such luck; am getting a locked icon on my https://domain.name/nextcloud (, a bit reluctant to provide it here) so I assume swag is working.

I have to admit that I'm getting somewhat confused with port mappings and what absolutely needs what port to work on. OMV itself I have running on port 82 (192.168.1.25:82).

Any help/comments appreciated.

Ray

Docker-compose yml file (some fields redacted with xxx's, and my actual domain name replaced with my.domain.com)

services:
  db:
    image: mariadb:10.6
    restart: always
    command: --transaction-isolation=READ-COMMITTED --log-bin=binlog --binlog-format=ROW
    volumes:
      - /SSD/appdata/nextclouddb:/var/lib/mysql
    environment:
      - MYSQL_ROOT_PASSWORD=xxx
      - MYSQL_PASSWORD=xxx
      - MYSQL_DATABASE=nextcloud
      - MYSQL_USER=nextcloud

  
  app:
    image: nextcloud
    restart: always
#    ports:
#     - 8080:80
    links:
      - db
    volumes:
      - /SSD/appdata/nextcloud:/var/www/html
    environment:
      - MYSQL_PASSWORD=xxx
      - MYSQL_DATABASE=nextcloud
      - MYSQL_USER=nextcloud
      - MYSQL_HOST=db

  swag:
    image: lscr.io/linuxserver/swag:latest         #swag is the replacement for letsencrypt (see link below)
    container_name: swag
    cap_add:
      - NET_ADMIN
    environment:
      - PUID=1001 #change PUID if needed
      - PGID=100  #change PGID if needed
      - TZ=America/Toronto # change Time Zone if needed
      - URL=my.domain.com #insert your domain name - yourdomain.url
#      - SUBDOMAINS=www,
      - VALIDATION=http
      - EMAIL=xxx@gmail.com # define email; required to renew certificate
    volumes:
      - /SSD/appdata/swag:/config  #/srv/dev-disk-by-label-disk1 needs to be adjusted
    ports:
      - 443:443
      - 8080:80
    restart: unless-stopped

NextCloud configuration file </SSD/appdata/nextcloud/config/config.php>

<?php
$CONFIG = array (
  'htaccess.RewriteBase' => '/',
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'apps_paths' =>
  array (
    0 =>
    array (
      'path' => '/var/www/html/apps',
      'url' => '/apps',
      'writable' => false,
    ),
    1 =>
    array (
      'path' => '/var/www/html/custom_apps',
      'url' => '/custom_apps',
      'writable' => true,
    ),
  ),
  'instanceid' => 'xxxxxxf9kt03',
  'passwordsalt' => 'xxxxxxxxxxx2ha0usUmilyJPCcYi+',
  'secret' => 'xxxxxxxxxxxxxxkPAlz1dSIpSnmOamHgjM2pHaMYDu4EK3c',
  'trusted_domains' =>
  array (
    0 => '192.168.1.25:443',
    1 => 'my.domain.com',
  ),
  'datadirectory' => '/var/www/html/data',
  'dbtype' => 'mysql',
  'version' => '26.0.1.1',
  'dbname' => 'nextcloud',
  'dbhost' => 'db',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'dbuser' => 'nextcloud',
  'dbpassword' => 'xxx',
  'installed' => true,
  'trusted_proxies' =>['swag'],
  'overwritewebroot' => '/nextcloud',
  'overwrite.cli.url' => 'https://my.domain.com/nextcloud/',
  'overwriteprotocol' => 'https',
);

NextCloud subfolderconfiguration </SSD/appdata/swag/nginx/proxy-confs/nextcloud.subfolder.conf>

## Version 2023/02/05
# make sure that your nextcloud container is named nextcloud
# make sure that nextcloud is set to work with the base url /nextcloud/
# Assuming this container is called "swag", edit your nextcloud container's config
# located at /config/www/nextcloud/config/config.php and add the following lines before the ");":
#  'trusted_proxies' => ['swag'],
#  'overwritewebroot' => '/nextcloud',
#  'overwrite.cli.url' => 'https://example.com/nextcloud',
#
# Also don't forget to add your domain name to the trusted domains array. It should look somewhat like this:
#  array (
#    0 => '192.168.0.1:444', # This line may look different on your setup, don't modify it.
#    1 => 'example.com',
#  ),

location ^~ /.well-known {
    # The rules in this block are an adaptation of the rules
    # in the Nextcloud `.htaccess` that concern `/.well-known`.

    location = /.well-known/carddav { return 301 /nextcloud/remote.php/dav/; }
    location = /.well-known/caldav { return 301 /nextcloud/remote.php/dav/; }

    # Let Nextcloud's API for `/.well-known` URIs handle all other
    # requests by passing them to the front-end controller.
    return 301 /nextcloud/index.php$request_uri;
}

location ^~ /nextcloud/ {
    include /config/nginx/proxy.conf;
    include /config/nginx/resolver.conf;
    set $upstream_app nextcloud;
    set $upstream_port 443;
    set $upstream_proto https;
    proxy_pass $upstream_proto://$upstream_app:$upstream_port;

    rewrite /nextcloud(.*) $1 break;
    proxy_hide_header X-Frame-Options;
    proxy_max_temp_file_size 2048m;
    proxy_set_header Range $http_range;
    proxy_set_header If-Range $http_if_range;
    proxy_ssl_session_reuse off;
}
~                                                                                                                       ~                       

Have this on my router as well to complete the picture.

Not quite sure how the

502 Bad Gateway

nginx

issue got resolved... still struggling with this at my end. swag seems to be working as I have a 'locked' icon in my browser, but I can't connect to OMV/Docker/NextCloud app...

I had a similar issue, no DNS after installing Docker from the OMV-6-extras GUI. Googled this and someone commented that the aforementioned Docker installation removed the Network entry and disabled access to the access to DNS. I decided to re-image my SD card and start over. Needless to say this fixed my problem. Did not do anything with my Firewalls (router/Pi/Windows 11).