Posts by riff-raff

    Putting your services in container offers you so much more flexibility and comfort. You can easily update a version, create a copy and mess with it without harm; use a version you want despite the depecies between the service an the host system. You can control access of network or even isolate a container.

    It's worth putting a litte effort into it.

    Try using the images of and Portainer as GUI for Docker, might make things a little easier and visual.

    More straight forward: docker-compose.

    If you set an individual share and use it as docker root (you can do so in OMV-Extras -> Docker), you are able to backup it to an external drive with OMVs own USB backup plugin. If you set up your containers through docker compose files or portainer stacks, these definitions contain everything needed to restore complete functionality of your containers. Setup of container volumes within the shared docker folder is required.

    Thanks for the answer, sadly, the drive is not present any more, so I can't edit its settings through GUI. There are no self-test jobs for this drive configured, I just enabled monitoring. I hoped to unmonitor it by editing a certain configuration file.

    I accidently enabled smartmontools monitoring through OMV5 GUI for an external hard drive, which I do not own any more. Every day there's an email reminding me, that smartmontools can't find this drive. In which config can I unmonitor the drive?

    I configured it in admin site ... in user site i can see it, but says I have no rights to access the content.

    i use user 'nextcloud' configured as system user through OMV GUI, the share is present through samba, the user is owner of the shared folder and has full rights. Do I access the share with Nautilus or Windows Explorer using the user, everything works. There is no difference in specifying (OMV IP) or Docker IP, same thing.

    Is it possible to mount Samba shares from the host within nextcloud docker through the external storage plugin?

    I have an share, lets call it 'example' on my host with, shared folder 'example' and all its subfolders is owned by user 'nextcloud', who has all privileges on it. Do I mount this share within nextcloud (host ip, shared folder 'example' global access with user 'nextcloud') the setup indicates that data is correct and share is reachable, but on opening I can not access any data within this share. At first I thought it was an permission issue or a connection, but both seem to be right. I do not want to run the container in privileged mode; which Capability Key is required?

    Any suggestions?

    I think I have more a folder- and/or redirection problem, since I do not use or, but instead directly.

    Using internal port 81 and 444 enables another container (for example nextcloud) to have 443 or 80 to bypass the proxy. But I do not need this.

    Besides ... does the linuxserver.nextcould support redis through php-fpm-module?

    Tried setting up a redis-docker and use

    'memcache.local' => '\\OC\\Memcache\\APCu',
    'memcache.locking' => '\\OC\\Memcache\\Redis',
    'redis' =>
    array (
    'host' => 'my-ip',
    'port' => 6379,

    Edit: redis is running with this code, just takes a couple minutes to see first connections with

    redis-cli monitor

    For testing I tried using subdomain and subfolder-method. On both I get

    502 Bad Gateway










    nextcloud by itself with just

    'trusted_domains' =>
    array (
    0 => '',
    1 => '',

    works, but without CERT.

    For tests with subdomain i stick exactly to the howto and I setup a CNAME pointing to

    Letsencrypt Logs:


    2020/05/21 00:27:56 [error] 404#404: *1 nextcloud could not be resolved (110: Operation timed out), client:, server: _, request: "GET /nextcloud/ HTTP/2.0", host: ""

    Despite all container are bridged and member of net


    nextcloud letsencrypt

    running - linuxserver/nextcloud:latest 2020-05-21 14:15:08 443:443 80:80 administrators
    running - linuxserver/letsencrypt:latest 2020-05-20 22:41:04 81:80 444:443 administrators



    nextcloud.subfolders.conf at

    proxy_pass $upstream_proto://$upstream_port;

    and the

    config.php to

    'trusted_domains' =>
    array (
    0 => '',
    1 => '',

    solved the 502 Bad Gateway problem, but still, its subdirectory and not the domain itself.