I recently had another user report a similar problem. In their case, the hosting provider changed their ssh server settings to limit the number of supported ciphers. I guess that's the case here as well. I'm currently investigating which ciphers Textastic needs to support to solve this problem.