SSH and the Console are failing because vicnezknihy has static outbound IPs enabled. The two don't work together right now: the container can't open its tunnel back to our SSH relay through the static-IP path, which is why the session drops after about 9 seconds even though your key is accepted. It isn't your image or configuration, and redeploying won't change it. We aim to have this fixed in the coming weeks and we'll reply here when it ships.

If you need a shell before then, turning static outbound IPs off and redeploying restores SSH, but the service's outbound IP changes, so only do that if nothing on your side allowlists the current IPs.

After the recent incident I turned on static IPs so I could implement firewall rules for my database. Are you saying that if I want to do that I lose SSH functionality? If so are there any plans to support it at some time in the future? Are there any suggested workarounds?

Yes, for now that's the trade-off: while static outbound IPs are enabled on a service, SSH and the Console can't connect to it, so a database firewall that only allows those IPs means doing without a shell until we fix it. It's a bug on our side, not a design decision, and the fix is in progress. We aim to ship it in the coming weeks and we'll reply here when it's out.

The only workaround today is the one above: turn static outbound IPs off and redeploy, which restores SSH but changes the service's outbound IP, so your database firewall would need updating too. If you can live without a shell for a while, keeping static IPs on and waiting for the fix is the safer option for your firewall rules.