CONNECTION GUIDE / 02
Prepare a JumpServer connection
Connect to the bastion first, then to your target host. Docklark has verified this complete basic connection path.
Login and host access verifiedConfirm these details with your administrator
- The SSH entry address and port for JumpServer
- Your bastion account and authentication requirements
- The target assets and system accounts your account can access
- Any VPN, multifactor authentication, or other access requirements
The three stages of a connection
Connect to the bastion
Use the SSH address and port confirmed by your administrator. Do not assume the web login and SSH entry point use the same address.
Authenticate your account
Sign in according to your organization’s requirements. Enter authentication details only in a trusted connection session.
Choose an authorized target
Use the bastion’s asset list and prompts to reach your target server. If an asset is missing, check permissions with your administrator.
File transfer limitations
rz/sz and drag uploads are implemented, with independent protocol checks passing CI and real-world feedback for drag uploads. The fix for a terminal hang after sz is integrated into main and still needs real JumpServer validation.
Check the roadmap for the current file transfer status.
If something goes wrong
First, identify whether the issue occurs when reaching the bastion or connecting from it to the target asset. Record the error without sensitive details, then check network access and permissions with your administrator. An unverified compatibility issue does not necessarily mean the account or server is at fault.