So first question I have is this. Is wayk gateway wayk bastion or which one of these is the new wayk den? because I have an old attempt, but never completed install of wayk den, but I see in the instructions there's two supported install methos. Windows Server and Ubuntu Linux. So After clarifying those details for me, where can I get the Linux installation instructions to just start a fresh new install of what used to be wayk den?
Hello,
Wayk Bastion is the replacement to Wayk Den. Here are the steps to proceed with a Linux distro:
The Devolutions Gateway can be used instead of the integrated one.
Best regards,
Richard Boisvert
Thanks for that info but now I'm really confused. So I just installed this Wayk Bastion and from what I understand there's another component called the Jet Relay and from what you're saying there's also a Wayk Gateway? Are all these separate servers? Can I put them all on the same server? What do these additional servers Serv? As in what do they do and what advantage is there to setting them up myself vs just using devolution servers. Also, the Devolution's Gateway and Jet Relay servers aren't going to be shut down any time soon like the wayk portal was will they??
Hi,
By default, Wayk Bastion launches a simple Devolutions Gateway preconfigured alongside the rest. This is fine to get started and for small deployments, but it is recommended to deploy Devolutions Gateway separately and tell Wayk Bastion to use it. When deployed separately, you can restart Wayk Bastion without restarting Devolutions Gateway, which is useful to avoid disconnecting active peer-to-peer connections. It is also the only way to deploy multiple Devolutions Gateway servers for high availability.
While we recommend configuring the Devolutions Gateway separately, most customers start with the simple option (automatic configuration alongside Wayk Bastion) and stick with it unless they feel they'd need a larger deployment with more relay servers.
As for the public Wayk Bastion relay servers (they are Devolutions Gateway servers), we don't recommend relying on them for private Wayk Bastion deployments. They are not going away, just like the public Wayk Bastion is not going away, but consider them to be a convenience more than anything else. Private Wayk Bastion deployments should aim to be independent from our cloud services as much as possible.
Best regards,
Marc-André Moreau
How about making these instructions easy to find on the Wayk documentation pages?
Hello,
The installation instructions are available here:
https://docs.devolutions.net/wayk/bastion/index.html I had listed the steps one by one in an earlier post, but they are all available here.
If you encounter an issue, you can either contact us on the forum, or write to ticket@devolutions.net . We are also available for a session with you for the installation and initial configuration.
Best regards,
Richard Boisvert
I saw those before I found this forum thread. The documentation and unclear, hard to follow and I could not figure out what is needed to setup a Linux host server.
Like Tin_Man, it is also unclear what all the components are and how they interact. Naming is also confusing.
One example from your Overview documentation page "WaykBastion is a PowerShell module for Wayk Bastion" WTF does that mean?
Since you do support Linux for the server, I would absolutely want to use Linux and avoid the licensing fees for Windows Server. It would be nice to have a one-liner bash installer for this.
Another confusion "While we recommend configuring the Devolutions Gateway separately, most customers start with the simple option (automatic configuration alongside Wayk Bastion) and stick with it unless they feel they'd need a larger deployment with more relay servers."
The product looks interesting for us to add to our RDM tool. However, I cannot spend hours just trying to figures out the components to get it working.
Hi,
I apologize for the lack of Linux-specific instructions right now, we've mostly focused on documenting Windows because it is was most customers have been inquiring about, but Wayk Bastion does correctly run on both. Once you have installed Docker, PowerShell and the "WaykBastion" PowerShell module, 80% of the instructions are the same, the remaining 20% of difference mostly being file paths on Windows and Linux.
As for "WaykBastion is a PowerShell module for Wayk Bastion" being confusing, maybe I should write "WaykBastion" with a different style to make it stand out: here it really means there is a PowerShell module named "WaykBastion" that you can import with the "Import-Module -Name WaykBastion" command. What this PowerShell module does is pull Docker images for all of the Wayk Bastion components, expose a configuration interface, and start/stop them all in the correct order.
We cannot offer a one-liner bash installer, but we do offer a PowerShell module to simplify as much as we can. Docker and PowerShell are the only two prerequisites that you need to install yourself, and trying to install them for you would likely cause more trouble than it would solve. Wayk Bastion is composed of multiple microservices (the components), most of of which you do not really need to be aware of, except for the Devolutions Gateway relay server which can be deployed separately. There is no "installation" in the traditional sense of the term, because we pull Docker container images. The only persistent data left is the Wayk Bastion configuration directory with files and parameters injected automatically in the containers, and the MongoDB database Docker volume. If you save backup both, you can literally delete the VM, rebuild it from scratch and then restore the backup.
One thing I should point out is that beyond the installation of the prerequisites (Docker, PowerShell), most of the installation process is actually configuration, where the most difficult part is properly exposing Wayk Bastion over HTTPS for external access. Certificates have to validate automatically, it is mandatory.
Maybe tell me more about your intended deployment, and I'll see how we can fix the missing documentation? Tell me more about the Linux distro you normally use, and how you handle certificates for HTTPS access in your environment. If you use a reverse proxy, please let me know which one (nginx, haproxy, traefik, etc). Do you intend to expose it externally like we recommend, or is this intended to be for an internal network environment only? Add everything else I missed that could be relevant to a getting started guide tailored for you.
Best regards,
Marc-André Moreau