My Workspace seems to be down and not working

Platform Feedback & Bugs
1

My Workspace seems to be down and not working, I have tried to swap to 2 different browsers, firefox and chrome, I get the same error on both: which is a 404 app not found type of error

2

Hi @ZeeshanM — if you hit this, refresh the course page and you should see the Launch Workspace button again. It’s likely your workspace timed out after a bit of inactivity. Let me know if it happens again :folded_hands:

3

Hey Varun, so it actually Iv never seen it, I haven’t been able to start the workspace at all, every time I click start it simply loads and I get an error page

4

I am also getting the same error as Zeeshan :sob:

5

Hey @ZeeshanM and @000 — thanks for your patience.

@000 — yours was a separate issue specific to your username, and it’s now fixed. Next time you hit Start it should launch cleanly — give it a go and let me know.

@ZeeshanM — yours looks different. We’re looking into it and I’ll update this thread as soon as we have a fix.

6

Hi @ZeeshanM - this is fixed now! It was a routing bug on our end. Thanks so much for reporting it and sticking with us while we chased it down. I’ve added 5 hours of bonus workspace time to your account as a thank you - go ahead and launch again, it should come right up.

7

Seems to be working now, tysm, I was really excited about this course

1 Like
8

I am still getting the same 404 error in Firefox. I have refreshed but no change.

9

Thanks for reporting it @threent . We’re looking into it.

10

Hi @threent , can you refresh and check now. Alternatively you can stop and restart the workspace

11

Workspace starts but foxglove and gazebo just show the manual commands I would need to run in a terminal to start them. I would have expected them to start automatically ( I have not tried the manual commends yet)

I also notice that in VSCode there are six extensions requiring update but would not expect any of those to cause this problem.

Having opened a terminal in VSCode any copied in the first command shown for Gazebo I get the following error

Unable to read from the browser’s clipboard. Please make sure you have granted access for this website to read from the clipboard.

12

Good news: the earlier 404 was an internal configuration issue on our end, and it’s now fixed.

The part where Foxglove and Gazebo don’t auto-start is actually working as intended. We deliberately don’t hide those steps behind the scenes, because running the commands yourself is a real part of the workflow and stays useful well beyond this course.

A couple of specifics:

  • Gazebo needs a Gazebo server running in your workspace plus a websocket service to view it. Those are the same commands listed in the Gazebo view.
  • Foxglove connects to a running ROS system through a Foxglove bridge, so you’ll run that command the same way.
  • Run those in the workspace terminal and both panels will come alive. Let me know if you hit anything.

Thanks for highlighting this though. It’s possible other users might also be confused by this. I’ll update the course content with this mention.

13

How do I get to the workspace terminal. If I open a terminal in VSCode I get the error I added to my last post

I have also spotted in the faint print at the bottom of the Foxglove window that it requires Chrome but the tutorial text doesn’t suggest I need to download Chrome (or should that happen in the simulation?)

14

Can you try Ctrl + ` in VSCode?

15

Unfortunately I seem to have “run out of my free time for today” and can no longer access the simulation at all

16

Sorry for that. I’ve reset your usage for today. Try launching the workspace again.

About Foxglove let me confirm and get back.

17

I have tried “New Terminal Window” in VSCode which gives me a completely separate terminal window which just hangs (no error message) after posting the command.
Using “New terminal” gives the error as before.

Creating the terminal using ctrl ` seems to work but of course running the first gz command just starts the world and does not return control to the terminal to enter the second command ( I have confirmed this using a terminal on my laptop

18

Understood. Let me look into it and I’ll update as soon as possible.

19

@threent, can you try now? Menu → Terminal → New Terminal

20

This creates a terminal OK but running gz sim -r -s empty.sdf leaves the terminal opne ( I have confirmed this on my local install of gazebo) so I can not then go on to the second command. Should I create a second terminal to do this?