Posts by UKnau22

Quote from kamild1996

I haven't had a chance to test the command yet (I choose not to restart my Odroid purposefully because of its strange issues with HDD detection), but I'll remember to try

Untested, but here's what I'd try:

• Login to the OMV's Linux shell
• sudo nano /etc/systemd/system/remount-nfs-on-unlock.service
• In the editor, paste this:

Code

[Unit]
Description=Remount NFS shares once LUKS volumes are unlocked
After=default.target

[Service]
ExecStart=/usr/local/bin/remount-nfs-on-unlock.sh

[Install]
WantedBy=default.target

• sudo nano /usr/local/bin/remount-nfs-on-unlock.sh
• In the editor, paste this: (you may need to refer to "Storage > Encryption" in OMV panel and replace the path in the 5th line of the script below with what you see in the "Decrypted Device" column)

Bash

#!/bin/sh
# remount-nfs-on-unlock.sh

while true; do
  if df | grep -q '/dev/mapper/md0-crypt';
  then
    echo "unlocked, remounting..."
    mount -o bind,rw /export/shared
    exit
  else
    echo "still locked, wait for 10 seconds and try again"
    sleep 10
fi
done

Display More

(thank you DimaKompot for this script)

• sudo chmod a+x /usr/local/bin/remount-nfs-on-unlock.sh
• sudo systemctl enable remount-nfs-on-unlock.service

Great write-up! I just stumbled across the same issue and found this thread. Took 5 minutes to implement and works!!!

THANK YOU!

OK, I figured it out just by hunch.... Had to add the full path to the /docker/volumes/.... directory in the docker compose file.

However... And this is what I've been dealing with all day... I can not access NextCloud through either the local IP:8080 nor NGINX...

I give up

This is the docker compose from the guide. I used it without any changes. The nextcloud_aio_mastercontainer directory was created but nothing inside it. The /_data folder doesn't exist

Quote

services:

nextcloud-aio-mastercontainer:

image: nextcloud/all-in-one:latest

restart: always

container_name: nextcloud-aio-mastercontainer

volumes:

- nextcloud_aio_mastercontainer:/mnt/docker-aio-config

- /var/run/docker.sock:/var/run/docker.sock:ro

ports:

- 11000:8080

environment:

- APACHE_PORT=11000

- NEXTCLOUD_DATADIR=CHANGE_TO_COMPOSE_DATA_PATH/nextcloud_data

volumes:

nextcloud_aio_mastercontainer:

name: nextcloud_aio_mastercontainer

Display More

I used the docker compose file for NextCloud AIO with reverse proxy option , but when I try deploy that container I get an error and it doesn't start.

I checked in the docker/volumes directory and it did create the nextcloud_aio_mastercontainer directory. It's empty though..

Quote

Error response from daemon: error evaluating symlinks from mount source "/srv/dev-disk-by-uuid-06b2b88f-d787-4fa0-abe6-8bebfcc3ac56/docker/volumes/nextcloud_aio_mastercontainer/_data": lstat /srv/dev-disk-by-uuid-06b2b88f-d787-4fa0-abe6-8bebfcc3ac56/docker/volumes/nextcloud_aio_mastercontainer/_data: no such file or directory in /usr/share/openmediavault/engined/rpc/compose.inc:613

I spent all day trying to get AIO to work and failed miserably!

However I was able to install a different version of NC and got it to work with NGINX PM instead of Swag.

Thanx for your help guys!

OK, I got that setup working in a test container. Made the necessary adjustments for a wildcard certificate and was able to setup the nginx for my HomeAssistant instance. Now both, NextCloud test server and HomeAssistant are accessible...

Now I just gotta figure out how to migrate NextCloud from my previous installation.

Thank you for helping out with this part! I'm still a work in progress...

Yes, I followed another migration guide that said to copy everything from the previous install. However the lines regarding Swag are changed to the new setup

I reinstalled NextCloud and Swag in a new OMV/Docker setup and can not figure out why NextCloud throws the 502 error.

I followed the guides available everywhere, copying the Swag nextcloud.subdomain.conf.sample to nextcloud.subdomain.conf and editing the NextCloud config.php file, using a copy from my previous setup as a template.

Swag is working fine, it pulled my wildcard certificate which I'm using for HomeAssistant (homeassistant.xxxxxxxx.duckdns.org). I also want to use it for nextcloud.xxxxxxxduckdns.org, which is what I did in my previous setup. When I attach to the console and ping the NextCloud container it gets a response.

Can't find anything in the NextCloud container logs

Any help, pointing me in the right direction would be appreciated. I spent hours on this already and can't figure it out...

Here is the subdomain.conf :

Quote

# located at /config/www/nextcloud/config/config.php and add the following lines before the ");":

# 'trusted_proxies' => ['swag'],

# 'overwrite.cli.url' => 'https://nextcloud.example.com/',

# 'overwritehost' => 'nextcloud.example.com',

# 'overwriteprotocol' => 'https',

#

# 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 => 'nextcloud.example.com',

# ),

server {

listen 443 ssl http2;

listen [::]:443 ssl http2;

server_name nextcloud.*;

include /config/nginx/ssl.conf;

client_max_body_size 0;

location / {

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;

# Hide proxy response headers from Nextcloud that conflict with ssl.conf

# Uncomment the Optional additional headers in SWAG's ssl.conf to pass Nextcloud's security scan

proxy_hide_header Referrer-Policy;

proxy_hide_header X-Content-Type-Options;

proxy_hide_header X-Frame-Options;

proxy_hide_header X-XSS-Protection;

# Disable proxy buffering

proxy_buffering off;

}

}

Display More

And here the config.php:

Quote

<?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' => '***************',

'passwordsalt' => '*************************************',

'secret' => '*****************************************************************',

'trusted_domains' =>

array (

0 => '192.168.1.122:8080',

1 => 'nextcloud.xxxxxxx.duckdns.org',

),

'datadirectory' => '/var/www/html/data',

'dbtype' => 'mysql',

'version' => '27.0.2.1',

'overwrite.cli.url' => 'https://nextcloud.xxxxxxx.duckdns.org',

'dbname' => 'nextcloud',

'dbhost' => 'mariadb',

'dbport' => '',

'dbtableprefix' => 'oc_',

'mysql.utf8mb4' => true,

'dbuser' => 'nextcloud',

'dbpassword' => '******************',

'installed' => true,

'default_phone_region' => 'US',

'trusted_proxies' =>

array (

0 => ['swag'],

),

'overwritehost' => 'nextcloud.xxxxxx.duckdns.org',

'overwriteprotocol' => 'https'

'app_install_overwrite' =>

array (

0 => 'backup',

1 => 'maps',

),

'mail_from_address' => 'xxxxxxxxx',

'mail_smtpmode' => 'smtp',

'mail_sendmailmode' => 'smtp',

'mail_domain' => 'yahoo.com',

'mail_smtphost' => 'smtp.mail.yahoo.com',

'mail_smtpauth' => 1,

'mail_smtpsecure' => 'ssl',

'mail_smtpname' => 'xxxxxxx@yahoo.com',

'mail_smtppassword' => '***************',

'mail_smtpport' => '465',

'loglevel' => 2,

'maintenance' => false,

);

Display More

I had opened up a new thread because I realized this one was marked as resolved, and eventually figured it out.

Post

RE: SWAG Docker certbot: command not found

try to change line lscr.io/linuxserver/swag by linuxserver/swag:latest

raulfg3

Aug 12th 2023

Thank you all for your help!

Oh, right. I saw that earlier and forgot about it...

Thank you

OMG! That did the trick!

So I deleted the swag container, removed the volume with all data and then reinstalled swag with all the same settings. The container immediately downloaded a new certificate!

Obviously after all that I had to re-write the subdomain.conf files. To reconnect the containers and now everything is up and running again!

Thank you again for your time!

Really appreciate you trying to help!

version: "3"
services:
  homeassistant:
    container_name: homeassistant
    image: homeassistant/home-assistant
    volumes:
      - /srv/dev-disk-by-uuid-131c09b9-6436-48f7-9b9c-2490f420e7b1/docker/volumes/HomeAssistant/_data:/config
      - /etc/localtime:/etc/localtime:ro
    ports:
      - 8123:8123
    network_mode: host
    restart: unless-stopped

  swag:
    image: lscr.io/linuxserver/swag
    container_name: swag
    cap_add:
      - NET_ADMIN
    environment:
      - PUID=1000
      - PGID=100
      - TZ=US/Pacific
      - URL=xxxxxxx.duckdns.org
      - VALIDATION=duckdns
      - DUCKDNSTOKEN=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
      - SUBDOMAINS=wildcard
    volumes:
      - /srv/dev-disk-by-uuid-131c09b9-6436-48f7-9b9c-2490f420e7b1/docker/volumes/Swag/_data:/config
    ports:
      - 443:443
      - 80:80
    restart: unless-stopped


# set trusted docker internal network
networks:
  default:
      ipam:
        config:
         - subnet: 172.10.0.0/24

I searched that linuxserver forum as well. Haven't posted anything, because I had to sign up and figure that one out...

I'm about to completely delete the Swag container including volumes and everything and see if I can start from scratch.

root@2e4515103cf0:/#certbot renew
bash: certbot: command not found

Yeah, I did that... It's the exact same response and the log shows the same thing.

Certbot doesn't even start. The command is not known. That is the problem. It has been trying to do the renewal, but can't because (it seems to me) that certbot is not installed.

root@raspberrypi:/home/udo# docker exec -it swag bash
root@2e4515103cf0:/#certbot-renew
bash: certbot-renew: command not found
root@2e4515103cf0:/#certbot renew
bash: certbot: command not found
root@2e4515103cf0:/#

It does not know the command certbot. Above is the response I get...

Seems to me as if the certbot portion of that container doesn't exist...

nginx portion works fine

[migrations] started
[migrations] 01-nginx-site-confs-default: skipped
[migrations] done
usermod: no changes
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support the app dev(s) visit:
Certbot: https://supporters.eff.org/donate/support-work-on-certbot

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    1000
User GID:    100
───────────────────────────────────────

using keys found in /config/keys
Variables set:
PUID=1000
PGID=100
TZ=US/Pacific
URL=*******.duckdns.org
SUBDOMAINS=wildcard
EXTRA_DOMAINS=
ONLY_SUBDOMAINS=false
VALIDATION=duckdns
CERTPROVIDER=
DNSPLUGIN=
EMAIL=*********@*****.**
STAGING=

the resulting certificate will only cover the subdomains due to a limitation of duckdns, so it is advised to set the root location to use www.subdomain.duckdns.org
Using Let's Encrypt as the cert provider
SUBDOMAINS entered, processing
Wildcard cert for *******.duckdns.org will be requested
E-mail address entered: *********@*****.**
dns validation via duckdns plugin is selected
Certificate exists; parameters unchanged; starting nginx
The cert is either expired or it expires within the next day. Attempting to renew. This could take up to 10 minutes.
<------------------------------------------------->

<------------------------------------------------->
cronjob running on Fri Aug 11 17:54:00 PDT 2023
Running certbot renew
/app/le-renew.sh: line 9: certbot: command not found
**** The following active confs have different version dates than the samples that are shipped. ****
**** This may be due to user customization or an update to the samples. ****
**** You should compare the following files to the samples in the same folder and update them. ****
**** Use the link at the top of the file to view the changelog. ****
┌────────────┬────────────┬────────────────────────────────────────────────────────────────────────┐
│  old date  │  new date  │ path                                                                   │
├────────────┼────────────┼────────────────────────────────────────────────────────────────────────┤
│ 2022-09-08 │ 2023-05-31 │ /config/nginx/proxy-confs/homeassistant.subdomain.conf                 │
│ 2023-05-10 │ 2023-06-24 │ /config/nginx/proxy-confs/nextcloud.subdomain.conf                     │
│ 2022-08-16 │ 2023-04-13 │ /config/nginx/nginx.conf                                               │
│ 2022-10-03 │ 2023-06-05 │ /config/nginx/site-confs/default.conf                                  │
│ 2022-08-20 │ 2023-06-24 │ /config/nginx/ssl.conf                                                 │
│ 2022-09-01 │ 2023-02-09 │ /config/nginx/proxy.conf                                               │
│ 2022-09-22 │ 2023-04-27 │ /config/nginx/authelia-server.conf                                     │
│ 2022-08-20 │ 2023-04-27 │ /config/nginx/authelia-location.conf                                   │
└────────────┴────────────┴────────────────────────────────────────────────────────────────────────┘
[custom-init] No custom files found, skipping...
[ls.io-init] done.
Server ready

I just noticed the SSL certificate for my duckdns domain is expiring tomorrow.

I'm using SWAG, previously installed in Portainer but reinstalled as per the guide with the new Compose plugin. Currently everything works as expected, 3 subdomains get proxied to the correct containers. However after tomorrow I will lose access to Nextcloud, Homeassistant and Motioneye from the outside world.

OMV6 and all my dockers are updated. I've been searching EVERYWHERE all day to find a solution but can not find a hint to make it work!

How can I renew the certificate?! Any ideas what the issue might be? Above is the Swag container log output

I opened a new thread because the other one I've been posting this issue on is marked as solved....

Quote from KM0201

If motioneye works, what is the output of:

Code

docker inspect motioneye | grep NetworkMode

 docker inspect swag | grep NetworkMode
            "NetworkMode": "docker-build_default",
 docker inspect nextcloud | grep NetworkMode
            "NetworkMode": "nextcloud_default",
 docker inspect MotionEye | grep NetworkMode
            "NetworkMode": "bridge",
 docker inspect homeassistant | grep NetworkMode
            "NetworkMode": "host",

All 3 containers that use Swag work fine. That's MotionEye, HomeAssistant and Nextcloud. They're all on different networks. Again, I don't understand how that affects the certbot renewal. I thought that happens within Swag and then nginx forwards https requests to the appropriate container... Am I misunderstanding the whole concept here?

docker: 'ls' is not a docker command.
See 'docker --help'

That's the output of that.

However, I don't see how the Network Mode is relevant to the cert renewal. I haven't made any changes there and it was working last time the renewal was due...

When I access HomeAssistant, MotionEye, and Nextcloud from outside the local network that all works fine (for now). The current cert expires next week, I believe...

 docker inspect swag | grep NetworkMode
            "NetworkMode": "docker-build_default",
 docker inspect nextcloud | grep NetworkMode
            "NetworkMode": "nextcloud_default",

Here's the output of those

[migrations] started
[migrations] 01-nginx-site-confs-default: skipped
[migrations] done
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support the app dev(s) visit:
Certbot: https://supporters.eff.org/donate/support-work-on-certbot

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    1000
User GID:    100
───────────────────────────────────────

using keys found in /config/keys
Variables set:
PUID=1000
PGID=100
TZ=US/Pacific
URL=xxxxxxx.duckdns.org
SUBDOMAINS=wildcard
EXTRA_DOMAINS=
ONLY_SUBDOMAINS=false
VALIDATION=duckdns
CERTPROVIDER=
DNSPLUGIN=
EMAIL=xxxxxxxxx@xxxxxxx.xxx
STAGING=

the resulting certificate will only cover the subdomains due to a limitation of duckdns, so it is advised to set the root location to use www.subdomain.duckdns.org
Using Let's Encrypt as the cert provider
SUBDOMAINS entered, processing
Wildcard cert for xxxxxxx.duckdns.org will be requested
E-mail address entered: xxxxxxxxx@xxxxxxx.xxx
dns validation via duckdns plugin is selected
Certificate exists; parameters unchanged; starting nginx
The cert is either expired or it expires within the next day. Attempting to renew. This could take up to 10 minutes.
<------------------------------------------------->

<------------------------------------------------->
cronjob running on Fri Aug 11 11:03:57 PDT 2023
Running certbot renew
/app/le-renew.sh: line 9: certbot: command not found
**** The following active confs have different version dates than the samples that are shipped. ****
**** This may be due to user customization or an update to the samples. ****
**** You should compare the following files to the samples in the same folder and update them. ****
**** Use the link at the top of the file to view the changelog. ****
┌────────────┬────────────┬────────────────────────────────────────────────────────────────────────┐
│  old date  │  new date  │ path                                                                   │
├────────────┼────────────┼────────────────────────────────────────────────────────────────────────┤
│ 2022-09-08 │ 2023-05-31 │ /config/nginx/proxy-confs/homeassistant.subdomain.conf                 │
│ 2023-05-10 │ 2023-06-24 │ /config/nginx/proxy-confs/nextcloud.subdomain.conf                     │
│ 2022-08-16 │ 2023-04-13 │ /config/nginx/nginx.conf                                               │
│ 2022-10-03 │ 2023-06-05 │ /config/nginx/site-confs/default.conf                                  │
│ 2022-08-20 │ 2023-06-24 │ /config/nginx/ssl.conf                                                 │
│ 2022-09-01 │ 2023-02-09 │ /config/nginx/proxy.conf                                               │
│ 2022-09-22 │ 2023-04-27 │ /config/nginx/authelia-server.conf                                     │
│ 2022-08-20 │ 2023-04-27 │ /config/nginx/authelia-location.conf                                   │
└────────────┴────────────┴────────────────────────────────────────────────────────────────────────┘
[custom-init] No custom files found, skipping...
[ls.io-init] done.
Server ready

This is the output.