I use Jump Desktop to remote into my Mac mini using my iPad Pro which works very well. There are times I need to remote restart the mini using the iPad and wanted to know if there is a way to log back in after a restart as admin using my iPad.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Resolved Is it possible enter the password for the login screen on my Mac mini using my iPad after a remote reboot?
- Thread starter Apple_Robert
- Start date
- Sort by reaction score
there is a terminal command that pre authorises your reboot you can use:
sudo fdesetup authrestart
sudo fdesetup authrestart
I entered the command in Terminal, enter my password and user name etc. After the mini rebooted, remote into the mini with JD, do a remote restart and JD tries to reconnect but nothing happens.
Thanks for replying.
Last edited:
Works great when FileVault isn’t enabled. When i have it on, JumpDesktop can’t reconnect and I get a message on my mini screen (in so many words) that if I can’t connect and forgot my password...etc.
I always have file vault enabled. I wouldnt disable it.
I use jump desktop to remote in to my mini via my iPad, same as you. It’s frustrating that there is no other option, especailly when there is a power cut or something and your away from home. But aside that, this termial command works extremely well. are you having trouble with it?
If I turn off FV and attempt a remote reconnect with JD, it works fine. If I turn FV back on and try, JD doesn’t seem to be able to connect.
On the Mac screen it says “If you’re having trouble entering your password, press and hold the power button on your Mac to shut it down. Then press it again to start up in the Recovery OS.”
With FV on, Jump Desktop does not reconnect and offer me the password screen.
Last edited:
No, nor me if I try normal restart. However, using that terminal command, it should work fine. It does for me, Filevault on or not. Are you saying that this terminal comand doenst work for you with file vault switched on?
Yes. If I do a normal remote reboot with FV off, JD is able to reconnect and log back in on its own. With FV turned on with a normal reboot, JD tries to reconnect but is unable to log back in. And after x amount of attempts it stops and then I get that message on the bottom on the Mac screen.
Edited to add: If I just try a simple connect, JD can connect with FileVault turned on. It is the normal reboot reconnect with FileVault turned on that is the problem.
Last edited:
If I reboot using the terminal it works fine. Maybe there is a diff in jump desktop settings or some internal macos settings.
I have just tried rebooting from jump desktop on the iPad and from the machine itself. Both work great
I apologize for confusing the situation. I will try to be more clear and concise.
I enabled root user and enter the command as noted. The user and password I entered in terminal is the same one I use for my day to day admin account. Once the Mac rebooted, I logged in under my admin account. Once logged in, I remote in with JD without any problems. I then proceeded to restart my Mac from the JD client. After the Mac restarts, JD attempts to reconnect but all I see is the “reconnecting” message from JD. It never gets to the actual login screen in JD where I can enter my password and log back into the Mac with FileVault turned on.
If i turn off FileVault, there are no problems and JD reconnects to the Mac mini after a reboot thus allowing me to enter my password.
Is it possible I am missing a toggle setting somewhere?
Does JumpDesktop have curtain mode whereby the remote Mac screen does not show what is being done when logged in via JD? I haven’t been able to find it if there is the option.
Last edited:
I’m going to have a little look later when I’m at my computer. I’ll get back to you but it could well be a setting somewhere that’s different yeah. Also- these things are notoriously finicky anyway so it could just be that. Frustrating though.
For me personally it’s because it ensures the computer and information on it are in an encrypted container.
I admit that that’s an old school way of looking at it, and my thinking regarding FileVault pertains to the days before t2.
I was actually looking into all the options as I wanted to disable it to aid with what the op and I are talking about- remoting in.
I would actually like more information regarding this because the t2 has confused things.
I have FileVault on, and it’s secured with my own personal key, ie- not tied to iCloud.
I have a firmware password - which I have disabled the ability for Apple (and by extension I assume anyone else) to reset it, via terminal as per the instructions on apples website.
I also have the machine locked down to the max security settings, no external booting.
I wonder if the t2 involvement coupled with the secured firmware actually make FileVault redundant?
My goal is to avoid any possible way of entering the system other than with my password. Either via the gui using the main disk as a start up or a usb disk, via the terminal from recovery mode or via electronic means such as removing the drive.
I very much appreciate you taking the time to try and help solve this problem.
I’m at my Mac and iPad now. I really can’t see if there are any settings that may affect this. As a test, I just did the whole process again, once via my mac directly, and once with the monitor unplugged via my iPad Pro. I connected via my phone so it was on a different network.
On both tests, I can log back in directly via Jump Desktop after using the terminal command to restart the Mac. I’m really not sure as to why youre unable to do this! I’m stumped to be honest.
Log in screen:
Logged in:
For a Mac that’s used exclusively remotely, you need to disable FileVault. The initial password prompt happens before the operating system loads so there is no possible way to remotely access the computer to enter the password to unlock the disk at that point. For a planned restart you can issue the command
Code:
sudo fdesetup authrestartThanks for the post. Out of frustration, I did a clean install late last night and was able to try the command again a little while ago, and it is now working. I don’t know what was impeding it working yesterday but, it appears to be working as it should today.
Thank you again, CC for posting the code and working with me yesterday to try and get this resolved.