[BUG] Android App can't connect to any host

[phil9309]

Title

Connection fails after 3 retries

Platform

App - Android

Server Installation Method

Docker

Version

1.9.0

Troubleshooting

• I have examined logs and tried to find the issue
• I have reviewed opened and closed issues
• I have tried restarting the application
• I have read Known Issues (Known Issues (Read Before Posting) #296)

The Problem

I set up Termix and love it so far, all my hosts work perfectly fine in the Web app on my computer and mobile.

When trying the mobile app, I encountered a stange problem: for some reason I can't connect to any of the ssh hosts there. It tries 3 Times and fails.

The only thing I changed in the default docker compose is the port, since 8080 was already in use.

I use Pangolin as reverse proxy, a friend of mine has this exact same setup the only difference between me and him is the change of the Port and him using iOS, so..

Is there anything I can do to troubleshoot this? I can't see anything in the logs.

How to Reproduce

1. Successfully login on mobile app
2. Try any host

Additional Context

No response

[phil9309]

It seems to be the Pangolin auth layer. Weird, for the friend using ios, double authing (Pangolin layer + termix auth) works.

For me the auth itself works, connecting to Servers doesnt. Is the Android App maybe "forgetting" the cookie?

[P3RF3CTION]

I remember to have seen issues with pangolin and some auth topics. And I thought it is how pangolin handles auth.

[doody]

I'm having the same issue with Android Client and Pangolin as reverse proxy, according to the pangolin request log, it seems like ssh client didn't provide valid auth information to pangolin, if I disable pangolin auth, I can ssh to server through termix, file browsering works well with or without pangolin auth

potential workaround is to setup rules to bypass auth on /ssh/websocket/ in pangolin until client can carry cookies

[ZacharyZcR]

Maintainer note - 2026-05-31

Audited current codebase against this Android connection report. This repository currently contains the shared web/PWA/Electron surface and mobile WebView detection, but I did not find native Android app source code here that would let us verify the specific Android client failure path. The shared connection code has evolved since this report, but I cannot confirm this issue is fixed from the current repository alone.

Keeping this open pending a current-version Android reproduction or confirmation.

[ZacharyZcR]

2026-05-31 update: Mobile-side fix is in Termix-SSH/Mobile#25. The PR enables shared cookies in the sign-in WebView and sends auth-related headers on the native terminal WebSocket, targeting Android reverse-proxy setups such as Pangolin where /ssh/websocket/ was reached without the expected auth context.

[ZacharyZcR]

Hey, has this issue been fixed in version 2.3.2?