Posts by shecky66

From yesterday, my NextCloud Docker installation result in Maintenance Mode.

How I can disabled It?

SOLVED!

Problem was due to a plugin incomplete update.
To resolve, enter on docker bash:

sudo docker exec -it <YOUR-DOCKER-NAME> /bin/bash

To remove maintenance mode, digit:

sudo -u abc php /config/www/nextcloud/occ maintenance:mode --off

(where "abc" is the user owner of config.php)

To avoid timeouts with large installations, you can run the following command from the installation folder.
So digits:

cd /config/www/nextcloud   #installation folder for Nextcloud docker
occ upgrade

Thats all!

Up.

Hi at all!

In my OMV, I installed Nextcloud (following the macom guide - [How-To] Nextcloud with Letsencrypt using OMV and docker-compose) and Airsonic.

Airsonic however does not use Letsencrypt, so I tried to change its configuration.

First of all, I removed LetsEncrypt service from the Nextcloud stack and created a container only for it.

I added LetsEncrypt container network the to the containers of the Nextcloud stack (redis, nextcloud and nextcloudDB).

Nextcloud continues to work properly.

So, I tried to follow the same steps to insert LetsEncrypt on Airsonic.

• I removed 4040 port forwarding from the router, leaving only ports 80 and 443 rules.
• I modified the Airsonic stack by inserting the variables CONTEXT_PATH and JAVA_OPTS and remove port 4040

---
version: "2.1"
services:
  airsonic:
    image: linuxserver/airsonic
    container_name: airsonic
    environment:
      - PUID=998
      - PGID=100
      - TZ=Europe/Rome
      - CONTEXT_PATH=/airsonic
      - JAVA_OPTS=-Dserver.use-forward-headers=true
    volumes:
      - /srv/app/config/airsonic:/config
      - /srv/dev-mydisk/music:/music
      - /srv/dev-mydisk/playlists:/playlists
      - /srv/dev-mydisk/podcasts:/podcasts
      - /srv/dev-mydisk/other_media:/media
      - /srv/dev-mydisk/private:/private
    restart: unless-stopped    

• I removed from airsonic container the bridge network and added the LetsEncrypt network

I then moved on to setting up the proxy:

cd /srv/dev-mydisk/appdata/letsencrypt/nginx/proxy-confs

cp airsonic.subfolder.conf.sample airsonic.subfolder.conf

and I modified the .conf file in this way:

# set the CONTEXT_PATH variable to /airsonic in airsonic container.

location ^~ /airsonic/ {
    # enable the next two lines for http auth
    #auth_basic "Restricted";
    #auth_basic_user_file /config/nginx/.htpasswd;

    # enable the next two lines for ldap auth, also customize and enable ldap.conf in the default conf
    #auth_request /auth;
    #error_page 401 =200 /ldaplogin;

    # enable for Authelia, also enable authelia-server.conf in the default site config
    #include /config/nginx/authelia-location.conf;

    include /config/nginx/proxy.conf;
    resolver 127.0.0.11 valid=30s;
    set $upstream_app airsonic;
    set $upstream_port 443;
    set $upstream_proto https;
    proxy_pass $upstream_proto://$upstream_app:$upstream_port;
    
    rewrite /airsonic(.*) $1 break;    
}

Now, if I call:

• https://mydomain.com/airsonic/ I am redirected to Nextcloud (https://mydomain.com/nextcloud/) or get a 502 error (Bad Gateway)
• https://mydomain.com/airsonic/login I get a 502 error (Bad Gateway)

Someone can help me?

Thanks!

Try this filter configuration

In Fail2ban the filter configuration file for Nextcloud is missing!

Create it with:

sudo nano /etc/fail2ban/filter.d/nextcloud.conf

Add the following to the file:

# Fail2Ban filter configuration file for Nextcloud
#
# /etc/fail2ban/filter.d/nextcloud.conf

[Definition]
failregex = ^{"reqId":".","remoteAddr":".","app":"core","message":"Login failed: '.' (Remote IP: '')","level":2,"time":"."}$
            ^{"reqId":".","level":2,"time":".","remoteAddr":".","app":"core".","message":"Login failed: '.' (Remote IP: '')".}$
            ^.\"remoteAddr\":\"\".Trusted domain error.*$

Now go to Fail2Ban --> Jails and add a new jails with this options:

Name: nextcloud
Port: http,https
Max Retry: 3
Ban Time: -1
Filter: nextcloud
Log Path: path/to/yournextcloud/data/nextcloud.log

Activate the nextcloud jail and deactivate apache-404 and apache-noscript jails (if they are not present in your installation).

Problem solved!

Quote from lameneb279

In the jails nextcloud enabled?
Check nextcloud jail log path
Should be like "path/to/yournextcloud/data/nextcloud.log

No.
No jails appplied for nextcloud.

Use putty, go to that folder and run the command

ls -la

the contents of the folder will be displayed

I have installed and activated the Fail2Ban plugin and setup some jails.

In the "Services" area it is enabled again but not running.

When I click on the Fail2ban tab the following error is shown

This is the error with it's details:

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; fail2ban-client status 2>&1' with exit code '255': Failed to access socket path: /var/run/fail2ban/fail2ban.sock. Is fail2ban running?

Details:
Errore #0:
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; fail2ban-client status 2>&1' with exit code '255':  Failed to access socket path: /var/run/fail2ban/fail2ban.sock. Is fail2ban running? in /usr/share/php/openmediavault/system/process.inc:182
Stack trace:
#0 /usr/share/openmediavault/engined/rpc/fail2ban.inc(141): OMV\System\Process->execute(Array, 255)
#1 [internal function]: OMVRpcServiceFail2ban->getStats(NULL, Array)
#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('getStats', NULL, Array)
#4 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Fail2Ban', 'getStats', NULL, Array, 1)
#5 {main}

Someone can help me?

Thanks.

Davide.

Here you find the guide:

[How-To] Install Plex Media Server (PMS) container using OMV and docker-compose

Hi, davidh2k !

I started from your configuration and I came to this:

---
version: "2"
services:
  dev-db:
    image: mariadb:latest
    container_name: dev-db
    environment:
      - TZ=Europe/Rome
      - MYSQL_ROOT_PASSWORD=***********
      - MYSQL_DATABASE=test
      - MYSQL_USER=test
      - MYSQL_PASSWORD=test
      - MYSQL_ALLOW_EMPTY_PASSWORD=no
    volumes:
      - /path/to/appdata/develop/db:/var/lib/mysql
    ports:
      - 3306:3306
    networks:
      - developarea  
    restart: unless-stopped
  dev-data:
    image: php:7.4-apache
    container_name: dev-data
    volumes:
      - /path/to/appdata/develop/www:/var/www/html
    ports:
      - 80:80
    links: 
      - dev-db:mysql
    networks:
      - developarea      
    restart: always
  dev-pma:
    depends_on:
      - dev-db  
    image: phpmyadmin/phpmyadmin
    container_name: dev-pma
    environment:
      PMA_HOST: dev-db
      MYSQL_ROOT_PASSWORD: ***********
      MYSQL_USER: test
    ports:
      - 81:80
    links:
      - dev-db:mysql
    networks:
      - developarea      
    restart: always
networks:
  developarea:    

...and everything works fine!

Thanks for your support!

Davide.

Quote from macom

When trying to use hostname instead of IP, did you edit the stack and the config.php like here?

RE: [How-To] Nextcloud with Letsencrypt using OMV and docker-compose

Just tried it and works for me.

Now it works!

Yes.

This is a screenshot of stack details

I try with network name, but with this setting receive Internal Server Error again...

Quote from monsen

The port 6379 stays fix for me. Not sure why it would change. It shouldn't

On reboot change the host IP, not the port

Last night, following the macom guide I installed Nextcloud on my OMV 5.x.

To speed up Nextcloud as suggested by monsen I also added redis to the stack.

Everything worked perfectly so I turned OMV off.

When I restarted it this morning, I received the "Internal Server Error" message.

I checked the logs, but there was no obvious error.

I therefore went to check the port assigned to redis container which was different from the one used before the restart.

My question then is:

is there any way to fix the port used by redis container so that it doesn't change with every reboot?

Nextcloud config.pho now start with:

<?php
$CONFIG = array (
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'memcache.distributed' => '\\OC\\Memcache\\Redis',
  'redis' =>
  array (
     'host'     => '172.18.0.3', # <== this value changes with each reboot
     'port'     => 6379,
  ),  

Do I need to change the host value?

If yes, what value should be entered?

Thanks.
Davide.

Quote from davidh2k

This may gets you started. Note however that you may need to tune it a bit here and there to fit your needs.

Code

version: "3"

services:
  webserver:
    image: nginx:latest
    container_name: webdev_nginx
    volumes:
      - /path/to/appdata/webdev/www:/www
      - /path/to/appdata/webdev/config:/etc/nginx/conf.d/default.conf
      - /path/to/appdata/webdev/config_php:/usr/local/etc/php-fpm.d/www.conf
    ports:
      - 80:80 # you can alter the hostport if you want to
    restart: unless-stopped


  php7:
    image: php7.3-mysql
    container_name: webdev_php
    volumes:
      - /path/to/appdata/webdev/www:/www
    restart: unless-stopped

  mysql:
    image: mysql:5.7
    container_name: webdev_db
    command: --init-file /db/init.sql
    environment:
      MYSQL_ROOT_USER: root
      MYSQL_ROOT_PASSWORD: yourpassword
      MYSQL_DATABASE: database
      MYSQL_USER: root
      MYSQL_PASSWORD: yourpassword
    volumes:
      - /path/to/appdata/webdev/db:/db
      - /path/to/appdata/webdev/mysql:/var/lib/mysql
    restart: unless-stopped

Display More

You can read up on the individual docker hub pages to get more info about the specifics for each container.

Greetings

David

Display More

Only a David could reply to another Davide in this way...

Now I try it and let you know

Thanks so much!

Hi sabamimi !

Do you know where i can download a docker (Apache, Mysql or MariaDb and PHP) to use with portainer?

Thanks in advance for your reply.

Among other things, I'm not interested that my works are visible from the "outside" but only from my internal network.
So I don't even need to perform port forwarding on ports 80 and 443

Thanks macom !

This was exactly the kind of help I was looking for

If I can take advantage of you, according to your point of view, it's better to stay on Nginx (on which OMV is based) or look for a docker with Apache?

Could Nginx and Apache on the same machine create conflicts?

Thanks again for your reply.

Nobody helps a poor developer?

UP