Is the Nx Cloud up? Visit our Status Page for the current health and performance of the Nx Cloud.

Status Page

Infinite Loading screen after connect

Answered
Permanently deleted user
Edited

Client is running Debian Bullseye.
Celeron NUC. Was working fine until it wasn't.There are 3 in production, 1 is misbehaving. Others are fine. These were all cloned.

After launching the program, you try to connect to the NX Server and get an infinite loading screen. Minimizing the client and maximizing it puts you back at the connect screen again. Only issue I can see in the log is following:

2021-11-18 13:37:59.285 1552 WARNING nx::vms::applauncher::InstallationManager(0x7ffebe09fc20): Can't find client binary in /home/user/.local/share/Network Optix/applauncher/default/bin

Edit:
Maybe an SSL issue?

2021-11-18 14:55:50.133   1253 VERBOSE nx::network::cloud::AnyAccessibleAddressConnector(0x7efbcc016860): Connecting to { direct:192.168.254.1({ port=7001 }) } with timeout 3001ms
2021-11-18 14:55:50.133   1253 VERBOSE nx::network::cloud::AnyAccessibleAddressConnector(0x7efbcc016860): Trying direct connection to 192.168.254.1:7001
2021-11-18 14:55:50.133   1253 VERBOSE nx::network::TCPSocket(0x7efbb800c000, 192.168.254.45:38844->192.168.254.1:7001): Connect to 192.168.254.1:7001 completed with result Success
2021-11-18 14:55:50.133   1253 VERBOSE nx::network::cloud::AnyAccessibleAddressConnector(0x7efbcc016860): Connection completed with result Success
2021-11-18 14:55:50.134   1253 VERBOSE nx::network::cloud::AnyAccessibleAddressConnector(0x7efbcc016860): Reporting connect success. Address { direct:192.168.254.1({ port=7001 }) }
2021-11-18 14:55:50.134   1253 VERBOSE nx::network::cloud::CloudStreamSocket(0x7efbcc015330): Connect completed with result 0
2021-11-18 14:55:50.134   1253 VERBOSE nx::network::cloud::CloudStreamSocket(0x7efbcc015330): Got connection to []
2021-11-18 14:55:50.134   1253 VERBOSE nx::network::http::AsyncClient(0x7efbcc008e88): Opened connection to url http://192.168.254.1:7001/api/moduleInformation?showAddresses=false&keepConnectionOpen&updateStream=10. Result code 0
2021-11-18 14:55:50.134   1253 VERBOSE nx::network::http::AsyncClient(0x7efbcc008e88): Sending request to url http://192.168.254.1:7001/api/moduleInformation?showAddresses=false&keepConnectionOpen&updateStream=10
2021-11-18 14:55:50.134   1253 VERBOSE nx::network::http::AsyncClient(0x7efbcc008e88): Request has been successfully sent to http://192.168.254.1:7001/api/moduleInformation?showAddresses=false&keepConnectionOpen&updateStream=10 from 192.168.254.45:38844. GET /api/moduleInformation?showAddresses=false&keepConnectionOpen&updateStream=10 HTTP/1.1

2021-11-18 14:55:50.134   1253 VERBOSE nx::network::http::AsyncClient(0x7efbcc008e88): Waiting for response. Timeout 3002ms
2021-11-18 14:55:50.135   1253 VERBOSE nx::network::http::AsyncClient(0x7efbcc008e88): Response header from http://192.168.254.1:7001/api/moduleInformation?showAddresses=false&keepConnectionOpen&updateStream=10 has been successfully read: HTTP/1.1 301 Moved Permanently

2021-11-18 14:55:50.136   1253 VERBOSE nx::network::http::AsyncClient(0x7efbcc008e88): Opening connection to 192.168.254.1:7001, URL https://192.168.254.1:7001/api/moduleInformation?showAddresses=false&keepConnectionOpen&updateStream=10, socket -1
2021-11-18 14:55:50.136   1253 VERBOSE nx::network::cloud::CloudStreamSocket(0x7efbcc015330): connectAsync. 192.168.254.1:7001
2021-11-18 14:55:50.136   1253 VERBOSE nx::network::cloud::CloudStreamSocket(0x7efbcc015330): Address resolved. Code: 0, entries: 1
2021-11-18 14:55:50.136   1253 VERBOSE nx::network::cloud::AnyAccessibleAddressConnector(0x7efbcc016860): Connecting to { direct:192.168.254.1({ port=7001 }) } with timeout 3001ms
2021-11-18 14:55:50.137   1253 VERBOSE nx::network::cloud::AnyAccessibleAddressConnector(0x7efbcc016860): Trying direct connection to 192.168.254.1:7001
2021-11-18 14:55:50.138   1253 VERBOSE nx::network::TCPSocket(0x7efbcc006d40, 192.168.254.45:38846->192.168.254.1:7001): Connect to 192.168.254.1:7001 completed with result Success
2021-11-18 14:55:50.138   1253 VERBOSE nx::network::cloud::AnyAccessibleAddressConnector(0x7efbcc016860): Connection completed with result Success
2021-11-18 14:55:50.139   1253 VERBOSE nx::network::cloud::AnyAccessibleAddressConnector(0x7efbcc016860): Reporting connect success. Address { direct:192.168.254.1({ port=7001 }) }
2021-11-18 14:55:50.139   1253 VERBOSE nx::network::cloud::CloudStreamSocket(0x7efbcc015330): Connect completed with result 0
2021-11-18 14:55:50.139   1253 VERBOSE nx::network::cloud::CloudStreamSocket(0x7efbcc015330): Got connection to []
2021-11-18 14:55:50.139   1253 VERBOSE nx::network::aio::StreamTransformingAsyncChannel(0x7efbcc019c60): Processing write task (0 bytes)
2021-11-18 14:55:50.139   1253 VERBOSE nx::network::aio::StreamTransformingAsyncChannel(0x7efbcc019c60): Scheduling socket write operation
2021-11-18 14:55:50.139   1253 VERBOSE nx::network::aio::StreamTransformingAsyncChannel(0x7efbcc019c60): Scheduling socket read operation
2021-11-18 14:55:50.140   1253 VERBOSE nx::network::ssl::ConnectingPipeline(0x7efbcc010bc0): SSL error SSL_ERROR_WANT_READ
0

Comments

5 comments

Date Votes
  • Permanently deleted user
    2021-11-18 14:55:55.212   1253   DEBUG nx::p2p::Connection(0x7efbcc041fe0, {47f2460c-a51f-733d-d3dd-3c6026e574a5}): Connection to peer {47f2460c-a51f-733d-d3dd-3c6026e574a5} canceled from state Connecting. Reason: Remote peer forbid connection with message: The connection from the peer {952114bf-d57d-44dc-b429-c4f97811124d} is already established
    Figured it out. NX cannot be cloned as it seems there is some uniqueness about the installation.
    0
  • Norman
    • Network Optix team

    Hi @...,

    I assume that these 3 devices are in the same network and/or merged together? In such case, cloning is likely the issue. That being said, cloning is still possible, but requires some additional steps as described in THIS support article.

    Another comment; please use a support OS. Although Ubuntu and Debian have a lot in common, issues still might occur, especially on the client side, since by default, Debian doesn't come with proprietary drivers. Please use Ubuntu instead with the default desktop environment in case you use the client. 

    Debian Bullseye is a non-supported OS. A list of supported OS and the applicable version can be found in THIS support article.

    0
  • Permanently deleted user

    Yes, same network, 2 of the 3 were cloned - 1st one was a test. So 2 and 3 clash when connecting to the server. To be honest, really silly having the client software have some sort of uniqueness to them. Server I can understand why, not the client though.

    Next batch will hopefully be Ubuntu - Debian was chosen as resources were absolute, client being cheap - putting down only for celerons - before they wanted atoms to use as device walls.

    Had to make do with what I was given...


    Well, hopefully I can fix this mess remotely and not have to go on site.

    0
  • Norman
    • Network Optix team

    Hi @...,

    The Nx Desktop Client does have a unique identifier called pcUuid in the configuration file.

    The configuration file can be accessed through the following path:

    /home/%username/.config/Network Optix/Network Optix HD Witness Client.conf

    The key name is "pcUuid". See the screenshot below.

    The process is the following:
    1. Stop the Nx Desktop Client.
    2. Delete the pcUuid key. (Everything on the line after pcUuid=)
    3. Start the Nx Desktop Client.

    The Client will create a new, unique, pcUuid.

    If you have remote access, you could do this through SSH or via TeamViewer through the terminal application.

     

    1
  • Permanently deleted user

    Solution works well, all 3 NUCS/Connections are able to be established at the same time.

    Thanks.

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post