Posts by Akeem

    If docker is not what you want to use for rdp you can select your environment with the command (as root)

    Code
    tasksel

    next you can :

    Code
    apt install xrdp tigervnc-standalone-server

    then you can connect from windows rdp (select xvnc not xorg)

    Thanks, I preferred this method because the danielguerra/ubuntu-xrdp image was also painfully slow for me, I'm not experienced enough to change the password in that docker without a step-by-step guide and would have taken more work to use as a file manager because the media shares aren't mounted.


    I did struggle to get it working; got some "VNC error - problem connecting - some problem" errors initially in the connection log. and had to

    Code
    mkhomedir_helper username

    to create the homedir where xrdp writes session settings.I also installed xorgxrdp.

    Sorry for the late reply. I used the static IP address on an older (non-VM) OMV machine which worked fine. Maybe I followed the guide you mentioned. The resasoning was that setting a static IP address below 100 frees up the DHCP assigned range above 100 and I could choose a memorable fixed IP address for the server(s).


    I just found out that the main reason for the OMV WebGUI being available for a couple of seconds during boot but then disappearing is/was the transmission/openVPN docker booting at the end of the startup process.
    So figuring out how to exclude all non-transmission data from the OpenVPN is my next step ;-)

    Disabling the static IPv4 option in the Interface page of the OMV Network configuration and relying on the DHCP of the router and the router option to "Always assign this network device the same IPv4 address" actually did the trick.


    Many thanks!

    When I reboot OMV ín the virtual machine, there is a very short (few sec) timeframe during the reboot process in which OMV actually ís reachable from outside the network. After these few seconds, ERR_CONNECTION_TIMED_OUT is back.
    Which makes me think there's a piece of OMV configuration which loads during boot which makes OMV services (& webgui) unreachable from an outside network.

    This article suggests that it's not the Windows firewall I should adapt, as I'm using Bridge mode:

    • The firewall software on your host computer isn’t blocking the connections. (This only applies to NAT mode with port forwarding – the host computer’s firewall doesn’t interfere in bridged networking mode.)

    and indeed, if I switch off the Windows firewall, I still can't access the OMV WebGUI from outside the network.


    I'm guessing, the OMV firewall won't block anything by default?


    I have the feeling I'm missing something obvious.

    I'm running OMV4 in virtualbox on a windows machine. The virtualbox network uses a bridged adapter, the OMV machine always receives the same IP address 192.168.0.115 from the router.
    I've put the WebGUI on port 6003 in general settings. And entered these details for IPv4 Interface: Method:static, Address:192.168.0.115, Netmask:255.255.255.0, default gateway 192.168.0.2(=router) and DNS 8.8.8.8


    On this windows machine, I can access the OMV WebGUI on 192.168.0.115:6003.


    I've enabled Port Forwarding on the router, directing TCP on port 6003 to 192.168.0.115 on port 6003.
    However, I'm unable to reach the webgui (or any other OMV service) through the <public IP address>:6003


    What extra steps should I take to make services running on OMV in a virtualbox reachable from outside the network?

    I renamed /opt/plexpy to /opt/Tautulli and ran through the daemon setup again: https://github.com/Tautulli/Ta…as-a-daemon#linux-systemd

    There are two commands which don't work for me on OMV v2.2.14 (Stone burner)


    # 4. Enable boot-time autostart with the following commands:
    # systemctl daemon-reload
    # systemctl enable tautulli.service


    -bash: systemctl: command not found


    Can I accomplish the same without systemctl or how would I make make systemctl work?

    I just received PMS 1.3.4 on OMV 2.2.13.
    Did I misunderstand the previous replies? I was under the impression that I would have to use OMV 3 to get PMS updates.
    Who should I thank for this?


    In the future, on amd64, is it possible to use the .deb package via the [please install manually]
    https://plex.tv/downloads/late…stro=ubuntu&X-Plex-Token=<xxxtokenxxx> link provided in plex.tv or should I only use the update package in the Update manager in OMV?

    I was wrong. Shell In A Box showed a result (while logging me out in the background)
    This is the Library\..\Plex media server\Media division:


    9.0G Cache
    0 Codecs
    0 Crash Reports
    86M Logs
    145G Media
    14G Metadata
    4.0K plexmediaserver.pid
    25M Plug-ins
    4.0G Plug-in Support
    4.0K Preferences.xml
    0 Scanners
    0 Thumbnails

    I have no idea how large my Library\..\Plex media server\Media is because I can't get a result from du -hs before the Shell In A Box timeout ..
    I'm guessing photos and series episodes take up more space than movies because each file has its own thumbnail.

    Press enable then go get a meal. It took quite a bit of time here to complete.


    For years I stayed away from the Plex plugin enable/disable button beacause it just appeared to fail, maybe an informative description next to this button "do not despair, enabling can take hours" would be useful?

    well, it appeared to work, but then I had the "will not play" issue mentioned here
    Plex issue...


    Disabling the plugin, re-enabling the plugin and waiting ~3hours (the time it takes to enable) solved it


    I always thought the re-enabling just failed, but after the remark of @gderf to "get a meal" after clicking enable, I finally waited long enough.
    During this ~3hours enabling, OMV stutters a bit and the user is is thrown out of the OMV GUI after that timeout, so this process is not very user friendly.


    For years I stayed away from the Plex plugin enable/disable button, maybe an informative description next to this button "do not despair, enabling can take hours" would be useful?

    after installation of plexmediaserver 1.0.0.2261-a0117e99e-debian through the update manager
    plex.tv server settings reports: Version 1.0.0.2261


    and
    root@OMV:~# dpkg -l | grep plex
    ii libmpc2:amd64 0.9-4 amd64 multiple precision complex floating-point library
    ii openmediavault-plexmediaserver 1.0.15 all OpenMediaVault Plex Media Server plugin
    ii plexmediaserver 1.0.0.2261-a17e99e-debian amd64 Plex Media Server for Linux
    root@OMV:~# apt-cache policy plexmediaserver
    plexmediaserver:
    Installed: 1.0.0.2261-a17e99e-debian
    Candidate: 1.0.0.2261-a17e99e-debian
    Version table:
    *** 1.0.0.2261-a17e99e-debian 0
    500 http://dh2k.omv-extras.org/debian/ plex-wheezy-mirror/main amd64 Packages
    100 /var/lib/dpkg/status
    root@OMV:~#



    I think this means everything's correct now.
    My sincere thanks to you guys.

    root@OMV:~# dpkg -l | grep plex
    ii libmpc2:amd64 0.9-4 amd64 multiple precision complex floating-point library
    ii openmediavault-plexmediaserver 1.0.15 all OpenMediaVault Plex Media Server plugin
    ii plexmediaserver 0.9.16.6.1993-5089475-debian amd64 Plex Media Server for Linux
    root@OMV:~#

    after apt-clean, a new update appears (I already installed 1.0.15):
    plexmediaserver 1.0.0.2261-a0117e99e-debian
    Plex media server for linux, 95MB
    maintained by Christian Svedin
    repo: omv-extras.org-plex-mirror/


    Can I install this one?

    root@OMV:~# apt-cache policy plexmediaserver
    plexmediaserver:
    Installed: 0.9.16.6.1993-5089475-debian
    Candidate: 0.9.16.6.1993-5089475-debian
    Version table:
    *** 0.9.16.6.1993-5089475-debian 0
    500 http://dh2k.omv-extras.org/debian/ plex-wheezy-mirror/main amd64 Packages
    100 /var/lib/dpkg/status
    root@OMV:~#

    root@OMV:~# dpkg -l | grep plex
    ii libmpc2:amd64 0.9-4 amd64 multiple precision complex floating-point library
    ii openmediavault-plexmediaserver 1.0.15 all OpenMediaVault Plex Media Server plugin
    ii plexmediaserver 0.9.16.6.1993-5089475-debian amd64 Plex Media Server for Linux
    root@OMV:~#


    OMV version 2.2.5 (Stone burner)
    Kernel 3.16-0.bpo.2-amd64