Cannot point core to local cloud - Resolved

Edit: I resolved this issue. I believe it was fixed when I updated the CLI but I also did the deep update at the same time so I’m not sure what actually did it.

The issue I was when I ran this command:
spark keys server IP_ADDRESS

It loaded the pem file but did not update the IP_ADDRESS. This caused the light to flash cyan.

To fix it I did the following:

sudo npm update -g spark-cli


spark flash --usb deep_update_2014_06

The problem is the core flashes rapid cyan and I see no evidence of it connecting in the server log. I did a tcpdump and I can see connection attempts to the amazon server. This indicates to me that the keys are updated but the core is still pointing to the cloud server.

This is the command I used:
spark keys server IP_ADDRESS

I have a couple of questions:

  1. Is there any way to force the core to point to the correct IP?
  2. Is there anyway to see where the core is pointing?
  3. How does the core know what port to use? Does it assume 8080?

Anything you can do to help would be appreciated!

I guess you have resolved this?

Yes I’ll make a edit.

@kennethlimcp I have one question though. When you run this command…

spark keys server IP_ADDRESS

Does it automatically point to 8080? If so is there a way to change this?

the IP_ADDRESS in this configuration is for COAP between the core and server.

COAP Port is fixed to 5683 and shouldn’t’ be changed.

8080 is for the API sever. You should most likely be able to change it here:

1 Like

Ah good to know! I was wondering why the server was reporting connecting to 5683. My printer software wants to connect through 8080 and was causing problems… I had to kill it.

Thank you for being so responsive!