Can't register device on cloud [resolved]



  • Got my Omega2+ all set up with wifi and everything.
    Trying to connect it to the cloud from the console, but when I click the "Register device on cloud"-button it gives me an iframe that points to https://registerdevice.onion.io/, a page describing what's great about the cloud but nothing more.

    alt text

    What to do? Is there any other URL I should use?

    Best regards,
    Pelle



  • Strange ...

    https://cloud.onion.io try this....



  • Hm, registerdevice.onion.io redirects me to cloud.onion.io now, very strange.
    Anyways, it works now :)



  • I did mine too, but it won't go online, it has been register directly off onion omega2+ and itself turns offline. Any help please? Device status says online on the omega.



  • @David-Wickenden said in Can't register device on cloud:

    I did mine too, but it won't go online, it has been register directly off onion omega2+ and itself turns offline. Any help please? Device status says online on the omega.

    Yeah, having the same problem right now =/



  • It looks like there is a problem in Omega firmware.

    Running device-client -v results in this repeating over and over again.

      > Restarting connection (restart #3) ...
    >> Starting device client
    >> Starting listening...
    '> Sending request to 'ds.onion.io/5a4af900-e5e4-4c2e-9787-e0d041f5f312/listen?key=LBHkOoFxEUXkGYjlwB4eguTwyrCild4OddKhBC4ro2dkY1PiqDEnsTkXIo2xgemd
    Error: curl_easy_perform: Illegal characters found in URL (3)
    >> Completed GET
    > Connection lost!
    

    Device id and device key in the web request are correct and going to that link in browser actually makes the device appear online. (I changed the id and key in the code above so nobody plays with my device.)

    Which means problem is in device-client.



  • @Jakub-Valtar I have the same issue. One thing I feel here - bad cURL config.



  • same here. Google says : Potential issue with no carriage return on string but hex 0d... Where is this string coming from ? Putting it into browser works, device is then online



  • @Thilo-Röhl Should I downgrade ? How ? To which version ?



  • I would like to have a debug version with a string to hex function here :)



  • Still no news how to get out of this problem?



  • Hi,
    I have got the same problem. Anyone knows how to fix it?
    Regards,
    Patrick



  • The same issue over here. The device is visible in device manager right after registering but immediately shows as offline...



  • I had the same problem and I was able to "fix" it by downgrading to the latest 1.5 image (omega2p-v0.1.5-b135.bin)



  • Same issue. I had tried both from the onion, the web interface and the cloud and it always shows offline. Get the same curl complaint.



  • If someone with 1.6 or 1.7 could check what versions they have for the following software:
    device-client - 0.6-1
    libcurl - 7.51.0-1
    we may be able to track it down.

    I am still unable to use the device explorer but i get the following when i run device-client:

    > Omega identified as device [omitted]
    > Sending response to device-server
    > Connection initialized
    > Sending response to device-server
    > Received command request for 'network.interface.wwan' group, 'status' function
    > Sending POST response
    > Sending response to device-server
    > Received command request for 'network.interface.wwan' group, 'status' function
    {}> Sending POST response
    {}{}> Sending response to device-server
    > Connection heartbeat

    ....

    sometime later:

    {}Error: curl_easy_perform: transfer closed with outstanding read data remaining (18)
    > Connection lost!
    > Restarting connection (restart #1) ...

    Running device-client in verbose i notice that it tries to run ubus list -v which causes command failed. I think it should run ubus -v list for the json output. Anyway I tried with a wrapper script to switch the two parameters in only that case but that fails terribly (openwrt does not like it at all). Here is the output from device-client with a lot omitted as i have no idea what is sensitive:

    >> RESPONSE THREAD!
    > Sending response to device-server
    >> Found 'group' and 'method' objects
    > Received command request for 'file' group, 'exec' function
    >> Parameters: '{ "command": "ubus", "params": [ "list", "-v" ] }'
    >> Launching ubus call
    > Sending POST response
    >> Sending POST to url: 'ds.onion.io/[omitted]?key=[omitted]', post data: '{"code":4,"stderr":"Command failed: Not found\n"}'
    {}>> POST Sent! (url: 'ds.onion.io/[omitted]/reply/[omitted]?key=[omitted])
    >> Closing RESPONSE THREAD



  • I am running firmware version 1.7 (b139) and have the same "Illegal characters found in URL" issue as described in this thread.

    To answer Markus' question I am running the same version of the software that are listed.

    @Markus-Schuss said in Can't register device on cloud:

    If someone with 1.6 or 1.7 could check what versions they have for the following software:
    device-client - 0.6-1
    libcurl - 7.51.0-1
    we may be able to track it down.



  • @Tomcom05
    The incorrect characters in the url are in the field "k'y" instead of"key".

    When tested with wget on a linux host with te command
    ds.onion.io/b8e2747e-18d2-4420-8955-2ada3e5ce13d/listen?key=z5fbkz2SFHEXDbKCgQCJ4yOsfTYfpcyBjgeWTb25EBUmyhXSfpg8iAYc0jy3LCDT
    the device gives a blue cloud sign.



  • @johan-ruijgt did you inform the onion.io team trough github?

    Just a missing "e" is causing that much trouble ;)



  • @johan-ruijgt I could not find k'y instead of key.
    I did the same as you did and did get the blue cloud but when it stopped or finished it revert back to no cloud. So something happening right there.



  • @David-Wickenden
    The device-client sent the incorrect string to ds.onion.io. This gives a error from the host.
    When simulate from a Linuc host with wget then it works for the time wget is active.
    If wget is closed there is a file with the response from ds.onio.io.
    In this file you can see the requested fields to the device-client.


Log in to reply