I have been demoing Bastion for a few hours today and was able to get a server up and running. Only real trouble I have run into so far was when I attempted to register an endpoint with the server. When I try to register, the agent connects to the server but if I attempt to regsister I get a non specifi "An unexpected error occured" error.
Only thing non standard in this case was I did not register the server with an SSL cert. That may or may not have anything to do with it. This server is not intended for production.
Hi Tyson
To find out what the issue is, please start by making sure that logging is enabled on your Wayk Agent:
One more thing - the current "login, register" workflow is something we're moving away from as it's not really scaleable for large deployments. We've added an alternative mechanism using the command-line. The documentation for this isn't added to docs.devolutions.net yet, so I'll explain here:
wayk-now enroll --token-id {tokenid} --den-url {bastionurl}
(Obviously substituting the token ID and your own Bastion URL)
In an upcoming release you can expect to see the existing registration UI replaced with something that uses the new token-based system.
Let me know if that helps,
Richard Markievicz
Thanks for the quick reply! Logs sent.
I'm glad you mentioned that this feature is getting a bit of an overhaul. The idea of registration did seem to be a bit challenging in larger deployments.
I ran the PowerShell command you mentioned and it registered straight away, thank you!
One more thing - the current "login, register" workflow is something we're moving away from as it's not really scaleable for large deployments. We've added an alternative mechanism using the command-line. The documentation for this isn't added to docs.devolutions.net yet, so I'll explain here:
wayk-now enroll --token-id {tokenid} --den-url {bastionurl}
is this the same command for the wayk agent? or perhaps it's "wayk-agent enroll --token-id ..."?
Hello,
The command is still wayk-now enroll --token-id {tokenid} --den-url {bastionurl} It was not changed for clients that had scripted the registration prior to the Wayk Bastions rebranding, they could just keep the same one as before.
You can consult the automation documentation here: https://docs.devolutions.net/wayk/bastion/deployment-automation.html
Best regards,
Richard Boisvert