JuiceSSH

JuiceSSH - #1 SSH client for Android

[JuiceSSH @JuiceSSH]

@PSU_Josh You can confirm this is the problem by checking the JuiceSSH debug log (see https://t.co/MMkEs4K2pu) which should show decryption errors (due to the wrong passphrase).

[JuiceSSH @JuiceSSH]

@PSU_Josh Hi. This can happen if your CloudSync passphrase on the new device is wrong. It should show an error stating that, but maybe that's not showing for some reason. Try updating your CloudSync passphrase on the new device to the one you used for the original backup.

[JuiceSSH @JuiceSSH]

@jpiscaer No there shouldn't be any issues. Let me DM you now and we can get it sorted.

[JuiceSSH @JuiceSSH]

@brimurdotcom You can do it on a per-connection basis, by long-pressing the connection (in the Manage Connections page), and selecting Clear History.

[JuiceSSH @JuiceSSH]

@flameeyes Hi Diego. Can you send us a DM and we can get this resolved for you. Thanks

[JuiceSSH @JuiceSSH]

@covarrubiasgg No, i'm afraid this isn't possible. JuiceSSH Pro is linked to Google Play Store's in-app billing. Sorry to be the bearer of bad news.

[JuiceSSH @JuiceSSH]

@plebeiji Are you using Mosh connections? If so, it's a known issue on our list, but we haven't got any progress to share at the moment.

[JuiceSSH @JuiceSSH]

@RGralinski As a first step, take a look to see if your device OS allows you to disable battery optimizations for certain apps.

[JuiceSSH @JuiceSSH]

@RGralinski What device are you using? This is usually due to battery optimization settings. We do everything we can to keep them running, but we are at the mercy of the hardware/OS manufacturer. Some are more aggressive than others with this.

see: https://t.co/hkJbKW6dD1

[JuiceSSH @JuiceSSH]

@__nry I'm afraid this isn't possible today

[JuiceSSH @JuiceSSH]

@davli0 @cityblue2001 Can you confirm which version of Android you are using? We've seen this bug reported before, but it only seems to impact a few devices running older OS versions. To be frank, we're really struggling to find the cause/fix for it.

[JuiceSSH @JuiceSSH]

JuiceSSH 3.1.0 with support for ed25519 keys is heading to our beta channel as soon as Google approve it. Join our beta program here: https://t.co/gEJndFwkkO

[JuiceSSH @JuiceSSH]

@mattster98 Check out our latest beta (v3.2.2-beta1) available here: https://t.co/paA7GDOMPA

It includes an option in the settings menu to change your font. Currently supported are: Cascadia Code, Sauce Code Pro, Roboto Mono, Open Dyslexic, Inconsolata and Droid Sans Mono.

[JuiceSSH @JuiceSSH]

JuiceSSH v3.2.1 rolling out over the next 48hrs

Changelog:

1) Fixed crash when attempting a local/remote port forward to a destination host/port that refuses connections (firewalled etc)
...

[JuiceSSH @JuiceSSH]

@TechnoMikko Check out our latest beta (v3.2.2-beta1) available here: https://t.co/paA7GDOMPA

It includes an option in the settings menu to change your font. Currently supported are: Cascadia Code, Sauce Code Pro, Roboto Mono, Open Dyslexic, Inconsolata and Droid Sans Mono.

[JuiceSSH @JuiceSSH]

@translatedcode Check out our latest beta (v3.2.2-beta1) available here: https://t.co/paA7GDOMPA

It includes an option in the settings menu to change your font. Currently supported are: Cascadia Code, Sauce Code Pro, Roboto Mono, Open Dyslexic, Inconsolata and Droid Sans Mono.

[JuiceSSH @JuiceSSH]

@horsemankukka Check out our latest beta (v3.2.2-beta1) available here: https://t.co/paA7GDOMPA

It includes an option in the settings menu to change your font. Currently supported are: Cascadia Code, Sauce Code Pro, Roboto Mono, Open Dyslexic, Inconsolata and Droid Sans Mono.

[JuiceSSH @JuiceSSH]

@My1xT We've made quite a few significant updates over the last year 🙂 see https://t.co/paA7GDOMPA

[JuiceSSH @JuiceSSH]

Get it early by joining our Play Store beta program:
https://t.co/6jjRCEZhuY

...or directly from https://t.co/paA7GDOMPA

[JuiceSSH @JuiceSSH]

3) Updated terminal font to Delugia Code. This monospaced terminal font is based on Cascadia Code, but patched with Font Awesome and Powerline glyphs. Updating the terminal font to this (from DroidSansMono) was necessary as a part of fixing the above rendering bug.