First time booting C-4 hub

🛎️ Get Help
6

I've tried that, but my system doesn't have that diagnostic Tool location.

7

When you're navigating to [your hub IP address]:8081, you are navigating to the diagnostic tool. Go there and post what version yours is at please.

8

Ahh. Ok. It doesn't have a version number anywhere on screen and I checked the source code, no hidden version number included.

Copyright 2018 if that helps.

9

Did you try browsing to http://[Your Hub IP]/hub/cloud/updateDiagnosticTool as the documentation page mentions?

10

Yeah, I've done that several times. It gives me the same connection refused message.

Really, just port 8081 connects. Nothing else seems to connect.

11

@tim.w.newsom Since you have a new C-4, your issue may be related to the link below. Not saying there's a fix here, but it's a likely explanation. If I remember correctly, support may need to do something on their end, but the hub should ultimately work. I'm almost positive there was another post somewhere saying how to handle this if the hub was never registered, but I can't find it now.

2 Likes
12

Great! That helps at least understand it, maybe. Lol

13

@gopher.ny might know how to help.

14

So, in Chrome dev tools, I can modify the web page that has the updater versions. If I knew the right code to put there, I could hack a submit that might perform the update.

But, that's pointless if the hub can't connect to cloud services in order to download the update.

I could host the update on my internal network update my internal dns so that it points to it... but I don't have the update file to host. Lol

Probably will need to have support help me resolve it.

1 Like
15

Lol. There’s no reason to hack anything. Someone will reach out soon and get you on your way.

2 Likes
16

Sorry for this dumb question, but you did substitute your actual IP address for the brackets and where it says your IP, correct?

E.g. http://[Your Hub IP]/hub/cloud/updateDiagnosticTool

If your hub IP address was, for example 192.168.1.2, then the URL for you would be...

http://192.168.1.2/hub/cloud/updateDiagnosticTool

1 Like
17

Hahaha. Yes. Love it.

1 Like
18

Thanks for confirming :joy:

1 Like
19

No worries. I spent the first part of my life in tech support for sound blaster.... so I totally understand where your question is coming from. :joy:

2 Likes
20

In that case, I guess I won't recommend the universal solution of rebooting. :slight_smile:

1 Like
21

Hahaha

22

Isn't it true that this won't work unless the platform is running already? Right now, AFAICT from @tim.w.newsom's description, there is nothing listening on TCP port 80.

If it cannot be done already, I think it would be great if there was a way to run the updateDiagnosticTool script from the Diagnostic Tool on port 8081.

23

That's how I understand it currently, @aaiyar.

1 Like
24

The URL in the doc will update the tool, but IIRC there was a cut off where it doesn’t work if it’s too old. This is an edge case, so creating a documented procedure might not make sense.

Blue light on the C4 doesn’t indicate there’s no platform running. Not sure what the issue is. Going to need @bobbyD or @gopher.ny to assist.

2 Likes
25

Let's try a few of things here... replace hubs.ip.address.here with actual IP.

  1. Run this in command prompt or terminal: curl -s -X POST http://hubs.ip.address.here:8081/api/getLatest
    This might get the latest version of hub software. I'm saying might because we don't know what the diagnostics tool version is.

  2. There may be a reset screen at http://hubs.ip.address.here:8081/resetHub, see if that works. If there is a screen, it should give some options, please PM me a screenshot.

  3. There also is a "last resort" URL at :slight_smile: CENSORED :slight_smile: ...

5 Likes