Domoticz does not open port 8080

[MasWetens]

Dear Domoticz,

I installed Domoticz already several times using the following command:
"Sudo curl -L install.domoticz.com | (sudo) bash"

When I check the installation using:
"wget localhost"
Isn't the port 8080 showing up, but I set in de setting that popped up when I installed it at port 8080.
What can I do to solve this problem????

[pvm]

Code: Select all

wget localhost:8080

does not result in an index.html file?

[MasWetens]

When I do

Code: Select all

wget localhost:8080

Get I a return as follows:

Code: Select all

--2017-09-04 16:55:52--  http://localhost:8080/
Resolving localhost (localhost)... ::1, 127.0.0.1
Connecting to localhost (localhost)|::1|:8080... failed: Connection refused.
Connecting to localhost (localhost)|127.0.0.1|:8080... failed: Connection refused.

Thank you for your reaction pvm.

[Elvana]

Hi, I had the same issue.
As a NOOB it took me some time to work this out... which is why I am sharing the following in boring detail.
On a new 16 GB SDcard I had installed Raspbian Stretch from https://www.raspberrypi.org/downloads/raspbian/
Upon starting the partition size was automically adjusted.
After opening a terminal window I ran sudo raspi-config and changed password, timezone, ssh access and screen resolution and overscan (last three under interfacing options).
Then rebooted in the terminal window by issuing

Code: Select all

sudo reboot

I then installed Domoticz "The Easy Way" according to https://www.domoticz.com/wiki/Installin ... e_easy_way with

Code: Select all

sudo curl -L install.domoticz.com | sudo bash

This ran successfully but yielded Domoticz inaccessible (with and without https enabled - no difference).

Like the topic starter - after a reboot I could not access Domoticz on either port 8080 or 443:

Code: Select all

pi@domoticzR1:~ $ wget localhost:8080
--2017-09-12 11:10:09--  http://localhost:8080/
Resolving localhost (localhost)... ::1, 127.0.0.1
Connecting to localhost (localhost)|::1|:8080... failed: Connection refused.
Connecting to localhost (localhost)|127.0.0.1|:8080... failed: Connection refused.

I found this topic as well as this other one viewtopic.php?t=18020 and my error message read:

Code: Select all

sudo service domoticz.sh status
● domoticz.service - LSB: Home Automation System
   Loaded: loaded (/etc/init.d/domoticz.sh; generated; vendor preset: enabled)
   Active: active (exited) since Tue 2017-09-12 11:08:28 CEST; 6min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 1100 ExecStop=/etc/init.d/domoticz.sh stop (code=exited, status=0/SUCCESS)
  Process: 1110 ExecStart=/etc/init.d/domoticz.sh start (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/domoticz.service

Sep 12 11:08:27 domoticzR1 systemd[1]: Starting LSB: Home Automation System...
Sep 12 11:08:28 domoticzR1 domoticz.sh[1110]: /home/pi/domoticz/domoticz: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file:
Sep 12 11:08:28 domoticzR1 systemd[1]: Started LSB: Home Automation System.

From a browser window on the raspberry I downloaded the armhf version of libssl.so.1.0.0 from https://packages.debian.org/jessie/libssl1.0.0
In a terminal window I installed the package:

Code: Select all

pi@domoticzR1:~ $ cd Downloads
pi@domoticzR1:~/Downloads $ sudo dpkg -i libssl1.0.0*
Selecting previously unselected package libssl1.0.0:armhf.
(Reading database ... 122756 files and directories currently installed.)
Preparing to unpack libssl1.0.0_1.0.1t-1+deb8u6_armhf.deb ...
Unpacking libssl1.0.0:armhf (1.0.1t-1+deb8u6) ...
Setting up libssl1.0.0:armhf (1.0.1t-1+deb8u6) ...

stopped and restarted Domoticz (a reboot should also work):

Code: Select all

pi@domoticzR1:~/Downloads $ cd ..
pi@domoticzR1:~ $ sudo service domoticz.sh stop
pi@domoticzR1:~ $ sudo service domoticz.sh start

then checked availability of Domoticz on port 8080:

Code: Select all

pi@domoticzR1:~ $ wget 127.0.0.1:8080
--2017-09-12 12:01:53--  http://127.0.0.1:8080/
Connecting to 127.0.0.1:8080... connected.
HTTP request sent, awaiting response... 200 OK
Length: 90327 (88K) [text/html]
Saving to: ‘index.html’

index.html          100%[===================>]  88.21K  --.-KB/s    in 0.002s  

2017-09-12 12:01:53 (57.4 MB/s) - ‘index.html’ saved [90327/90327]

after this I could also access Domoticz from other devices.

[wegen]

hello,

sorry for this simple question...

how did you put libssl.so.1.0.0 in the download directory?
wich version of this lib did you use?

Many thanks for your answers

[koowee]

here is one way how you can do it
http://www.domoticz.com/forum/viewtopic ... 20#p150258

[wegen]

here is one way how you can do it
http://www.domoticz.com/forum/viewtopic ... 20#p150258

Many thanks for your help. I did it but I still become this page : Apache2 Debian Default Page

Any idea?

[SweetPants]

Many thanks for your help. I did it but I still become this page : Apache2 Debian Default Page Any idea?

Ehhh "Apache2 Debian Default page" suggests you have apache installed too. Domoticz has it's own web server (not apache). Does that run on 8080 too? Try starting domoticz manually with a different "-www port"

[wegen]

Many thanks for your help. I did it but I still become this page : Apache2 Debian Default Page Any idea?

Ehhh "Apache2 Debian Default page" suggests you have apache installed too. Domoticz has it's own web server (not apache). Does that run on 8080 too? Try starting domoticz manually with a different "-www port"

I really need your help. Could you contact me private?

[wegen]

I still don't get it:

Code: Select all

pi@raspberrypi:~/domoticz $ wget 192.168.1.112:8080
--2017-09-17 20:20:40--  http://192.168.1.112:8080/
Connecting to 192.168.1.112:8080... failed: Connection refused.

I followed those steps:

Install Raspbian desktop edition
activate ssh by creating ssh file in boot
connect via putty, user pi
run command

Code: Select all

sudo curl -L install.domoticz.com | sudo bash

run command

Code: Select all

cd domoticz
./updaterelease

Code: Select all

wget http://mirrordirector.raspbian.org/raspbian/pool/main/o/openssl/libssl1.0.0_1.0.1t-1+deb8u6_armhf.deb
sudo dpkg -i libssl1.0.0_1.0.1t-1+deb8u6_armhf.deb

Code: Select all

sudo curl -L install.domoticz.com

I cannot reach my roboticz at the adress: 192.168.1.112:8080
ping on 192.168.1.112 works
I use RPI3

Many thanks for your help

[jandirkv]

I have also a problem with remote access. Port 8080 is open and forwarded in my router to the Domoticz ip. But when I try to access I get routed to the login page of my router.

[jandirkv]

I finale have a solution. The problem was My router. I have a new one and all my problems are solved. Thanks for all the help

[SweetPants]

I have also a problem with remote access. Port 8080 is open and forwarded in my router to the Domoticz ip. But when I try to access I get routed to the login page of my router.

Please be aware this (HTTP) is highly insecure. Better switch to HTTPS (443) and use Certificates or a VPN connection.

[Tonio16]

Hello

I have two domoticz at home. One on a Pi B+ and a second on a Pi 3+.
Today, for less than 1 hour, I have the offline page on the Pi 3+. Just after I finaly set up the Synology monitoring: https://www.domoticz.com/wiki/NAS_Monitoring#Synology
I also made an apt-get update/upgrade this afternoon but it was working fine after though I made several reboots.

If i do the wget:

Code: Select all

wget localhost:8080
--2018-08-01 21:45:53--  http://localhost:8080/
Résolution de localhost (localhost)… ::1, 127.0.0.1
Connexion à localhost (localhost)|::1|:8080… échec : Connexion refusée.
Connexion à localhost (localhost)|127.0.0.1|:8080… échec : Connexion refusée.

but the service is running

Code: Select all

domoticz@raspberrypi:~ $ sudo /etc/init.d/domoticz.sh status
● domoticz.service - LSB: Home Automation System
   Loaded: loaded (/etc/init.d/domoticz.sh; generated; vendor preset: enabled)
   Active: active (exited) since Wed 2018-08-01 21:25:14 CEST; 25min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 528 ExecStart=/etc/init.d/domoticz.sh start (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/domoticz.service

aoû 01 21:25:13 raspberrypi systemd[1]: Starting LSB: Home Automation System...
aoû 01 21:25:14 raspberrypi domoticz.sh[528]: 2018-08-01 21:25:14.741  Stat…Cuz
aoû 01 21:25:14 raspberrypi domoticz.sh[528]: 2018-08-01 21:25:14.754  Stat…:51
aoû 01 21:25:14 raspberrypi domoticz.sh[528]: 2018-08-01 21:25:14.766  Stat…cz/
aoû 01 21:25:14 raspberrypi domoticz.sh[528]: domoticz: Domoticz is startin…...
aoû 01 21:25:14 raspberrypi domoticz[548]: Domoticz is starting up....
aoû 01 21:25:14 raspberrypi domoticz[588]: Domoticz running...
aoû 01 21:25:14 raspberrypi systemd[1]: Started LSB: Home Automation System.
Hint: Some lines were ellipsized, use -l to show in full.

[Koensk]

This looks the same with me. But from another pc I cannot connect. Hows that possible?

Code: Select all

pi@domoticzR1:~ $ wget 127.0.0.1:8080
--2017-09-12 12:01:53--  http://127.0.0.1:8080/
Connecting to 127.0.0.1:8080... connected.
HTTP request sent, awaiting response... 200 OK
Length: 90327 (88K) [text/html]
Saving to: ‘index.html’

index.html          100%[===================>]  88.21K  --.-KB/s    in 0.002s  

2017-09-12 12:01:53 (57.4 MB/s) - ‘index.html’ saved [90327/90327]

[jornm]

To make i easier for people to help you troubleshoot run the command:

sudo netstat -lpn

and paste the result.

This will show what process is listening on which port.

[m.versteegh]

To make i easier for people to help you troubleshoot run the command:

sudo netstat -lpn

and paste the result.

This will show what process is listening on which port.

I'm facing the same issue. Seems domoticz is running, but I'm not able to access the GUI. I guess the webserver is not running as shown below by a netstat output. Any hints?

Note: Running on a 1st generation Pi, 2B, most recent beta version of domoticz. Domoticz itself is running, at least that what service domoticz status states.

Code: Select all

Proto RefCnt Flags       Type       State         I-Node   PID/Program name     Path
unix  2      [ ACC ]     SEQPACKET  LISTENING     6398     1/init               /run/udev/control
unix  2      [ ACC ]     STREAM     LISTENING     11525    429/python3          /var/run/fail2ban/fail2ban.sock
unix  2      [ ACC ]     STREAM     LISTENING     12084    511/systemd          /run/user/1000/systemd/private
unix  2      [ ACC ]     STREAM     LISTENING     12089    511/systemd          /run/user/1000/gnupg/S.gpg-agent.extra
unix  2      [ ACC ]     STREAM     LISTENING     12092    511/systemd          /run/user/1000/gnupg/S.gpg-agent.browser
unix  2      [ ACC ]     STREAM     LISTENING     12094    511/systemd          /run/user/1000/gnupg/S.gpg-agent
unix  2      [ ACC ]     STREAM     LISTENING     12096    511/systemd          /run/user/1000/gnupg/S.gpg-agent.ssh
unix  2      [ ACC ]     STREAM     LISTENING     8263     1/init               /run/thd.socket
unix  2      [ ACC ]     STREAM     LISTENING     8265     1/init               /var/run/avahi-daemon/socket
unix  2      [ ACC ]     STREAM     LISTENING     8268     1/init               /var/run/dbus/system_bus_socket
unix  2      [ ACC ]     STREAM     LISTENING     6065     1/init               /run/systemd/private
unix  2      [ ACC ]     STREAM     LISTENING     8883     362/dhcpcd           /var/run/dhcpcd.sock
unix  2      [ ACC ]     STREAM     LISTENING     8885     362/dhcpcd           /var/run/dhcpcd.unpriv.sock
unix  2      [ ACC ]     STREAM     LISTENING     6085     1/init               /run/systemd/fsck.progress
unix  2      [ ACC ]     STREAM     LISTENING     6087     1/init               /run/systemd/journal/stdout

[m.versteegh]

Nobody?

[waaren]

Nobody?

can you see anything in the domoticz logfile ?
what do you see when you do a sudo ps -ef | grep domo from the commandLine ?

[m.versteegh]

Nobody?

can you see anything in the domoticz logfile ?
what do you see when you do a sudo ps -ef | grep domo from the commandLine ?

I've initialised logging and rebooted the system, so it's a fresh log. It starts with the items as provided below. The log does contain a error, but that is related to InfluxDB. Based on the log, I would say that it has fired up the server running at 8443.

The result of sudo ps -ef | grep domo is:

Code: Select all

pi         555   524  0 14:38 pts/0    00:00:00 grep --color=auto domo

The logfile:

Code: Select all

019-01-01 14:29:50.317  Status: Domoticz V4.10304 (c)2012-2018 GizMoCuz
2019-01-01 14:29:50.327  Status: Build Hash: 30480b21, Date: 2018-12-30 09:37:02
2019-01-01 14:29:50.339  Status: Startup Path: /home/pi/domoticz/
2019-01-01 14:29:51.328  Sunrise: 08:45:00 SunSet: 16:39:00
2019-01-01 14:29:51.328  Day length: 07:54:00 Sun at south: 12:05:00
2019-01-01 14:29:51.328  Civil twilight start: 08:05:00 Civil twilight end: 17:19:00
2019-01-01 14:29:51.328  Nautical twilight start: 07:22:00 Nautical twilight end: 18:02:00
2019-01-01 14:29:51.340  Astronomical twilight start: 06:41:00 Astronomical twilight end: 18:43:00
2019-01-01 14:29:51.347  Status: EventSystem: reset all events...
2019-01-01 14:29:55.066  Status: PluginSystem: Started, Python version '3.5.3'.
2019-01-01 14:29:55.318  Active notification Subsystems: (0/13)
2019-01-01 14:29:55.388  Status: WebServer(HTTP) started on address: :: with port 8080
2019-01-01 14:29:55.603  Status: WebServer(SSL) started on address: :: with port 8443
2019-01-01 14:29:55.645  Status: Proxymanager started.
2019-01-01 14:29:55.709  Status: Camera: settings (re)loaded
2019-01-01 14:29:55.714  Starting shared server on: :::6144
2019-01-01 14:29:55.749  Status: TCPServer: shared server started...
2019-01-01 14:29:55.749  Status: RxQueue: queue worker started...
2019-01-01 14:29:57.753  Status: XiaomiGateway (ID=5): Delaying worker startup...
2019-01-01 14:29:58.254  Status: OpenZWave: using config in: /home/pi/domoticz/Config/
2019-01-01 14:29:58.321  Status: OpenZWave: Starting...
2019-01-01 14:29:58.321  Status: OpenZWave: Version: 1.4-3276-g43740494-dirty
2019-01-01 14:29:59.634  Status: OpenZWave: Driver Ready