“Cannot detect any display running” even when using itself to try to connect

Forum / NoMachine for Linux / “Cannot detect any display running” even when using itself to try to connect

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #46172
    cchen2
    Participant

    I am using the free version of NoMachine, version 8.10.1, on Ubuntu 22.04, Gnome.

    I am trying to connect to the server from itself, as a test run. I don’t know if this would cause any issues, but I would assume it wouldn’t cause the issue of not being able to detect a display from it. If I should not do this I will try a different way.

    I looked around on the forum and I think the only one I found related said try a reboot, and it didn’t fix the problem. How can I diagnose what is wrong?

    Thank you.

    #46198
    Britgirl
    Participant

    I understand you are connecting to localhost. Can you send us the logs? See here for instructions and send them to forum[at]nomachine[dot]com. Please use the title of your topic in the subject of the email.

    https://kb.nomachine.com/DT07S00243

    #46263
    cchen2
    Participant

    Logs have been sent. The owner of the room went on a business trip at the worst time, and I had to wait for them to get back before I could physically access the computer again to use the GUI (hence the need for NoMachine).

    #46328
    Britgirl
    Participant

    Hi, logs show a lot of errors, but they also show that you have a Small Business Server Subscription file installed in a NoMachine server free edition package. From version 8, the product subscription file and the installed server type must match.

    You should install the Small Business Terminal Server package v8. Please install that, and start from this clean installation, then try to connect again. If you continue to have errors, resubmit the logs.

    Valid subscriptions are entitled to technical assistance from the support team, so please consider opening a support enquiry from the customer area. If you can’t access the customer area, please submit your issue to our team via the Report Issues link here: https://www.nomachine.com/report-an-issue

    #46347
    cchen2
    Participant

    We are trying to get a new version of NoMachine. Previously we had version 5 licensed as small business, but it was throwing errors (probably because the environment is significantly different now) so we are trying to get rid of the old one. Is this going to be an issue? if it is, how do I scrub the old licenses out and get this new version working? Thanks.

    #46351
    Britgirl
    Participant

    If you need the latest version of the software, please go to https://downloads.nomachine.com/download-enterprise/ and scroll down to the Small Business Terminal Server link and click to download. Provided your subscription licenses are valid, you can install that package.

    If your subscription has expired, please get in contact with the Sales Team (Go to Contact Us in the footer of the website).

    Please also consult this link article “How to upgrade NoMachine products v7 to v8” available here: https://kb.nomachine.com/AR12S01147. From version 8 onwards, there is only a single license file, server.lic, for each server side product. When replacing license 7 with the new v8 server.lic, the old node.lic file is simply ignored by server software v8 and no further actions are required.

    #46355
    cchen2
    Participant

    Currently we have installed the free version because we are fairly certain that it will fulfill our needs, although we will likely upgrade at some point in the future. I had already done a clean install with the new version, but I now realize I think I forgot to clean up the logs before getting new ones. Should I logrotate, re-gather logs, and resend?

    #46364
    Britgirl
    Participant

    If you are going to use the free NoMachine and not the SBTS which seems to be what you were using before, please install from scratch by first uninstalling completely first, removing traces of NoMachine etc, then reproduce the problem, send new logs of the affected session.

    #46420
    cchen2
    Participant

    After a clean install, and finding that some files didn’t get deleted, it now works again after a restart. I appreciate your assistance.

Viewing 9 posts - 1 through 9 (of 9 total)

This topic was marked as solved, you can't post.