According to the server headers nginx/1.10.3 is running on myopenhab.org.
The header also states that Ubuntu is running on it.
So according to the nginx version my conclusion would be that Ubuntu 16.04.X is running on that server.
Standard support ends in April 2021.
The only changes I see on git belong to updates related to OH3 although there are several users reporting back the same issues like those you have.
as already reported in reply #201, due to SD-card crash I lost my private cloud instance. After days of digging through this forum and Github, I have finally (!) managed to get the cloud back online. The time I invested to reinstall openhab-cloud was almost unbearable and if I hadnāt managed to install the cloud a couple of years ago, I would have given up by now and switched to different automation software.
HOWEVER, I did not. So, in case someone else runs into the same problem depicted in this post (and its replies), hereās my guide to saving precious live time .
Preface: Ryanās installation guide is still pretty comprehensive but needs a couple of adaptions, almost three years after the intial post. The steps below have been tested on following platform (and most likely will work on different setups, as well):
OH Version: 2.4 HW: RPi Zero + ENC28J60 OS : dietpi v6.33.3 & nginx 1.14.2
Make yourself familiar with Ryanās post (this one).
Step #7: Make sure, that you really DO install build-essential and python. Some users (including me) have reported that the installation process npm install broke, because the precompiled package bcrypt@1.0.2 was unavailable! According to bcrypt@github, this is not a problem: if a precompiled version of a package is unavailable for a specific platform, npm install falls back to compile from source automagically.
Step #7: do not pull the master trunk of openhab-cloud at GitHub - I wasnāt able to get that one running. Instead, pull tag 1.0.10: git clone --depth 1 --branch 1.0.10 https://github.com/openhab/openhab-cloud.git
Step #7: Make sure that you install NodeJS, no other than v7.10.1, the install process will fail otherwise. If there is no setup-script for your architecture, donāt worry! You can follow the manual install instructions on GitHub - no problem.
Step #7: When I first tried to run the cloud with node app.js, the console log reported āunmet dependenciesā. After a while of googling I found this on GitHub. If the cloud does not start after the first npm install, try at least npm install bcryptjs@^2.4.3 qunitjs@^2.0.0 npm install node-time
which will post-install 3 more packages.
Reply #28 suggests using Unitechās Process Manager PM2 to have app.js run as a system service. As openhab-cloud is tied to NodeJS v7.10.1, cloning the github repository from the latest branch is again no option. I found that PM2 versions below 4.x.x actually work with NodeJS v7.10.1 npm install pm2@3.5.0 -g (as root) and then pm2 startup
Consult Readme.MD for details on PM2!
Hope this helps!
Good luck & Best regards,
-bernie
Has anyone launched a cloud on OH3?
Everything worked fine for me on OH2.5, but on OH3 I canāt go further than the HOME page.
A similar problem and its solution are described here https://github.com/openhab/openhab-cloud/issues/313, but nothing works for me.
Adding <āproxyHostā: home.openhab.mydomain.co> to config.json does not solve the problem. Apparently you need to implement all the actions described in the penultimate post, but here my knowledge is not enough.
i tried to install the cloud server with the steps described at the first post.
At the point i have to start āapp.jsā i get the following error:
sudo node app.js
{"errno":-2,"syscall":"open","code":"ENOENT","path":"certs/aps/AuthKey.p8"}
(node:43041) Warning: Accessing non-existent property 'MongoError' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)
node_redis: Warning: Redis server does not require a password, but a password was supplied.
I am trying to install it on a āfreshā vserver (ubuntu 20.04).
I found a similar issue. This seems to be due to the APN config. I do not use it, so I have a dummy config for it (oh-cloud wonāt seem to start without it), but the file referred to in the signingKey parameter still neds to exist even if empty.
I have this in my config:
"apn" : {
[... rest of apm config here, even if "dummy" ...]
"signingKey": "aps.p8"
},
And then just created an empty āaps.p8ā file in the same directory as the config.js.
Thank you!
I created the path /certs/aps/AuthKey.p8 with an empty file.
Also i removed the password line from config.json for redis.
After these two changed i only get one error message:
(node:43041) Warning: Accessing non-existent property 'MongoError' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)
Iām also having the same issues. When I moved from S2300 to S2306 my cloud connector started to have some issues. I attempted to update and now Iām down with the same errors.
I have removed the apn section and the node just crashes. Doesnāt write any logs either.
# node app.js
(node:12469) Warning: Accessing non-existent property 'MongoError' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)
#
I just pulled down the latest published docker image and ran against my config without the APN section and it works for me. Can you verify your config file is properly formed after removing the APN section? Thats the only thing i can think of that might cause a quick crash.
Iāll recheck, but all I did was delete the lines in full. Iām also not running docker, im running native on the box as this was just an upgrade for me.
Go figure this one out, it works when i build a docker image locally. The pulled image doesnāt work. Native doesnāt work. I made no changes to the configs after I did docker pull versus docker build.
What docker image are you using, iām assuming the latest tag? (i have not tagged a version number yet) Also did you do a npm install when building locally? Thats the only thing i can think of that would be different from building and running with docker vs running node alone.