No access to IP:8083 page

Discussions about RaZberry - Z-Wave board for Raspberry computer
Post Reply
testerbb
Posts: 3
Joined: 04 May 2018 21:11

No access to IP:8083 page

Post by testerbb » 04 May 2018 21:29

Hi everybody

I'm new here, because i started to play around with my raspberry and the option of zwave is very interesting.
Nevertheless, i followed the installation procedure, all works fine.
By accessing the page https://find.z-wave.me/zboxweb the link with the IP is visible, ok.
By clicking and going to the page: IP:8083 an error message is displayed: unable to connect. It seems the server is not running, but it does. Checked with z-way server status. even with localhost:8083 the same error is shown.
Do i have to configure my router or where could be the error?

Thanks in advance for your help

adamjarema
Posts: 4
Joined: 04 May 2018 03:10

Re: No access to IP:8083 page

Post by adamjarema » 05 May 2018 05:25

Can you check any log pages? I'm having this issue too. What I am finding is that the z-way server process is not actually starting. If you look at: systemctl status z-way-server it should tell you if it is running or has exited.

testerbb
Posts: 3
Joined: 04 May 2018 21:11

Re: No access to IP:8083 page

Post by testerbb » 05 May 2018 10:12

In my eyes its running.. isn't it?

pi@raspberrypi:~ $ systemctl status z-way-server
● z-way-server.service - LSB: RaZberry Z-Wave service
Loaded: loaded (/etc/init.d/z-way-server; generated; vendor preset: enabled)
Active: active (exited) since Wed 2018-05-02 21:00:38 CEST; 2 days ago
Docs: man:systemd-sysv-generator(8)
Process: 318 ExecStart=/etc/init.d/z-way-server start (code=exited, status=0/S
CGroup: /system.slice/z-way-server.service

May 02 21:00:38 raspberrypi systemd[1]: Starting LSB: RaZberry Z-Wave service...
May 02 21:00:38 raspberrypi z-way-server[318]: Starting z-way-server: done.
May 02 21:00:38 raspberrypi systemd[1]: Started LSB: RaZberry Z-Wave service.

adamjarema
Posts: 4
Joined: 04 May 2018 03:10

Re: No access to IP:8083 page

Post by adamjarema » 08 May 2018 06:15

No, it has exited. Seems you and I have the same problem. Interesting.

Brekne
Posts: 10
Joined: 09 Aug 2017 16:52

Re: No access to IP:8083 page

Post by Brekne » 09 May 2018 19:33

Backend server error. When will this problem be solved. Have no remote access to my 2 razberries. Frustrated

testerbb
Posts: 3
Joined: 04 May 2018 21:11

Re: No access to IP:8083 page

Post by testerbb » 09 May 2018 21:34

Does anybody have any ideas to solve the problem?

adamjarema
Posts: 4
Joined: 04 May 2018 03:10

Re: No access to IP:8083 page

Post by adamjarema » 11 May 2018 03:05

My problem with this is that I'm not getting any logs from the z-way server. I think it has something to do with one of the packages being updated that the server depends on, but that's just a hunch.

mtylerb
Posts: 1
Joined: 07 Jun 2018 10:06

Re: No access to IP:8083 page

Post by mtylerb » 07 Jun 2018 10:09

I know it's been almost a month, but I thought you might be interested in the solution I found with the help of the github issues. I'm copying this directly from the Raspbian forum where I had previously asked for help:

Well, answered my own question after having a eureka "search idea" moment. I found a github issue with a specific response that seems to have solve the problem. So for others:

Code: Select all

$ cd \tmp
$ wget http://mirrordirector.raspbian.org/raspbian/pool/main/o/openssl/libssl1.0.0_1.0.1t-1+deb8u8_armhf.deb
$ sudo dpkg -x libssl1.0.0_1.0.1t-1+deb8u8_armhf.deb .
$ sudo mv usr/lib/arm-linux-gnueabihf/lib* /opt/z-way-server/libs/
Please keep in mind that the filename had changed from the original response in the github issue. I had to traverse the URL directories to discover that libssl1.0.0_1.0.1t-1+deb8u7_armhf.deb had become libssl1.0.0_1.0.1t-1+deb8u8_armhf.deb. So if you get a 404 error with the wget command, you may need to do something similar. The problem occurs due to the change in libssl from 1.0.0 to 1.0.2, so you're looking specifically for libssl1.0.0.

With that in, my problem seems to be solved for the moment. They're planning on updating to stretch, but they seem to be on the slower side. At least it runs.

Post Reply