OK, in this case the java version is not the problem.
1 Like
After re-installing the connector, and putting new info on myopenhab…
2020-04-15 11:56:45.762 [ERROR] [io.openhabcloud.internal.CloudClient] - Error connecting to the openHAB Cloud instance: not authorized
That may take a few minutes/hours until everything gets registered??? 
1 Like
Ok, I can wait. I uninstalled the connector, then re-installed again just now…
2020-04-15 12:02:01.801 [DEBUG] [io.openhabcloud.internal.CloudClient] - Socket.IO connected
2020-04-15 12:02:01.803 [INFO ] [io.openhabcloud.internal.CloudClient] - Connected to the openHAB Cloud service (UUID = de09fc53-b654-40a8-8497-b99c36337c36, base URL = http://localhost:8080)
…I’ve been waiting for 2 years at this point…What’s another few hours… 
1 Like
Is the cloud showing as online now?
No sir
Last log was:
2020-04-15 12:02:01.801 [DEBUG] [io.openhabcloud.internal.CloudClient] - Socket.IO connected
2020-04-15 12:02:01.803 [INFO ] [io.openhabcloud.internal.CloudClient] - Connected to the openHAB Cloud service (UUID = de09fc53-b654-40a8-8497-b99c36337c36, base URL = http://localhost:8080)
This part may take some time before it goes online.
Did you check the console for the list mentioned above…and below. 
299 | Active | 80 | 1.0.0 | IO.Socket Engine Client
300 | Active | 80 | 1.0.0 | IO.Socket Socket Client
301 | Active | 80 | 20180813.0.0 | JSON in Java
302 | Active | 80 | 3.8.1.1 | Apache ServiceMix :: Bundles :: okhttp
303 | Active | 80 | 1.13.0.1 | Apache ServiceMix :: Bundles :: okio
304 | Active | 80 | 2.5.0.M4 | openHAB Add-ons :: Bundles :: IO :: openHAB Cloud Connector
300 │ Active │ 80 │ 1.0.0 │ IO.Socket Engine Client
301 │ Active │ 80 │ 1.0.0 │ IO.Socket Socket Client
302 │ Active │ 80 │ 20180813.0.0 │ JSON in Java
303 │ Active │ 80 │ 3.8.1.1 │ Apache ServiceMix :: Bundles ::
304 │ Active │ 80 │ 1.13.0.1 │ Apache ServiceMix :: Bundles ::
305 │ Active │ 80 │ 2.5.4.202004150418 │ openHAB Add-ons :: Bundles :: I
Still OFFLINE btw
All looks good. 
Now you can wait, hopefully not 2 years, 
or be impatient like me and restart OH a few more times. Just watch the logs and make sure it’s fully restarted between restarts.
After 3-4 restarts and it’s not online then I would just give it some time. 
EDIT: Does changing the log level to TRACE give any additional info?
1 Like
How to do that without looking it up?
From the console, I see in the logs above you have the binding set to DEBUG so just do the same except use TRACE instead.
There is now a lot more info, but I will have to look if anything about cloud connector…a few minutes please…
I don’t see anything having to do with the connector…even when I filter for “cloud”
Check /var/lib/openhab2/etc/org.ops4j.pax.web.cfg make sure you have this line and it’s not commented out or changed to use a different address:
org.ops4j.pax.web.listening.addresses = 0.0.0.0
It was hashed out
Do I need to stop openhab before I change it? What happens if I didint?
Try unhashing it or adding your servers IP address on a line below it.
Yes I would stop OH first.
I’m not really sure what could happen but it wouldn’t be a good idea to make changes to OH running except in /ect/openhab2/
I thought of that question too late…
Restarting…she froze up
You may need to reboot then do a few restarts.
What are you running OH on?
Last option is power down but that is when nothing else will work.
Ok, so I have another issue…EVERY time I either reboot, or restart, the RuleEngine and CloudConnector get uninstalled. Only those two.
rPi 3b+
root on SSD