CryptoStream transform error TypeError: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt
onSocketData called, but no data sent.
You might want to try flashing the server key again. There seems to be some error and the core should be breathing cyan as per normal.
Seems like you are not familiar with the normal setup yetā¦ Might want to play around with the core and understand how things are working before playing with the local ?
Thank you so much for help @kennethlimcp, I solved the problem, and the core is able to connect local cloud and easily switch to the spark cloud. However, when the core is connecting to the spark cloud, I ran
Iāve been trying to get the local cloud working again after a change of computer. I can get the local cloud server up and running and connecting to the core which is breathing cyan happily. The problem I have is setting up the account and getting a token so I can access the core with curl. I have tried to access the connected core with/without an access token, but it doesnāt matter what I try everything comes back with invalid tokenā¦
I try it with the server running and not running. So I never seem to be able to create an account! Each time the server starts it comes up with the message:
"No users exist, you should create some users!"
Easier said than done.
Without an account you cannot get a token, and no token: no access, so how do I create an account and get a token I can use to access the core given the situation Iām in?
My local cloud server identifies with two cores, but it seems it does not recognize any accounts, and I cannot find any reference other than ānullā to any tokens in the config files.
Apologies, yes I used spark setup as per your tutorial. Is there somewhere the spark ecosystem is described so I can understand it better (without needing a phd!)?
Thanks,
R
I deleted everything and re-installed the server, ran it once and then began this tutorial. Hereās a screen shot of what I did. To be clear the server was NOT running when I did all this. Itās not clear from the tutorial whether it should be.
Note that after I entered the "spark config ks1 ā192.168.1.81:8080ā the config had not switched to ks1, so I did this manually before executing spark startup.
I would very much like to read about the ecosystem, so if you could point me to something that describes it, Iād be most grateful. Iāve looked around, but cannot find anything.
@kennethlimcp
Hi,
I'm trying to setup a local cloud running spark-server on a raspberry pi following the tutorial. The server is running and giving me a public key. I've also generated a local profile that holds the settings for my local cloud:
Current profile: local
Using API: http://192.168.178.25:8080
I've used spark keys send to transfer the core keys to the server and copied the server public keys to my core using
spark keys server default_key.pub.pem IP_ADDRESS
I registered a new user on my local cloud using spark setup
After reset the core connects (flashing green, then breathing cyan) but I get the following output from the server:
After a few seconds the core flashes cyan faster and tries to connect again resulting in the same server output (connection id increments)
I checked my raspberry installation and the only obvious difference I could find was the version of the node.js module (0.12.0) instead of 0.10.29 as in the tutorial.
I'm doing all interaction with my local cloud and the core from a Windows PC.
Reinstalled Rasbian (rollback was not possible/failed), installed node 0.10.36 (couldnāt find 0.10.29 for the Pi) and now everything is working. Iām not sure if this was really the version rollback, might have also been the Rasbian re-installā¦
BTW: I had no problems with the usra and express modules as indicated in your docs.
I also made the Windows local cloud work.
Thereās another thing I noticed though: I can only subscribe to all events (GET /v1/events) or named events (GET /v1/events/:event_name) but not to core specific events. This was indicated in another thread already, but it was not 100% clear to me which event subscriptions work.