[BUG] Cant connect to internal hosts when using jumphost function

[termix-github-bot]

Platform

Debian+docker

Version

2.4.1

The Problem

I have a running vm with v1.11.1. I connect to all my internal hosts via the jumphost feature in termix. I then pulled the latest image v2.4.1 and all seemed fine. I could login with my credentials to the webui and connect from termix into my jumphost cli. However as soon as I attempt to connect to my internal hosts via the jumphost it just times out.

If i connect from termix to my jumphost. And then manually type in my jumphost cli to login via username@ip, it immediately authenticates with the key and logs in fine.

The same happends if i try to use password authentication instead of ssh keys.

How to Reproduce

See above in the problem definition. I will add screenshots later tonight.

---

Note

Submitted via the Termix Discord Support Bot
Reported by jonnybandini on Discord
View Discord thread

[termix-triage-bot]

Auto-triage

Users are unable to connect to internal hosts via the jumphost feature after upgrading Termix to version 2.4.1, with connections timing out.

Field	Value
Type	Bug
Difficulty	3/5 (Moderate)
Priority score	6.0
Labels	bug ssh

A maintainer will review shortly. If the auto-classification looks wrong, feel free to say so.

[h4nnamon]

I replaced IPs and usernames for privacy:

This is from the Connection Log inside Termix
11:07:57 AM
Starting address resolution of x.x.x.8
11:07:57 AM
Connecting to x.x.x.x port 22
11:07:57 AM
Loaded 1 jump host(s) from server-side host data
11:07:57 AM
Credentials resolved from server-side host data
11:07:57 AM
Using SSH key authentication
11:07:57 AM
Starting SSH session through jump host
11:07:57 AM
Authenticating as ####
11:08:31 AM
Connection timeout
11:08:32 AM
Connection rejected by server. Please check your authentication and network configuration.

This is the from the SSH log in the host I was trying to connect to:
sshd: Connection from x.x.x.2 ... incomplete message [preauth]
dispatch_protocol_error: type 186 seq 0 [preauth]

[rnihesh]

yeah same for me too

Error: Corrupted padlen 0 on input.

And this jump host is working normally from other clients.

[rnihesh]

fixed in 2.5.0

[termix-triage-bot]

It looks like this issue may be resolved based on the comments.

Based on the thread, the fix was: The issue was resolved in Termix version 2.5.0.

If that's correct, feel free to close it. If the problem is still happening, please drop a comment with your current Termix version and any new info.

[h4nnamon]

Tested this V2.5.0 this morning. can confirm its working! Thanks for the speedy update!