Brian

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 24 total)
  • Author
    Posts
  • Brian
    Participant

    Ah! I think relentless tinkering has finally arrived at the answer to this.

    It appears that somehow along the way, multiple attempts to uninstall and reinstall the software and delete and reestablish my user ID resulted in my iPhone appearing in the authorized devices list more than once. Apparently this confuses the notification process and it basically gives up.

    If having difficulty receiving 2FA notifications to connect to a remote device (whether an external IP address or within the same LAN), might I suggest that you go online to the NM website and get in to your user account profile and look at the authorized devices signed up to receive 2FA notifications and see if it needs some cleanup.

    What I did just to make sure I was totally clean was to delete ALL authorized devices from my user account on the website and then uninstall the software from all of my devices (NM servers and all clients including iPhone). I then reinstalled everything, logged back in, and re-enabled 2FA and the notifications began to work again. I had uninstalled and reinstalled many times before but it was obvious the problem was that I was unaware that I had totally screwed up the authorized devices list. So hopefully this helps !

    Brian
    Participant

    Ok this is stranger than fiction! With no other changes since we last addressed this subject, I now DO receive connect notifications on both iPhone and MacBook Pro clients from the MacMini server. The only thing that changed was that I entered 9-Debug mode and restarted the server. Not sure how that could change things, but I guess I’ll not ask questions and just be happy! Everything works fine now so I guess that’s it for this thread. Not sure if you still want logs or not at this point….thanks for staying with me!

    Brian

    Brian
    Participant

    Yes I realize I don’t need to be logged in to the network with my email to receive 2FA notifications. 

    However I logged in to see if for some reason I would start to receive 2FA notifications when I try to initiate a session if logged in to the network as opposed to not being logged in….(i.e., something else to try.)

    I received the 2FA notification when I was logging in to the network with my email address just fine.

    However when attempting to initiate a connection I am unable to receive a 2FA notification on the same phone, irrespective of whether I am or am not logged in to the network with my email address.

    Let me know if there is any further insights I can pass along that will help!

    Thanks!

    Brian

     

    Brian
    Participant

    UPDATE – Worked together with your people and found this also was resolved with release candidate 9.1.22, so I am all set. Thanks so much!

    in reply to: Screen shading cannot be controlled #53701
    Brian
    Participant

    Worked together with your people and found all of my issues in this thread were resolved with release candidate 9.1.22, so I am all set. Thanks so much!

    Brian
    Participant

    I am experiencing this same phenomenon: do not receive push notifications and when asking to be re-sent, receive nothing. Happens with both an iPhone client and a MacBook Pro client attempting to connect to a MacMini M1 server.

    As to the above:

    – after inserting the email address in the 2FA machine configuration window, you received a push notification on your phone asking you to accept/refuse receiving notifications regarding that machine. [Never received]

    – that you accepted this notification and see a success message. [No, as never received]

    – then you tried to connect to your computer after you accepted pairing on the phone. [Same as above].

     

     

    in reply to: Screen shading cannot be controlled #53550
    Brian
    Participant

    I made the requested changes to the node.cfg file and I still note the screen shading issue. It happens when the server screen is asleep and it also happens when the screen is awake so it does not appear related to sleep issues. I am providing a link to a screencast video so you can see the issue happening for yourself. I will email the logs without the /users folder as the number of files in that folder is so large my email server rejects the mail. Let me know if this is an issue or if you want it anyway and I will send it with a different mail service. https://app.screencast.com/EUnOprNy76vZp

    in reply to: Screen shading cannot be controlled #53156
    Brian
    Participant

    No it does not help by implementing the suggested settings on either the server or the client. I’m also having issues I’ve never had before with the server being unresponsive to the keystrokes from the client, i.e., I cannot enter in my MacOS password on the remote server lock screen; characters will not appear in the password entry field when keys are depressed. Restarts and close and reopens do not remedy this issue. Very frustrating after just having gotten version 8 finally working.

    in reply to: Screen shading cannot be controlled #53131
    Brian
    Participant

    I’ve also added a link to screencast where I’ve placed a brief 17 second video that shows what is happening on my client side connection on the MBP as well as a snip of the security settings on the MacMini M1 server.

    See video here:

    Brian
    Participant

    Noted with thanks!

    Brian

    Brian
    Participant

    Got it now, thanks! Installed and an interesting result. When it connects for the first time the results are exactly the same as before:

    the client connects to the server and the server wakes up, but the client is in black screen. Moving the finger around on the black screen of the iPhone correspondingly moves around the arrow cursor on the MacBook, but this is not visible on the black screen of the client.

    Now however, after having installed your update, if I then disconnect from the server, and I reconnect once again, I am able to connect and see the server on my iOS client, apparently because the server has now been awaken (though it was in the previous instance as well so I’m not able to understand why dropping out and going back in works now.)

    This behavior is different than with my MacMini M1 where the computer wakes and connection is possible right from the very first attempt. So this is usable now, but wanted to throw these findings out to you for what it’s worth.

    Thanks!

    Brian

    Brian
    Participant

    What in box are we referring to ? Nothing received in my email and if it is here on the website I’m not sure if I know where that is? Sorry!

    Brian
    Participant

    I’ll take it whenever you’re ready to send it….

    Brian
    Participant

    Did you get my logs on email?

    Brian

    Brian
    Participant

    Ah thanks for that link on how to collect all of the log files.  Again, what I am seeing, on an iOS iPhone 12 Pro Max client (running ver. 8.7.1) and an Intel MacBook Pro (running ver. 8.16.1) is that for both LAN and outside External WAN IP address connection attempts, the client connects to the server and the server wakes up, but the client is in black screen. Moving the finger around on the black screen of the iPhone correspondingly moves around the arrow cursor on the MacBook, but this is not visible on the black screen of the client. If the MacBook is already awake, the client will connect and the screen of the MacBook is visible as normal on the iPhone client with no black screen.

    The ZIP file is too big to attach so I will email it to you…(I did reset and clear the logs before I started debug mode to catch the errors for demonstration).

    Thanks!

    Brian

     

Viewing 15 posts - 1 through 15 (of 24 total)