"Unable to map port: Could not locate gateway on time."

[paxperscientiam]

After giving up on prey installed via NPM, I decided to try directly from the website.

Whereas the prey agent would crash and restart continuously when it had been installed via NPM, this is no longer the case. However, prey is still not working.

log.txt

Any thoughts on how to remedy this?

[mauricioschneider]

Hello. According to the log, it should be working. The "could not locate gateway on time" part is because Prey was unable to use uPnP, most likely because your router does not support it. Nevertheless, uPnP has been removed in the release soon to be uploaded.

Could you please check if your config file located in /etc/prey/prey.log contains an API and Device keys? (Do not share your keys here if that's the case).

[paxperscientiam]

Hiya,

Hm okay. Did you mean /etc/prey/prey.conf? I have that and it does indeed have a device key and an API key.

[mauricioschneider]

Yes, sorry, that's what I meant. Did you try sending instructions (alert, alarm) to your device from the Prey website?

[paxperscientiam]

I've only tried the location service. Let me give that a whirl. BRB.

Very interesting! The ear-piercing siren works! Yeah, should have checked the volume on my head phones first... Also, the alert message works too.

And now location service is working...

So, I don't know what to say. It's working now 👍

[mauricioschneider]

What OS do you have? I could provide you with a beta version of the next release which should be more responsive to instructions from our servers.

[paxperscientiam]

If you're interested, I have a hunch why their might be a problem with NPM installed version working. I installed NPM via Macports and as such my global modules require sudo to update. But that's just a guess.

EDIT: OSX 10.11.1. So, I'll power cycle and report back if there are any further issues.

Thanks for the awesome program!

[mauricioschneider]

To be honest, the NPM version is not very reliable right now and the stand-alone version is recommended (which I see you installed it, though).

[mauricioschneider]

Yeah, should have checked the volume on my head phones first

Woops. I'm sorry again, I forgot to warn you about that. I learnt the hard way to remove my headphones prior to running any test 🙄.

[paxperscientiam]

OK, after some digging, I'm noticing a few potential minor issues.

When device location is requested from the online Control Panel by either clicking the "Update Location" button or by refreshing the webpage, the "last seen" response fails to update even though the Control Panel reports "device reached" and "got location." That said, sometimes those responses are followed by a failure to locate response.

Looking over the log file, it seems that both alert and alarm "actions" are recorded. However, there is no record of attempts to locate the device in the log. Perhaps this is by design? I'm left wondering if the mother ship is truly determining the location of my machine.

[mauricioschneider]

Until version 1.4.2 the Prey client was connecting to our servers via intervals. Starting from the next release (most likely we'll make the jump to 1.5.0), Prey will use a completely different approach to the way it connects to our servers, which solves the delayed location issue you mention and a few other user experience related problems, also allowing for a more responsive and stable behaviour.

[paxperscientiam]

Ah, thanks for the explanation, lemavri.