Missing Installation Steps?

Missing Installation Steps?

avatar

I'm trying to install Wayk Bastion and following the documented steps for Docker on Windows Server 2019. I feel like I'm missing some steps though. I've run through everything to install Docker and the Wayk Bastion module. I've also created the configuration profile. I just don't know what to do next? Is there an address to login to the dashboard? I can't find it documented anywhere.

All Comments (3)

avatar

Hi,

Once you have PowerShell and Docker installed, and then installed the WaykBastion PowerShell module + created your initial configuration, then launched it using Start-WaykBastion, you are ready to access the Web UI for the initial setup: https://docs.devolutions.net/wayk/bastion/index.html#initial-setup

The default -ListenerUrl parameter is "http://localhost:4000" and we have a special check in the server to let you access the Web UI directly on localhost, before you move on to configuring the -ExternalUrl parameter (the final external URL from which you will access Wayk Bastion). Try opening "http://localhost:4000" on the machine where Wayk Bastion is running, you'll be asked to change the default password ("wayk-admin" // "wayk-admin").

Once you have launched it a first time, you can follow the instructions to either configure a certificate in Wayk Bastion, or deploy Wayk Bastion behind a reverse proxy like IIS (https://docs.devolutions.net/wayk/bastion/iis-deployment.html). For non-localhost access, it is very important to remember that you must access Wayk Bastion through the configured -ExternalUrl. You also need to "Restart-WaykBastion" to apply changes.

I hope this helps,

Best regards,

Marc-André Moreau

avatar

When I try to go to http://localhost:4000 I get a message that says connection refused. I tried restarting the computer, but received the same result.

avatar

Did you manage to start Wayk Bastion? What does "docker ps -a" output for you?

If it says connection refused, it most likely isn't running, because nothing is listening on TCP/4000 (or the non-default port of your choosing).

Marc-André Moreau