Beiträge von Nefertiti

root@rockpro64:~# cat /etc/docker/daemon.json

{

"data-root": "/dev-disk-by-uuid-a8d62abf-6358-488e-9239-7e1e82738c84/docker"

witch is in the root directory!

Zitat von gderf

Post the contents of this file:

/etc/docker/daemon.json

root@rockpro64:~# /etc/docker/daemon.json

-bash: /etc/docker/daemon.json: Permission denied

I think I did as you can see in the picts

Well with

/dev-disk-by-uuid-a8d62abf-6358-488e-9239-7e1e82738c84/docker

portainer opened but no previous container to be found

Yes I figure it since this is the new norm https://www.openmediavault.org/?p=2866 but the issue now portainer says site cannot be reached even after a new portainer install

Sorry again I did /srv/dev-disk-by-uuid-a8d62abf-6358-488e-9239-7e1e82738c84/docker

instead of

/dev-disk-by-uuid-a8d62abf-6358-488e-9239-7e1e82738c84/docker

Sorry just found it !!

dev-disk-by-uuid-a8d62abf-6358-488e-9239-7e1e82738c84

and

dev-disk-by-uuid-9cd27ed0-ef9a-4346-ae1e-5e835ba05832

First one is WD_10TB_1

Second one is Segate16T

How to fix it ?

I got none

Sorry I do not understand they use exactly the same dev-disk-by-label-WD_10TB_1 in two different installs

Zitat von gderf

Verify that the specified directory really exists and contains the data. (Your mount points may have changed from by-label to by-UUID)

I think it is the problem I just tried with yacht got the same issue, when I use a previous install everything is there in /srv/dev-disk-by-label-WD_10TB_1/

but with the new install /srv/dev-disk-by-label-WD_10TB_1/ is empty except the new docker just created

So what is the solution?

On a new install, what would be the proper way for portainer to connect to an existing set of container at

/srv/dev-disk-by-label-WD_10TB_1/docker

although i entered the correct path in docker storage for some reason portainer removed my set of containers and installed a new portainer container with nothing else ! fortunately I was able to put back my old container (backup)?

I was able to create a PW for portainer at the second login the PW does not allowed me to login, I removed portainer and recreate it no option for a new password.

So How to start from the page create password for portainer?

Woo!

Thank you

I am almost ashamed to post for help for something so basic! but anyway for some reasons I decided to do a new install OMV my rockpro

I login with admin but still get few items in the web interface like the user section of Access Rights Management.

and yes I cleared the cache and cookies of my browser even log in an incognito window?

To reply to myself I think I can add _netdev to

192.168.2.30:Media2_bis /mnt/movies nfs defaults,noatime 0 0

or 192.168.2.30:/export/Media2_bis/movies/mnt/movies nfs defaults,noatime 0 0

but I am not completely sure how to add this add this argument to the strings above?

https://unix.stackexchange.com…ab-mount-wait-for-network

Sometimes but not always I got an issue after a reboot, where persistent is not detected "fstab;

192.168.2.30:Media2_bis /mnt/movies nfs defaults,noatime 0 0"

and If I do not realize it right away, all my emby catalog directory is destroyed.

What should I do to make sure persistent is always working or and is there a way to prevent emby to start in this case, like restart policy On Faillure?

Finally was working for me in addition to the steps from @roundcubetwo just disabled Remote access in the browser

Can login at

https://plex.MYDOMAIN/web/inde…tent.movies&source=movies
Happy

## Version 2020/12/09
# make sure that your dns has a cname set for plex
# if plex is running in bridge mode and the container is named "plex", the below config should work as is
# if not, replace the line "set $upstream_app plex;" with "set $upstream_app <containername>;"
# or "set $upstream_app <HOSTIP>;" for host mode, HOSTIP being the IP address of plex
# in plex server settings, under network, fill in "Custom server access URLs" with your domain (ie. "https://plex.yourdomain.url:443")

server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name plex.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;
    proxy_redirect off;
    proxy_buffering off;

    # enable for ldap auth, fill in ldap details in ldap.conf
    #include /config/nginx/ldap.conf;

    # enable for Authelia
    #include /config/nginx/authelia-server.conf;
    location / {
        # 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
        #auth_request /auth;
        #error_page 401 =200 /ldaplogin;

        # enable for Authelia
        #include /config/nginx/authelia-location.conf;

        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_app plex;
        set $upstream_port 32400;
        set $upstream_proto http;
        proxy_pass https://192.168.2.40:32400;

        proxy_set_header X-Plex-Client-Identifier $http_x_plex_client_identifier;
        proxy_set_header X-Plex-Device $http_x_plex_device;
        proxy_set_header X-Plex-Device-Name $http_x_plex_device_name;
        proxy_set_header X-Plex-Platform $http_x_plex_platform;
        proxy_set_header X-Plex-Platform-Version $http_x_plex_platform_version;
        proxy_set_header X-Plex-Product $http_x_plex_product;
        proxy_set_header X-Plex-Token $http_x_plex_token;
        proxy_set_header X-Plex-Version $http_x_plex_version;
        proxy_set_header X-Plex-Nocache $http_x_plex_nocache;
        proxy_set_header X-Plex-Provides $http_x_plex_provides;
        proxy_set_header X-Plex-Device-Vendor $http_x_plex_device_vendor;
        proxy_set_header X-Plex-Model $http_x_plex_model;
    }
}

I tried to use and adapt plex.conf sample but contrary to all my other subdomain.conf , I cannot have it working I am using wildcard in letsencrypt

Is somebody can post a functional Plex subdomain.conf to help me a bit since I am kind of stuck!?

Letsencrypt was working good I duplicate my emby.conf for a plex.conf I restarted nothing is working!

nginx: [emerg] "ssl_session_timeout" directive is duplicate in /config/nginx/ssl.conf:4

According to this https://unix.stackexchange.com…ate-add-new-ssl-enabled-s I got a duplicate certificate

So How exactly can I resolve it ?

root@OMV-Dell:~# timedatectl | grep 'Time zone'
                Time zone: America/Los_Angeles (PST, -0800)
root@OMV-Dell:~# timedatectl
               Local time: Wed 2020-12-23 08:36:34 PST
           Universal time: Wed 2020-12-23 16:36:34 UTC
                 RTC time: Wed 2020-12-23 16:36:34
                Time zone: America/Los_Angeles (PST, -0800)
System clock synchronized: no
              NTP service: inactive
          RTC in local TZ: no

When I input TZ in the GUI it goes away as soon as I click update now.

using NTP server and save button look like it is sticking.

root@OMV-Dell:~# timedatectl
               Local time: Wed 2020-12-23 08:45:42 PST
           Universal time: Wed 2020-12-23 16:45:42 UTC
                 RTC time: Wed 2020-12-23 16:45:42
                Time zone: America/Los_Angeles (PST, -0800)
System clock synchronized: yes
              NTP service: inactive
          RTC in local TZ: no

I am getting ton of it in logs

OMV-Dell omv-engined[23374]: Unknown or deprecated time zone [tz=]. Please reconfigure your time zone settings.

so how to correct it?