Troubleshooting
Logs and terminal closed
Each reason a log stream or a shell closes, and when to reconnect.
Updated
A log stream and a terminal are live connections to Cloud. When one closes, the log shows the reason under its controls, and the terminal prints it in brackets on the screen. Press Reconnect on a log, or Open a new shell in the terminal, once the cause is cleared.
The same sentences end a shell opened over SSH; see SSH refused for the gateway's own messages.
Why a log or a shell closed
| Message | Why | What to do |
|---|---|---|
| Nothing is running. | The service has no running container to read from or open a shell in. | Deploy or start the service, then reconnect. If it keeps stopping, see The service keeps restarting. |
| This deployment has not started yet. | A build log was opened before the platform reported the deployment. | Nothing: while the deployment is moving, the page tries again on its own. |
| Closed after 10 minutes without output. | A log stream closes after 10 minutes in which the service printed nothing. | Press Reconnect. |
| Closed after 30 minutes idle. | A shell closes after 30 minutes with nothing typed and nothing printed. | Press Open a new shell. |
| The engine closed the connection. | The platform ended the stream or the shell: the shell exited (for example after exit), or the container stopped. | Open a new shell, or reconnect the log. If a new shell closes at once, choose sh, the default, under Shell. |
| Too many open connections. Close one and try again. | An account may hold 8 log streams, shells and SSH sessions open at once, and Cloud also caps the total it holds for everyone. Every open log tab, build log, terminal and SSH session counts. | Close tabs you are not reading and shells you are not using, then reconnect. |
| The engine did not answer. Try again in a minute. | Cloud could not reach the platform to open or keep the connection. | Reconnect in a minute. If it lasts, contact support. |
| Sign in to continue. | Your session has ended. | Reload the page and sign in again. |
| That does not exist. | The service or deployment was deleted, or the link belongs to another account. | Open it again from its project. |
| Your workspace is still being prepared. | The workspace of the service's organization is not ready. | See Your workspace is still being prepared. |
| That shell is not offered. | The shell in the address is not one of sh, bash, zsh or ash. | Choose one from Shell. |
| That log range or limit is not offered. | The line limit or time range in the address is not one the page offers. | Choose from Line limit and Time range. |
| This belongs to a different engine than the one running now. | The service was created on a platform Cloud no longer runs it on. | Contact support. |
| The connection was lost. | The network between your browser and Cloud dropped. | Check your connection, then reconnect. |
| The connection was closed. | The connection ended without a reason from Cloud, for example after sending more than 64 KiB in one go, such as a very large paste into the terminal. | Reconnect, and paste large text in smaller parts. |
Empty screens
These are states rather than errors, and they clear on their own.
| What you see | Why | What to do |
|---|---|---|
| Nothing is running. Deploy the service and its log appears here. | The service is not running, so it has no runtime log. | Deploy or start it. A build log stays with each deployment. |
| Waiting for output. | The stream is open and the service has printed nothing in the chosen range yet. | Wait, or widen Time range. |
| No line matches. | The search or Log type filter hides every line. | Clear the search or set Log type to All types. |
| No service is running. Deploy one and open a shell here. | The Terminal page lists running services only, and you have none. | Deploy or start a service. |