I sent you a private message earlier this week, as mentioned in this thread. Did you see it?
On November the 3rd, you attempted resolving "e1853e5b-8070-b6a5-798f-c2025dadca51", which is a valid unique id for a machine currently online. However, the unique id should not be used directly as a target id, it should be put in a bookmark, making sure not to put the short id (we'll fix this behaviour).
If e1853e5b-8070-b6a5-798f-c2025dadca51 is the correct unique id, then the current short id would be "385344". Let me know if the information is good, I have confirmed that "385344" is an id that can be resolved.
If I have guessed incorrectly, please send me the unique id of the target you are trying to reach. The unique id can currently only be used in one way: by creating a bookmark where you include the unique id and not the short id (6 digits). If the short id is present it will be used instead of the unique id. You cannot put the unique id in the "target id" text box. I agree that this is a bit confusing and we'll improve how the unique id can be used in the future.
You can find the short id from the unique id at any time by changing the last part of the following URL:
This is the information that is fetched by Wayk Now when a bookmark is configured with a unique id.
If the information is correct but you still cannot connect, it is possible that the unattended service gets stuck. We have made a couple of changes in the code since the last release to fix different conditions where this happens. In addition to this, we plan on upgrading the Wayk Den infrastructure this Thursday with additional fixes that should really improve overall stability.
First things first, please confirm the information above, otherwise please tell me the unique id and short id that you are trying to connect to, and I'll see what I can do on my side.