First off, thanks for an amazingly useful product. I couldn’t live without it. I ran into a surprising bug today:
I have two user accounts. I must have started remote.it on one account at some point. Today, on my other account I tried to start remote.it and the spash screen appears for a moment then disappears. No feedback. There’s no useful message in the console logs.
I started it from the terminal, and there the cause is obvious: it warns that it’s unable to bind to its desired address, then immediately quits–I assume that’s why, but that’s not very smart behaviour on multiple levels. It’s such an obivous problem, I’d be surprised that it was not anticipated, so I’m bring it up in case there is something more unexpected going on.
- some kind of UI feedback is always needed rather than silently quitting
- it should have a fallback, or be intelligent enough to figure out that another instance of remote-it is using that port and deal with it, or warn the user if it can’t.
- Seems odd that an app that can be set per-user to run on startup can’t handle multiple instances.
% /Applications/Remote.It.app/Contents/MacOS/Remote.It
2025-05-03 14:00:36.347 [PID 68278] - info: REMOTEIT DESKTOP STARTING UP ---------------------------------------------------------
…
2025-05-03 14:00:36.477 [PID 68278] - warn: SERVER START FAILED {
“error”: {
“code”: “EADDRINUSE”,
“errno”: -48,
“syscall”: “listen”,
“address”: “127.0.0.1”,
“port”: 29999
},
“details”: “Error: listen EADDRINUSE: address already in use 127.0.0.1:29999”,
“directory”: “/Applications/Remote.It.app/Contents/Resources/app.asar/node_modules/remoteit-headless/build”
}
2025-05-03 14:00:36.477 [PID 68278] - info: QUITTING APP
% sudo lsof -nP -iTCP:29999 -sTCP:LISTEN
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
Remote.It 12558 otheruser 23u IPv4 0x9b2ed09bfe4166bc 0t0 TCP 127.0.0.1:29999 (LISTEN)