Server is online and working with cloud connection issues

Answered

Comments

5 comments

  • Avatar
    Adam Anderson

    Occasionally this error pops up, but then the client can connect without restarting

    at the nxvms.com web portal we get the following

     

    0
    Comment actions Permalink
  • Avatar
    Ichiro

    Hi Adam Anderson,

    Thanks for your detailed report. 
    May I know if you have updated the system from v4.2 then 5.0.0.35136 then 35270?

    What if you use an incognito tab/page of a browser to access the nxvms.com under your Nx Cloud account? Will that make any difference, ex: your system now becomes online or any thing different from previous access?

    Thanks.

    0
    Comment actions Permalink
  • Avatar
    Adam Anderson

    Hi We went straight to 35270, as we had this connection issue, I just downloaded the latest install and ran it on the production system (installed over, not upgraded).

    This did not solve the problem.

    I set some port forwarding so that I could connect directly to the Server (local account), this worked so then switched back to connect via the cloud and it worked, which was great for me but I didn't want to create local accounts for the cloud users, so after restarts and other things I tried unsuccessfully I decided to run an instance on AWS and Merge it into the system. This immediately resolved the connectivity issue for all cloud users. This also allowed the server to appear in nxvms.com and I could monitor and see settings.

    In the next few days I will shut down the AWS server and see if the authentication / routing / access problem- (or whatever it is) comes back.

    0
    Comment actions Permalink
  • Avatar
    Ichiro

    HI Adam Anderson,

    Thanks for the detailed information. It sounds like it could be some authentication or routing problem.
    Can you let us know the result if the cloud is down again after you shutdown the AWS instance?

    I believe we will need to look into this.
    Thanks for your corporation and appreciate your assistance.

    0
    Comment actions Permalink
  • Avatar
    Adam Anderson

    Yes shutting down the AWS instance causes the problem to return.  I'll test again, our ISP is also looking into routing.

    0
    Comment actions Permalink

Please sign in to leave a comment.