Troubleshooting & FAQ
Last updated
Common questions and what to do when an instance doesn't behave as expected.
A cold launch walks through Launching → Initializing → Starting services → Running and usually takes 5–10 minutes. The Initializing and Starting services steps cover first-boot setup and bringing the editors up. Give it a few minutes—we'll email you when it reaches Running. If it stays in one step far longer than that, it likely hit an error (below).
An Error status means the machine didn't come up cleanly. The status detail explains where it failed—for example:
The instance failed to boot.
Started, but its services didn't come up in time.
Initialization failed.
Stopped after an error.
Try Restart… from the instance menu. If it keeps erroring, contact support@gofigr.io with the instance name.
That's idle auto-stop doing its job—instances stop after a period of inactivity (60 minutes by default) so you don't pay for an idle machine. Nothing is lost; just Start it again. To change how long it waits, adjust the idle window under Auto-shutdown….
The Jupyter, code-server, and R Server buttons only become active once the instance is Running and its services are up. If a button is disabled, check the status—if it's still Initializing or Starting services, wait for Running. Connect links are tied to you as the instance owner.
You've reached the 3 self-service restore limit for that instance. Email support@gofigr.io to restore it. See Deleting & restoring.
No. Stopping preserves everything on your data volume—notebooks, files, and installed packages. Only deleting an instance removes its data. See Lifecycle & persistence.
Compute bills per minute only while an instance is Running, so Stop it when you're done (or rely on idle auto-stop). Storage bills continuously on the data volume even while stopped. Watch your usage on the Compute Usage card—see Compute & storage charges.
Still stuck? Email support@gofigr.io with your instance name and what you were doing.
Last updated