Openhab cloud stopped working after update of local openhab instance

Setup, Configuration and Use Installation
1

Hi,
I updated my openhab instance and the version running now is 4.1.0.M3.
Now I can’t access my openhab cloud instance anymore.
image

Is this just a coincidence that the system breaks right now?
I don’t think so but I cannot think of a reason why the openhab cloude instance should stop working because of an update of the locale openhab instance.

If somebody could point me into the right direction would be great!

Best regards

2

What version did you update from?
When you say openhab cloud, are you referring to myopenhab?

3

It is your cloud instance or the one of myopenhab.org

4

Thanks for the reply @brianlay @Wolfgang_S

I’m using my own openhab cloud instance.

And because of problems with a device I switched to testing and I was under the impression that I’m still using it, since I did not change it but apperently I’m using release
image

I first performed an “apt upgrade” and then I executed points 02 and 03 in openhabian-config.
Could this be the problem?
Otherwise, the system runs as usual, so I wouldn’t assume that anything has gone wrong.

The message on the server has also changed.
image

Maybe it really is just a coincidence and I should concentrate on getting the server up and running again?

Best regards

5

What do you nginx logs and openhab-cloud logs show ?

6

proxy_error_log of domain home.mydomain.de is filling up with this

2023/11/12 15:58:54 [error] 1137259#0: *431943 connect() failed (111: Connection refused) while connecting to upstream, client: <LOCAL-IP>, server: home.mydomain.de, request: "GET /rest/events/states HTTP/1.1", upstream: "http://<SERVER-IP>:3000/rest/events/states", host: "home.mydomain.de", referrer: "https://home.mydomain.de/"

proxy_error_log of domain openhab.mydomain.de is full with this

2023/11/12 16:04:16 [error] 1137259#0: *435852 open() "/var/www/vhosts/mydomain.de/httpdocs/hosting/capabilities" failed (2: No such file or directory), client: <SERVER-IP>, server: mydomain.de, request: "GET /hosting/capabilities HTTP/1.1", host: "mydomain.de"

this message has been there for a long time so I don’t think it is connected to my issue.

2023-11-12 01:14:58:5858 error: uncaughtException: write EPIPE
Error: write EPIPE
    at afterWriteDispatched (node:internal/stream_base_commons:160:15)
    at writeGeneric (node:internal/stream_base_commons:151:3)
    at Socket._writeGeneric (node:net:905:11)
    at Socket._write (node:net:917:8)
    at writeOrBuffer (node:internal/streams/writable:391:12)
    at _write (node:internal/streams/writable:332:10)
    at Socket.Writable.write (node:internal/streams/writable:336:10)
    at console.value (node:internal/console/constructor:299:16)
    at console.log (node:internal/console/constructor:376:26)
    at consoleCall (<anonymous>)
    at process.<anonymous> (/var/www/vhosts/mydomain.de/openhab.mydomain.de/app.js:44:13)
    at process.emit (node:events:525:35)
    at process._fatalException (node:internal/process/execution:149:25)
2023-11-12 01:14:58:5858 error: undefined
2023-11-12 01:14:58:5858 warn: GCM XMPP error: Error: self signed certificate
2023-11-12 01:14:58:5858 warn: GCM XMPP error: Error: self signed certificate
2023-11-12 01:14:59:5959 warn: GCM XMPP error: Error: self signed certificate
2023-11-12 01:14:59:5959 warn: GCM XMPP error: Error: self signed certificate

This was the last time I got an gateway time-out. After that there is only warn: GCM XMPP error: Error: self signed certificate in the logs.

7

I was looking for the error message and I found my own thread that I posted above. I remembered that back than the instance was not running correctly, so I restarted not just the service (what I did yesterday) but the hole server and the locale instance. Now it’s working again. I have no idea what happened or why it happened. :man_shrugging:t3:

Nevertheless, thanks for all the help!

Best regards

1 Like