Where does the "domoticz url" setting come from?

[jsiegmund]

I downloaded the ideAlarm scripts and tried to get them working. Noticed some errors in the logs that URLs could not be opened. When I check the scripts, the calls are constructed using the following setting:

domoticz.settings['Domoticz url']

This seems to be set to "127.0.0.1:80" which is not where my Domoticz install is running. So now my question is: where is this variable being set and why is it at the wrong value? I'm running everything under SSL by default to port 80 isn't even open.

[EdwinK]

The IP address 127.0.0.1 is a special-purpose IPv4 address called localhost or loopback address. All computers use this address as their own to communicate with it self.

[Hobbybob]

Agreed, the 127.0.0.1-part should be okay, but I think the standard Domoticz-port is 8080 (at least it is in my installation). So it should be "127.0.0.1:8080" I think.

[dannybloe]

That's weird indeed. I'd expect it to be 8080 (by default). dzVents gets that value from the event-system. Reading the C++ code it seems it gets it from the settings: our_listener_port = web_settings.listening_port;

[jsiegmund]

The IP address 127.0.0.1 is a special-purpose IPv4 address called localhost or loopback address. All computers use this address as their own to communicate with it self.

Yes, that part I know. The problem is not the loopback address, it's the wrong port number.

[jsiegmund]

That's weird indeed. I'd expect it to be 8080 (by default). dzVents gets that value from the event-system. Reading the C++ code it seems it gets it from the settings: our_listener_port = web_settings.listening_port;

Ok. And where does that settings object come from? Is it the stuff you specify in the domoticz.sh init script, or are they stored elsewhere? I'm running https only on 443, port 80 is not in use so I would not know where it got that. I could run it on 8080 as well just to be sure though. Also wonder what happens when it would call https://localhost since the ssl cert is not for localhost but for the FQDN. That should not work to begin with.