Remote Desktop - xfce4 - is not running because of wrong permissions

    • OMV 4.x
    • Remote Desktop - xfce4 - is not running because of wrong permissions

      Hello,

      yesterday I've installed xfce4 and wanted to connect to IP-Server:3389 but it's not working.
      Under syslog I found this error message:
      xrdp (some figures)[ERROR] Cannot read private key file /etc/xrdp/key.pem:Permission denied

      under www I found the info that adding xrdp to the ssl-cert group will fix this issue.

      Unfortunately I don't know how to add xrdp to this group.

      How can I solve this issue?

      My server is in the signature.

      Thanks in advance
      OMV-Server-HW: MoBo Fujitsu D3417-B2 (Intel-LAN), Intel Xeon E3-1245 v6 Kaby Lake (4x3.70GHz), 16GB-Ram ECC UDIMM, 1x512GB SSD Samsung 850 Pro (sda2 - 30GB system, 4GB swap, sda5/rest - for work), 1x 10TB WD Red Pro, 1x 3TB WD Red (both basic setup) - Digibit R1 Sat-IP-Server with SatIP-Axe-Firmware

      OMV-Server-SW: Debian Stretch with backports-Kernel (always up-to-date), OMV v4 (always latest), omv-extras-plugin (always latests), AutoShutdown-Plugin, Virtualbox (with DSM 6.2.x), Docker with PlexMediaServer, TVHeadendServer (unstable release)

      BackupServer: Synology DS1010+ with 4GB Ram, 9TB@SHR (different hdd's), DSM 5.2-5967-2
    • Huberer wrote:

      How can I solve this issue?
      While that error is in syslog (I have it too and xrdp is working fine), that is not what is causing your problem of xrdp not working. Is the login screen coming up or is it not listening at all? No working isn't enough detail.
      omv 4.1.13 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • No, I can't login. When I try to open IP-AdressServer:3389 I get the message that the browser can't connect.
      Should Remote Desktop show up under services (where the others like ASP, Docker, ftp,... are)? I don't have it under services

      OMV-Server-HW: MoBo Fujitsu D3417-B2 (Intel-LAN), Intel Xeon E3-1245 v6 Kaby Lake (4x3.70GHz), 16GB-Ram ECC UDIMM, 1x512GB SSD Samsung 850 Pro (sda2 - 30GB system, 4GB swap, sda5/rest - for work), 1x 10TB WD Red Pro, 1x 3TB WD Red (both basic setup) - Digibit R1 Sat-IP-Server with SatIP-Axe-Firmware

      OMV-Server-SW: Debian Stretch with backports-Kernel (always up-to-date), OMV v4 (always latest), omv-extras-plugin (always latests), AutoShutdown-Plugin, Virtualbox (with DSM 6.2.x), Docker with PlexMediaServer, TVHeadendServer (unstable release)

      BackupServer: Synology DS1010+ with 4GB Ram, 9TB@SHR (different hdd's), DSM 5.2-5967-2
    • Huberer wrote:

      Should Remote Desktop show up under services (where the others like ASP, Docker, ftp,... are)? I don't have it under services
      Nope.

      What is the output of: dpkg -l | grep openm
      omv 4.1.13 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Here is the output:

      Source Code

      1. root@OMV-HomeServer:~# dpkg -l | grep openm
      2. ii openmediavault 4.1.12 all openmediavault - The open network attached storage solution
      3. ii openmediavault-autoshutdown 4.0.4 all OpenMediaVault AutoShutdown Plugin
      4. ii openmediavault-docker-gui 4.0.1 all OpenMediaVault plugin for Docker
      5. ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive
      6. ii openmediavault-omvextrasorg 4.1.11 all OMV-Extras.org Package Repositories for OpenMediaVault
      7. ii openmediavault-remotedesktop 4.0.1 all Remote desktop plugin for OpenMediaVault.
      8. ii openmediavault-remotemount 4.0.5 all Remote mount plugin for OpenMediaVault.
      9. ii openmediavault-virtualbox 4.1 all VirtualBox plugin for OpenMediaVault.
      10. root@OMV-HomeServer:~#
      Today I've made a brand new installation of OMV. Still no chance to connect to Remote Desktop

      What does this mean unter "Remote Desktop":

      Connecting user must have existing home directory.

      I've created a shared folder and added the user to it:



      But this didn't help
      OMV-Server-HW: MoBo Fujitsu D3417-B2 (Intel-LAN), Intel Xeon E3-1245 v6 Kaby Lake (4x3.70GHz), 16GB-Ram ECC UDIMM, 1x512GB SSD Samsung 850 Pro (sda2 - 30GB system, 4GB swap, sda5/rest - for work), 1x 10TB WD Red Pro, 1x 3TB WD Red (both basic setup) - Digibit R1 Sat-IP-Server with SatIP-Axe-Firmware

      OMV-Server-SW: Debian Stretch with backports-Kernel (always up-to-date), OMV v4 (always latest), omv-extras-plugin (always latests), AutoShutdown-Plugin, Virtualbox (with DSM 6.2.x), Docker with PlexMediaServer, TVHeadendServer (unstable release)

      BackupServer: Synology DS1010+ with 4GB Ram, 9TB@SHR (different hdd's), DSM 5.2-5967-2
    • Huberer wrote:

      What does this mean unter "Remote Desktop":
      If the user doesn't have a home directory, they won't be able to connect. The xrdp service will still be listening though.

      The plugin is very simple. I have no idea why it isn't working on your system. What is the output of:

      systemctl status xrdp.service
      systemctl status xrdp-sesman.service
      omv 4.1.13 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • So, as I wrote, I've created a home directory for the user.

      Here are the outputs of:

      systemctl status xrdp.service

      Source Code

      1. ● xrdp.service - xrdp daemon
      2. Loaded: loaded (/lib/systemd/system/xrdp.service; enabled; vendor preset: enabled)
      3. Active: active (running) since Sun 2018-10-28 19:41:04 CET; 1 day 2h ago
      4. Docs: man:xrdp(8)
      5. man:xrdp.ini(5)
      6. Main PID: 1205 (xrdp)
      7. Tasks: 1 (limit: 4915)
      8. Memory: 1.8M
      9. CPU: 9ms
      10. CGroup: /system.slice/xrdp.service
      11. └─1205 /usr/sbin/xrdp
      12. Okt 28 19:41:03 OMV-HomeServer systemd[1]: Starting xrdp daemon...
      13. Okt 28 19:41:03 OMV-HomeServer systemd[1]: xrdp.service: PID file /var/run/xrdp/xrdp.pid not readable (yet?) after start: No such file or directory
      14. Okt 28 19:41:04 OMV-HomeServer systemd[1]: Started xrdp daemon.
      Display All

      and of

      systemctl status xrdp-sesman.service




      Source Code

      1. ● xrdp-sesman.service - xrdp session manager
      2. Loaded: loaded (/lib/systemd/system/xrdp-sesman.service; enabled; vendor preset: enabled)
      3. Active: active (running) since Sun 2018-10-28 19:41:03 CET; 1 day 2h ago
      4. Docs: man:xrdp-sesman(8)
      5. man:sesman.ini(5)
      6. Main PID: 1085 (xrdp-sesman)
      7. Tasks: 1 (limit: 4915)
      8. Memory: 1.3M
      9. CPU: 2ms
      10. CGroup: /system.slice/xrdp-sesman.service
      11. └─1085 /usr/sbin/xrdp-sesman
      12. Okt 28 19:41:03 OMV-HomeServer systemd[1]: Starting xrdp session manager...
      13. Okt 28 19:41:03 OMV-HomeServer xrdp-sesman[979]: (979)(139672806171968)[DEBUG] libscp initialized
      14. Okt 28 19:41:03 OMV-HomeServer xrdp-sesman[979]: (979)(139672806171968)[DEBUG] Testing if xrdp-sesman can listen on 127.0.0.1 port 3350.
      15. Okt 28 19:41:03 OMV-HomeServer xrdp-sesman[979]: (979)(139672806171968)[DEBUG] Closed socket 1 (AF_INET6 ::1 port 3350)
      16. Okt 28 19:41:03 OMV-HomeServer xrdp-sesman[1085]: (1085)(139672806171968)[INFO ] starting xrdp-sesman with pid 1085
      17. Okt 28 19:41:03 OMV-HomeServer systemd[1]: Started xrdp session manager.
      18. Okt 28 19:41:03 OMV-HomeServer xrdp-sesman[1085]: (1085)(139672806171968)[INFO ] listening to port 3350 on 127.0.0.1
      Display All



      I hope this can help you further
      OMV-Server-HW: MoBo Fujitsu D3417-B2 (Intel-LAN), Intel Xeon E3-1245 v6 Kaby Lake (4x3.70GHz), 16GB-Ram ECC UDIMM, 1x512GB SSD Samsung 850 Pro (sda2 - 30GB system, 4GB swap, sda5/rest - for work), 1x 10TB WD Red Pro, 1x 3TB WD Red (both basic setup) - Digibit R1 Sat-IP-Server with SatIP-Axe-Firmware

      OMV-Server-SW: Debian Stretch with backports-Kernel (always up-to-date), OMV v4 (always latest), omv-extras-plugin (always latests), AutoShutdown-Plugin, Virtualbox (with DSM 6.2.x), Docker with PlexMediaServer, TVHeadendServer (unstable release)

      BackupServer: Synology DS1010+ with 4GB Ram, 9TB@SHR (different hdd's), DSM 5.2-5967-2
    • Not sure why I didn't think of this early but I'm guessing you don't have backports enabled. What is the output of: dpkg -l | grep xrdp
      omv 4.1.13 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • @ryecoaaron

      this is the output of dpkg -l | grep xrdp

      Source Code

      1. root@OMV-HomeServer:~# dpkg -l | grep xrdp
      2. ii xorgxrdp 0.9.1-9+deb9u3 amd64 Remote Desktop Protocol (RDP) modules for X.org
      3. ii xrdp 0.9.8-2~bpo9+1 amd64 Remote Desktop Protocol (RDP) server
      I have backports enabled. Just see here:


      OMV-Server-HW: MoBo Fujitsu D3417-B2 (Intel-LAN), Intel Xeon E3-1245 v6 Kaby Lake (4x3.70GHz), 16GB-Ram ECC UDIMM, 1x512GB SSD Samsung 850 Pro (sda2 - 30GB system, 4GB swap, sda5/rest - for work), 1x 10TB WD Red Pro, 1x 3TB WD Red (both basic setup) - Digibit R1 Sat-IP-Server with SatIP-Axe-Firmware

      OMV-Server-SW: Debian Stretch with backports-Kernel (always up-to-date), OMV v4 (always latest), omv-extras-plugin (always latests), AutoShutdown-Plugin, Virtualbox (with DSM 6.2.x), Docker with PlexMediaServer, TVHeadendServer (unstable release)

      BackupServer: Synology DS1010+ with 4GB Ram, 9TB@SHR (different hdd's), DSM 5.2-5967-2
    • Those are the right versions. Not sure why it isn't working. Maybe purge the plugin and reinstall?
      omv 4.1.13 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Remote Desktop - xfce4 - is not running because of wrong permissions

      Should I purge it via CLI or via OMV GUI? What is the better way to do it?

      I‘m right now on vacation and can test it not before next Monday


      Gesendet von iPhone mit Tapatalk
      OMV-Server-HW: MoBo Fujitsu D3417-B2 (Intel-LAN), Intel Xeon E3-1245 v6 Kaby Lake (4x3.70GHz), 16GB-Ram ECC UDIMM, 1x512GB SSD Samsung 850 Pro (sda2 - 30GB system, 4GB swap, sda5/rest - for work), 1x 10TB WD Red Pro, 1x 3TB WD Red (both basic setup) - Digibit R1 Sat-IP-Server with SatIP-Axe-Firmware

      OMV-Server-SW: Debian Stretch with backports-Kernel (always up-to-date), OMV v4 (always latest), omv-extras-plugin (always latests), AutoShutdown-Plugin, Virtualbox (with DSM 6.2.x), Docker with PlexMediaServer, TVHeadendServer (unstable release)

      BackupServer: Synology DS1010+ with 4GB Ram, 9TB@SHR (different hdd's), DSM 5.2-5967-2
    • Huberer wrote:

      Should I purge it via CLI or via OMV GUI? What is the better way to do it?
      Either one should be ok.
      omv 4.1.13 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • So, back from vacation I did it again. I removed remote-desktop via OMV GUI (but before I've updated everything to be on the latest level), rebooted the server and installed it again via GUI.

      while installation I got these messages (I only started with the suspicious lines):

      Source Code

      1. insserv: warning: script 'S99startvm' missing LSB tags and overrides
      2. insserv: warning: script 'startvm' missing LSB tags and overrides
      3. insserv: There is a loop between service monit and rpcbind if started
      4. insserv: loop involving service rpcbind at depth 4
      5. insserv: loop involving service networking at depth 3
      6. insserv: There is a loop between service startvm and udev if started
      7. insserv: loop involving service udev at depth 1
      8. insserv: There is a loop at service monit if started
      9. insserv: Starting startvm depends on monit and therefore on system facility `$all' which can not be true!
      10. ..this last line was repeated around 20 times...
      11. insserv: Starting startvm depends on monit and therefore on system facility `$all' which can not be true!
      12. insserv: Max recursions depth 99 reached
      13. insserv: loop involving service docker at depth 1
      14. insserv: Starting startvm depends on monit and therefore on system facility `$all' which can not be true!
      15. ...another repeat of the last line around 20 times...
      16. insserv: There is a loop between service startvm and mountall if started
      17. Created symlink /etc/systemd/system/multi-user.target.wants/xrdp-sesman.service -> /lib/systemd/system/xrdp-sesman.service.
      18. Created symlink /etc/systemd/system/multi-user.target.wants/xrdp.service -> /lib/systemd/system/xrdp.service.
      19. Processing triggers for systemd (232-25+deb9u4) ...
      20. Setting up libwnck-common (2.30.7-5.1) ...
      21. Setting up libupower-glib3:amd64 (0.99.4-4+b1) ...
      22. Setting up libfontenc1:amd64 (1:1.1.3-1+b2) ...
      23. Setting up libpciaccess0:amd64 (0.13.4-1+b2) ...
      24. Processing triggers for man-db (2.7.6.1-2) ...
      25. Setting up libgudev-1.0-0:amd64 (230-3) ...
      26. Processing triggers for openmediavault (4.1.13-1) ...
      27. Restarting engine daemon ...
      28. Processing triggers for hicolor-icon-theme (0.15-1) ...
      29. Setting up libexo-helpers (0.10.7-1) ...
      30. Setting up libexif12:amd64 (0.6.21-2+b2) ...
      31. Setting up libpolkit-gobject-1-0:amd64 (0.105-18) ...
      32. Processing triggers for fontconfig (2.11.0-6.7+b1) ...
      33. Setting up libxklavier16:amd64 (5.4-2) ...
      34. Setting up libkeybinder-3.0-0:amd64 (0.3.1-1) ...
      35. Setting up libgtk2.0-0:amd64 (2.24.31-2) ...
      36. Setting up xserver-common (2:1.19.2-1+deb9u4) ...
      37. Setting up libwnck22:amd64 (2.30.7-5.1) ...
      38. Setting up libxfont2:amd64 (1:2.0.1-3+deb9u1) ...
      39. Setting up xserver-xorg-core (2:1.19.2-1+deb9u4) ...
      40. Setting up libxfont1:amd64 (1:1.5.2-4) ...
      41. Setting up tigervnc-standalone-server (1.7.0+dfsg-7) ...
      42. update-alternatives: using /usr/bin/tigervncserver to provide /usr/bin/vncserver (vncserver) in auto mode
      43. update-alternatives: using /usr/bin/Xtigervnc to provide /usr/bin/Xvnc (Xvnc) in auto mode
      44. Setting up libxfce4util7:amd64 (4.12.1-3) ...
      45. Setting up orage (4.12.1-3) ...
      46. Setting up gtk2-engines-xfce (3.2.0-2) ...
      47. Setting up libxfce4panel-2.0-4 (4.12.1-2) ...
      48. Setting up xorgxrdp (0.9.1-9+deb9u3) ...
      49. Setting up xfonts-utils (1:7.7+4) ...
      50. Setting up xfconf (4.12.1-1) ...
      51. Setting up libxfconf-0-2 (4.12.1-1) ...
      52. Setting up libxfce4ui-1-0 (4.12.1-2) ...
      53. Setting up xfonts-base (1:1.0.4+nmu1) ...
      54. Setting up libexo-1-0:amd64 (0.10.7-1) ...
      55. Setting up xfwm4 (4.12.4-1) ...
      56. update-alternatives: using /usr/bin/xfwm4 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
      57. Setting up exo-utils (0.10.7-1) ...
      58. Setting up libxfce4ui-2-0 (4.12.1-2) ...
      59. Setting up libxfce4ui-utils (4.12.1-2) ...
      60. Setting up libgarcon-1-0 (0.4.0-2) ...
      61. Setting up libthunarx-2-0 (1.6.11-1) ...
      62. Setting up xfce4-appfinder (4.12.0-2) ...
      63. Setting up xfce4-settings (4.12.1-1) ...
      64. Setting up xfce4-panel (4.12.1-2) ...
      65. Setting up xfdesktop4 (4.12.3-3) ...
      66. Setting up xfce4-pulseaudio-plugin:amd64 (0.2.4-1) ...
      67. Setting up xfce4-session (4.12.1-5) ...
      68. update-alternatives: using /usr/bin/startxfce4 to provide /usr/bin/x-session-manager (x-session-manager) in auto mode
      69. Setting up thunar (1.6.11-1) ...
      70. Setting up xfce4 (4.12.3) ...
      71. Setting up openmediavault-remotedesktop (4.0.1) ...
      72. Processing triggers for libc-bin (2.24-11+deb9u3) ...
      73. Processing triggers for openmediavault (4.1.13-1) ...
      74. Updating locale files ...
      75. Updating file permissions ...
      76. Purging internal cache ...
      77. Restarting engine daemon ...
      78. Fertig ...
      Display All
      After installation I rebooted the server again and tried to connect via IP-Server:3389 and still the same error. No connection to IP-Server:3389 possible X(

      Don't know why it's not working.
      OMV-Server-HW: MoBo Fujitsu D3417-B2 (Intel-LAN), Intel Xeon E3-1245 v6 Kaby Lake (4x3.70GHz), 16GB-Ram ECC UDIMM, 1x512GB SSD Samsung 850 Pro (sda2 - 30GB system, 4GB swap, sda5/rest - for work), 1x 10TB WD Red Pro, 1x 3TB WD Red (both basic setup) - Digibit R1 Sat-IP-Server with SatIP-Axe-Firmware

      OMV-Server-SW: Debian Stretch with backports-Kernel (always up-to-date), OMV v4 (always latest), omv-extras-plugin (always latests), AutoShutdown-Plugin, Virtualbox (with DSM 6.2.x), Docker with PlexMediaServer, TVHeadendServer (unstable release)

      BackupServer: Synology DS1010+ with 4GB Ram, 9TB@SHR (different hdd's), DSM 5.2-5967-2
    • Huberer wrote:

      Don't know why it's not working.
      Your startvm service (older init script?) looks like it is causing the problem.
      omv 4.1.13 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      Your startvm service (older init script?) looks like it is causing the problem.
      and how can I update it?
      I've installed OMV about 3 weeks ago. I always install latest Debian 9 netinstaller (because of manual partitioning the system drive) and OMV (v4) over it. Could this be the issue why it't not working?
      OMV-Server-HW: MoBo Fujitsu D3417-B2 (Intel-LAN), Intel Xeon E3-1245 v6 Kaby Lake (4x3.70GHz), 16GB-Ram ECC UDIMM, 1x512GB SSD Samsung 850 Pro (sda2 - 30GB system, 4GB swap, sda5/rest - for work), 1x 10TB WD Red Pro, 1x 3TB WD Red (both basic setup) - Digibit R1 Sat-IP-Server with SatIP-Axe-Firmware

      OMV-Server-SW: Debian Stretch with backports-Kernel (always up-to-date), OMV v4 (always latest), omv-extras-plugin (always latests), AutoShutdown-Plugin, Virtualbox (with DSM 6.2.x), Docker with PlexMediaServer, TVHeadendServer (unstable release)

      BackupServer: Synology DS1010+ with 4GB Ram, 9TB@SHR (different hdd's), DSM 5.2-5967-2
    • @ryecoaaron

      I have to add something to my tread above (don't want to edit it, because it should not disappear).
      You wrote about "startvm"
      Could it be that I've made a startvm-script described here. I need this startvm otherwise my VM doesn't start
      OMV-Server-HW: MoBo Fujitsu D3417-B2 (Intel-LAN), Intel Xeon E3-1245 v6 Kaby Lake (4x3.70GHz), 16GB-Ram ECC UDIMM, 1x512GB SSD Samsung 850 Pro (sda2 - 30GB system, 4GB swap, sda5/rest - for work), 1x 10TB WD Red Pro, 1x 3TB WD Red (both basic setup) - Digibit R1 Sat-IP-Server with SatIP-Axe-Firmware

      OMV-Server-SW: Debian Stretch with backports-Kernel (always up-to-date), OMV v4 (always latest), omv-extras-plugin (always latests), AutoShutdown-Plugin, Virtualbox (with DSM 6.2.x), Docker with PlexMediaServer, TVHeadendServer (unstable release)

      BackupServer: Synology DS1010+ with 4GB Ram, 9TB@SHR (different hdd's), DSM 5.2-5967-2
    • Huberer wrote:

      Could it be that I've made a startvm-script described
      Yes. That script doesn't have init script headers. And there is still something going on with your system if the VMs don't start when set to automatic start in the phpvirtualbox (VM -> Settings -> General -> Basic -> Startup Mode = Automatic)
      omv 4.1.13 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Ok, I've removed the startvm-script, rebooted the server and installed remote-desktop again. No error while installation but also no connection to the RDP. Also no autostart of the VM (as it was before).
      Removed RDP and rebooted the server again. Still no VM running. I had to manual start it.

      So I installed the startvm-script again, inserted a init-script-header, installed RDP. No error-message while installation but no access to RDP-GUI. VM started as usual.
      Even changing the port of the RDP didn't help. So I think that RDP is not working on my system.
      OMV-Server-HW: MoBo Fujitsu D3417-B2 (Intel-LAN), Intel Xeon E3-1245 v6 Kaby Lake (4x3.70GHz), 16GB-Ram ECC UDIMM, 1x512GB SSD Samsung 850 Pro (sda2 - 30GB system, 4GB swap, sda5/rest - for work), 1x 10TB WD Red Pro, 1x 3TB WD Red (both basic setup) - Digibit R1 Sat-IP-Server with SatIP-Axe-Firmware

      OMV-Server-SW: Debian Stretch with backports-Kernel (always up-to-date), OMV v4 (always latest), omv-extras-plugin (always latests), AutoShutdown-Plugin, Virtualbox (with DSM 6.2.x), Docker with PlexMediaServer, TVHeadendServer (unstable release)

      BackupServer: Synology DS1010+ with 4GB Ram, 9TB@SHR (different hdd's), DSM 5.2-5967-2
    • Huberer wrote:

      lso no autostart of the VM (as it was before).
      Removed RDP and rebooted the server again. Still no VM running. I had to manual start it.
      It is set to automatic in phpvirtualbox?

      Huberer wrote:

      So I installed the startvm-script again, inserted a init-script-header, installed RDP. No error-message while installation but no access to RDP-GUI. VM started as usual.
      Even changing the port of the RDP didn't help. So I think that RDP is not working on my system.
      If the systemctl status says they are running, I would like to see the output of: netstat -tulpn | grep 3389
      omv 4.1.13 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • So, I installed my new Odroid HC1 with latest OMV v4 (via armbian) and also installed remote-desktop
      Here is the output of:

      netstat -tulpn | grep 3389

      Mainserver (see signature)

      Source Code

      1. root@OMV-HomeServer:~# netstat -tulpn | grep 3389
      2. tcp6 0 0 :::3389 :::* LISTEN 1262/xrdp
      3. root@OMV-HomeServer:~#

      and from the Odroid HC1

      Source Code

      1. root@OdroidHC1:~# netstat -tulpn | grep 3389
      2. tcp6 0 0 :::3389 :::* LISTEN 4482/xrdp
      3. root@OdroidHC1:~#


      and what is the result?
      On both machines (with different IP's) I don't have access to the GUI.
      OMV-Server-HW: MoBo Fujitsu D3417-B2 (Intel-LAN), Intel Xeon E3-1245 v6 Kaby Lake (4x3.70GHz), 16GB-Ram ECC UDIMM, 1x512GB SSD Samsung 850 Pro (sda2 - 30GB system, 4GB swap, sda5/rest - for work), 1x 10TB WD Red Pro, 1x 3TB WD Red (both basic setup) - Digibit R1 Sat-IP-Server with SatIP-Axe-Firmware

      OMV-Server-SW: Debian Stretch with backports-Kernel (always up-to-date), OMV v4 (always latest), omv-extras-plugin (always latests), AutoShutdown-Plugin, Virtualbox (with DSM 6.2.x), Docker with PlexMediaServer, TVHeadendServer (unstable release)

      BackupServer: Synology DS1010+ with 4GB Ram, 9TB@SHR (different hdd's), DSM 5.2-5967-2