-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
Most failures on this platform produce no error message, so this is symptoms and what actually causes them.
| Symptom | Cause |
|---|---|
| The descriptor opens as a page of text | Wrong MIME type. Must be text/vnd.sun.j2me.app-descriptor. |
| Install fails, no explanation |
MIDlet-Jar-Size does not match the jar. Usually a cache serving an old descriptor beside a new jar — serve both no-store. |
| The browser will not load the page | The hostname redirects HTTP to HTTPS. The device cannot do modern TLS. |
907 Invalid JAR — missing stack map |
The jar was not preverified. See Building from source. |
| "Already installed" | The descriptor's version must be higher, not equal. |
"no transport reached host:port" — nothing answered on any connection mode. Check Wi-Fi, and that you are on a network that can see that address. A handset on mobile data cannot see your LAN.
"THE HOST KEY FOR ... HAS CHANGED" — the server was rebuilt, or something is intercepting. There is deliberately no way past. If you know it was rebuilt, delete the saved connection and recreate it.
A key that works from a laptop is refused — it is RSA (unsupported, needs
BigInteger), or it has a passphrase (unsupported), or its public half is not
in authorized_keys.
Connects and authenticates, then nothing appears — try a different Terminal size.
| Message | Cause |
|---|---|
| "this is not an authenticating bridge" | You set a Bridge key but the far side is a plain proxy that never asks. Clear the key. |
| "the bridge refused the key" | Does not match psk in the bridge config — compared exactly, so a pasted trailing space counts. |
| "no such target" | Not in the bridge's targets. Re-open Bridge target to refetch the list. |
| "Could not ask the bridge" | Unreachable. Check with the curl in Reaching remote servers — 101 means alive. |
Drops after about a minute idle — nginx proxy_read_timeout. Set it to
86400s.
Works from the LAN, not from outside — the reverse proxy is not passing the
WebSocket upgrade. Caddy does it automatically; nginx needs proxy_set_header Upgrade and Connection "upgrade".
Some keys do nothing, others produce the wrong character — known and open, #11. The mapping needs raw key codes measured on hardware; Keys in the session menu shows the code for whatever you press, and those measurements are what the issue is waiting for.
Open an issue with the handset
model and OS version, what the status line said, and whether the same
connection works from ssh on a desktop.