I Can't Connect to my Cubby

I'm trying to connect to my cubby from a command-line and get a "Permission denied (publickey)" error

This error means you are able to establish a connection to the cubby, but the cubby is denying access due to missing or incorrect keys/credentials.

  1. Make sure you an authorized dev - Log in to your account at cubbies.dev. If you can't see the cubby in your list of cubbies, ask an administrator or someone with access to the cubby to add you as an authorized dev. If you can see the cubby, but you are not an authorized dev, you can add yourself by editing the cubby.
  2. Check the command you're using - Sometimes it's easy to mix up hostnames and credentials between cubbies and/or other servers. Log in to your account at cubbies.dev, copy the SSH command next to your running box, and paste that in to your command line.
  3. Check your keys - In order to connect to your cubby, we use SSH keys. If the key your command line is using doesn't match any of the keys on your Devcubbies user, you won't be able to connect to any of your cubbies. Check to make sure the computer you're using has at least one of the keys you've added to Devcubbies or add a new one. See: Adding SSH Keys to my Account
  4. If none of these steps help, log in to your account at cubbies.dev, click the Support link in the footer, and fill out a support ticket so we can assist.

I'm trying to connect to my cubby from a command-line and get a "Name or service not known" error

This error means your command-line can't find a path over the Internet to your cubby using the command you supplied.
  1. Check your Internet - Make sure you are on an unrestricted Internet connection. Sometimes public WiFi will block, throttle, or limit certain connections on their network that can cause you to randomly or intermittently lose connections.
  2. Check the command you're using - Generally this error means you're not using the correct hostname or IP address to connect to the cubby. Log in to your account at cubbies.dev, and copy the SSH command next to your running box and paste that in to your command line.
  3. If none of these steps help, log in to your account at cubbies.dev, click the Support link in the footer, and fill out a support ticket so we can assist.

I'm trying to connect to my cubby from a command-line and get a time out or no response error
This error means your command-line can't find a path over the Internet to your cubby using the command you supplied.
  1. Check your Internet - Make sure you are on an unrestricted Internet connection. Sometimes public WiFi will block, throttle, or limit certain connections on their network that can cause you to randomly or intermittently lose connections.
  2. Check the command you're using - Generally this error means you're not using the correct hostname or IP address to connect to the cubby. Log in to your account at cubbies.dev, and copy the SSH command next to your running box and paste that in to your command line.
  3. Check the status of your cubby -  Log in to your account at cubbies.dev. If your cubby isn't in the "running" state, you won't be able to log in. Start the cubby if it's stopped or if it's "lame", see My cubby says it's Lame.
  4. If none of these steps help, log in to your account at cubbies.dev, click the Support link in the footer, and fill out a support ticket so we can assist.

I'm using VSCode or another IDE and can't establish a connection to my cubby

  1. Check your Internet - Make sure you are on an unrestricted Internet connection. Sometimes public WiFi will block, throttle, or limit certain connections on their network that can cause you to randomly or intermittently lose connections.
  2. Make sure you can connect via SSH - Log in to your account at cubbies.dev, copy the SSH command next to your running box, and paste that in to your command line. If you can't connect via SSH, follow the instructions above based on the error you get. If you can SSH in, check your IDEs connection profile and/or settings to make sure it matches the SSH command you just copied.
  3. Restart cubby - Depending on your workload, it's possible your cubby (just like any other computer) might just crash. You might have overloaded the processor, have a memory leak in one of the tools you're using, or altered a network setting that brought down the network connection. Generally, you can get back online by just restarting the cubby. If this happens often, though, you'll want to track down what's causing the crashes and address it.
  4. If none of these steps help, log in to your account at cubbies.dev, click the Support link in the footer, and fill out a support ticket so we can assist.


I'm trying to view work on my cubby in a browser and it won't connect

  1. Check your Internet - Make sure you are on an unrestricted Internet connection. Sometimes public WiFi will block, throttle, or limit certain connections on their network that can cause you to randomly or intermittently lose connections.
  2. Check the server/service - Depending on how you have the service set up that you're trying to view (PHP server, Nginx, Apache, dotnet, JBoss, PM2, npm run, etc), it might just be that the service itself is either not running or has encountered an issue. Check the status of the service and any logs related to double-check that it's actually running and healthy. 
  3. Check your ports - If you're using your cubby's IP address or hostname (*.cubby.zone), make sure the port you're trying to access (even port 80) is open on your cubby. By default, all the ports on your cubby will be inaccessible to the Internet. See: How to Share Work on my Cubby.
  4. Check your tools - If you're using port-forwarding and/or a tunnel (like using localhost with VSCode), make sure that the tool creating that forward or tunnel is running and healthy. It may be worth restarting that tool just to be sure.
  5. If none of these steps help, log in to your account at cubbies.dev, click the Support link in the footer, and fill out a support ticket so we can assist.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.