Back to Newsroom

Product

Fixes from a tester report: login links, terminal start, machine plan hint

More login addresses open the sign-in window, the terminal waits briefly for a freshly started container, and a Pro account sees a plain plan hint for own machines.

User impact: Not reviewed

Three fixes from the report of a tester on the Pro plan, each with a test.

Login links OPENS SIGN-IN /login, /signin, /sign-in /log-in, /anmelden /einloggen Terminal start WAITS UP TO 6 S New container may lack its network at first Then 503 with Retry-After Machines on Pro PLAIN HINT Own machines start at the Ultra plan Link to the plans REPORTED 28 OCTOBER
The three fixes.
Text version

Login addresses open the sign-in window. The terminal waits up to six seconds for the sandbox network of a new container before it answers 503 with a retry hint. A Pro account sees a plan hint for own machines, not an error.

Until now only /login opened the sign-in window. Now /signin, /sign-in, /log-in, /anmelden and /einloggen do too, where before they ended in a 404.

Right after a container started, the terminal could answer with a bare 503 while its network had no gateway yet. It now waits up to six seconds, and if the network is still missing it says so with a retry hint.

On Pro, the machines card used to show a red error. It now says that own machines start at the Ultra plan and links to the plans.

Corrections belong here too. Feed · Docs · X · Legal & privacy