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

    • OMV 4.x
  • Huberer
    • #1

    Hullo,

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

    under www I plant the info that adding xrdp to the ssl-cert grouping will fix this consequence.

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

    How tin can I solve this upshot?

    My server is in the signature.

    Thanks in accelerate

    • #2

    How tin I solve this issue?

    While that error is in syslog (I have it also and xrdp is working fine), that is non 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.

    • #3

    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 testify upwards nether services (where the others like ASP, Docker, ftp,... are)? I don't take it under services

    • #4

    Should Remote Desktop show up nether 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

    • #5

    Here is the output:

                                                                                        root@OMV-HomeServer:~# dpkg -l | grep openm                                                                                                                    2  openmediavault                      iv.1.12                                   all          openmediavault - The open network fastened storage solution                                                                                                                    ii  openmediavault-autoshutdown         4.0.4                                    all          OpenMediaVault AutoShutdown Plugin                                                                                                                    ii  openmediavault-docker-gui           four.0.1                                    all          OpenMediaVault plugin for Docker                                                                                                                    two  openmediavault-keyring              1.0                                      all          GnuPG archive keys of the OpenMediaVault archive                                                                                                                    ii  openmediavault-omvextrasorg         4.1.xi                                   all          OMV-Extras.org Package Repositories for OpenMediaVault                                                                                                                    two  openmediavault-remotedesktop        4.0.i                                    all          Remote desktop plugin for OpenMediaVault.                                                                                                                    ii  openmediavault-remotemount          4.0.5                                    all          Remote mount plugin for OpenMediaVault.                                                                                                                    ii  openmediavault-virtualbox           iv.i                                      all          VirtualBox plugin for OpenMediaVault.                                                                                                                    root@OMV-HomeServer:~#

    Today I've fabricated a brand new installation of OMV. Still no adventure to connect to Remote Desktop

    What does this hateful 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

    • #six

    What does this hateful unter "Remote Desktop":

    If the user doesn't accept a home directory, they won't be able to connect. The xrdp service will still be listening though.

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

    systemctl status xrdp.service
    systemctl status xrdp-sesman.service

    • #7

    And so, equally I wrote, I've created a home directory for the user.

    Here are the outputs of:

    systemctl status xrdp.service


    and of

    systemctl status xrdp-sesman.service

    I hope this can assistance yous farther

    • #eight

    Non sure why I didn't think of this early but I'm guessing you don't take backports enabled. What is the output of: dpkg -fifty | grep xrdp

    • #9

    @ryecoaaron

    this is the output of dpkg -l | grep xrdp 

                                                                                        root@OMV-HomeServer:~# dpkg -l | grep xrdp                                                                                                                    ii  xorgxrdp                            0.9.1-9+deb9u3                           amd64        Remote Desktop Protocol (RDP) modules for X.org                                                                                                                    ii  xrdp                                0.9.eight-two~bpo9+ane                           amd64        Remote Desktop Protocol (RDP) server

    I take backports enabled. Just see here:

    • #10

    Those are the right versions. Not sure why it isn't working. Perchance purge the plugin and reinstall?

    • #eleven

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

    I'yard right at present on holiday and tin can examination information technology not before next Monday

    Gesendet von iPhone mit Tapatalk

    • #12

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

    Either 1 should exist ok.

    • #xiii

    So, back from vacation I did it once again. I removed remote-desktop via OMV GUI (just earlier 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):

    After installation I rebooted the server over again and tried to connect via IP-Server:3389 and notwithstanding the same fault. No connection to IP-Server:3389 possible X(

    Don't know why information technology's non working.

    • #14

    Don't know why it'due south not working.

    Your startvm service (older init script?) looks like information technology is causing the problem.

    • #fifteen

    Your startvm service (older init script?) looks similar 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 information technology. Could this exist the upshot why information technology't not working?

    • #16

    @ryecoaaron

    I have to add together something to my tread above (don't want to edit it, considering it should not disappear).
    You wrote about "startvm"
    Could it be that I've made a startvm-script described here . I demand this startvm otherwise my VM doesn't start

    • #17

    Could it exist that I've made a startvm-script described

    Yep. That script doesn't have init script headers. And there is withal something going on with your organisation if the VMs don't start when set to automatic start in the phpvirtualbox (VM -> Settings -> Full general -> Basic -> Startup Mode = Automatic)

    • #18

    Ok, I've removed the startvm-script, rebooted the server and installed remote-desktop again. No fault while installation just also no connection to the RDP. Also no autostart of the VM (as it was earlier).
    Removed RDP and rebooted the server again. Withal no VM running. I had to transmission first it.

    So I installed the startvm-script again, inserted a init-script-header, installed RDP. No error-message while installation but no admission to RDP-GUI. VM started as usual.
    Even changing the port of the RDP didn't help. Then I think that RDP is not working on my system.

    • #19

    lso no autostart of the VM (equally information technology was earlier).
    Removed RDP and rebooted the server once again. Even so no VM running. I had to transmission start it.

    It is set to automated in phpvirtualbox?

    So I installed the startvm-script again, inserted a init-script-header, installed RDP. No fault-bulletin while installation but no admission to RDP-GUI. VM started as usual.
    Even changing the port of the RDP didn't help. And so I recollect that RDP is not working on my arrangement.

    If the systemctl condition says they are running, I would like to come across the output of: netstat -tulpn | grep 3389

    • #xx

    So, I installed my new Odroid HC1 with latest OMV v4 (via armbian) and too installed remote-desktop
    Here is the output of:

    netstat -tulpn | grep 3389

    Mainserver (come across signature)

                                                                                        root@OMV-HomeServer:~# netstat -tulpn | grep 3389                                                                                                                    tcp6       0      0 :::3389                 :::*                    Heed      1262/xrdp                                                                                                                    root@OMV-HomeServer:~#


    and from the Odroid HC1

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

    and what is the effect?
    On both machines (with dissimilar IP's) I don't accept access to the GUI.