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

Best regards,
Pelle

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

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 =/

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.

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

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.

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.

Just a missing "e" is causing that much trouble

This never happened before, we're looking into it and will let you guys know when we know anything. Stay tuned for updates.

The issue came up when libcurl was updated to v7.53.0 in Lede, for whatever reason the URL to connect to the Cloud Device Server causes libcurl to throw an Invalid URL error.

This never happened before, we're looking into it and will let you guys know when we know anything. Stay tuned for updates.

That is good to know. Thanks.