Posts by Bambuleee

    Client: Windows 10, domainmember. domainname: dom
    OMV System: Hostname: omv01, ip 172.16.10.15, domain: dom


    I can see all my smb shares, when i type in \\omv01
    I can access all smb shares where guest access is configured via \\omv01\guestshare
    I have a share "test". Owner users.
    When i try to access \\omv01\test i'm promted for a password. Correct. I type in the credentials for "user1" and get an no access message.
    When i try \\172.16.10.15\test and type in the credentials for user1, it is working.
    omv01 has an dns entry (forward and ptr). Any ideas?

    I'm unsing a reverse proxy (sophos utm) for external access, but I want to use the cert internal (dns zone), It's working fine for omv01.

    Why you don't want to regenerate the cert on the new system?The new cert still have the same sub-domains with longer expiration date.

    I will try. I though it's not possible.


    Edit: works. thx

    Of course you have to sync. Kodi is syncing the informations about the movies etc etc to put it in the local database. ...the official emby plugin is called " Emby.Kodi Sync Queue"
    The problem is not that kodi synced my library, but when I startetd kodi I realised, that the library is empty.


    When you read my posting, you can see that I also have probvlems with a fresh emby installation. WITHOUT kodi. Just the emby server. It's not possible to add movies etc


    There are different errors in the serverlogs.
    It's a fresh omv installation!


    I have a strange problem.
    A few days ago, when I started Kodi and synced with emby, all movies and series are gone.
    I looked in the emby webinterface and there are 0 movies and 0 series.
    When I click "sync library" it happens nothing.


    I tried to give the mediafolder 777. Nothing.
    I set up a new omv installation. IN this installation (omv2) I mountet a nfs share from omv1 with the media files.
    This folder I added to my new emby installation. Sync -> nothing.
    This is the log from the new install.


    Any ideas?`I'm going crazy ;)

    Files

    • Log.txt

      (45.07 kB, downloaded 268 times, last: )

    It's not possible to start docker.


    service start docker
    -> starting docker: docker
    docker ps -a
    -> Cannot connect to the Docker daemon. Is the docker daemon running on this host?


    Edit: Docker.log says, that my Kernel 3.2.0-4amd64 is not supported.
    i will try again with backports.


    Edit2: Works! :thumbsup:

    I have a brand new OMV installation (2.2.13).
    When I install docker and activate it, I get this error:


    I even tried to change the port:



    Code
    Fehler #0:
    exception 'OMVModuleDockerException' with message 'Error: "couldn't connect to host" - Code: 7' in /usr/share/omvdocker/Utils.php:63
    Stack trace:
    #0 /usr/share/omvdocker/Utils.php(125): OMVModuleDockerUtil::doApiCall('http://localhos...')
    #1 /usr/share/openmediavault/engined/rpc/docker.inc(145): OMVModuleDockerUtil::getImages('12345', true)
    #2 [internal function]: OMVRpcServiceDocker->getImages(Array, Array)
    #3 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
    #4 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('getImages', Array, Array)
    #5 /usr/sbin/omv-engined(500): OMVRpc::exec('Docker', 'getImages', Array, Array, 1)
    #6 {main}

    New omv ystem. Docker is the first plugin I installed. It can reproduce the problem with another new installation.
    It's a VM on Hyper-V Server 2016.

    Actually I'm using OMV 2 set up in an VM on Hyper-V. Host is a HP Gen8.
    I have three disks directly passed through to omv and build a Raid 5 on it.


    Is it possible to set up a omv 3 installation and switch the disks over (omv 2 is shutdown) to test the plugins?
    Or will OMV 3 make changes, so that I can now use the filesystem on omv 2 again?

    Option 1 sounds great. I will try. THX


    Works fine. For everybody the cron:

    Code
    /etc/init.d/emby stop
    openssl pkcs12 -inkey /etc/letsencrypt/live/hostname.dyndns.de/privkey.pem -in /etc/letsencrypt/live/hostname.dyndns.de/fullchain.pem -export -out /media/balbla/emby/ssl/hostname.dyndns.de.pfx -passout pass:
    chown -c emby /media/blabla/emby/ssl/hostname.dyndns.de.pfx
    /etc/init.d/emby start