Log flooded with msg 'Incoming connection from ..'

[bl34]

Hi,
I flood of messages in the log when I connect to Domoticz over http. Sometime it is 10ish messages, sometime 70,80..
The messages shown on connection from any IP in the local network at few ms interval, see below.
Not a problem per say but this behavior appeared as I moved to 2023.1.

Code: Select all

2023-05-30 09:37:42.342 Status: [web:8080] Incoming connection from: 192.168.1.11
2023-05-30 09:37:43.326 Status: [web:8080] Incoming connection from: 192.168.1.11
2023-05-30 09:37:43.332 Status: [web:8080] Incoming connection from: 192.168.1.11
2023-05-30 09:37:43.334 Status: [web:8080] Incoming connection from: 192.168.1.11 
...
 2023-05-30 09:37:43.633 Status: [web:8080] Incoming connection from: 192.168.1.11
2023-05-30 09:37:43.634 Status: [web:8080] Incoming connection from: 192.168.1.11
2023-05-30 09:37:43.634 Status: [web:8080] Incoming connection from: 192.168.1.11
2023-05-30 09:37:43.635 Status: [web:8080] Incoming connection from: 192.168.1.11
2023-05-30 09:37:43.636 Status: [web:8080] Incoming connection from: 192.168.1.11 

Help to find the root cause is much appreciated.
Thanks
Bruno

[waltervl]

something in your network is polling Domoticz a lot....

[bl34]

Hi Walter,
The flood only occurs as I connect to Domoticz using a web browser. This is on the first connection for any given device with an IP in the local network and regardless of the page I access. Once the connection is establish there is no more messages during further navigation in Domoticz.
Again no impact on Domoticz which works normally.
Just to dig a bit on this I'll try accessing a web page via other methods to see if it is browser related, who knows, or if this behaves the same with requests from other http clients.

[waltervl]

I see them too when I connect with my browser to domoticz, so seems a new feature of 2023.1

[FireWizard]

Hello,

I do not see multiple log messages, only one "Status: [web:8080] Incoming connection from: IP address", after connection.
Using latest beta 15255 and tested with both Firefox and Google Chrome in Linux.

Regards

[rfvdboom]

Same problem heren. Any fix?

2024-01-02 17:53:42.657 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.659 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.660 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.661 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.666 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.667 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.696 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.700 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.702 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.718 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.719 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.720 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.721 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.727 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.736 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.737 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.741 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.742 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.743 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.744 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.746 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.766 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.776 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.794 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.806 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.813 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.814 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.820 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.824 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.827 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.829 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.830 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.831 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.838 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.839 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.842 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.843 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.844 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.846 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.847 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.848 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.849 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.850 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.851 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.852 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.853 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.854 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.857 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.871 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.949 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:42.963 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:43.304 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:53:44.714 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:54:48.684 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:55:20.196 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:55:20.202 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:55:20.621 Status: [web:9876] Incoming connection from: 192.168.2.111
2024-01-02 17:55:21.680 Status: [web:9876] Incoming connection from: 192.168.2.111

[gizmocuz]

Do you have the same issue when using the Edge browser?
Could you also tell if this is happening when you use the browser in private mode?
192.168.2.111 is the machine where you opened the browser?

[rfvdboom]

Thx for reply. Found out that Firefox is the problem. When is use Chrome of Safari, i dont have te issue. Switched off "delete cookies and website data after shutdown", and the flooded log stopped. Problem solved.

[NvBgm]

Afther update to the last version i get all this connection. What is it and how to stop ??

2025-08-09 00:00:00.833 Status: dzVents: Write file: C:\Domoticz\scripts\dzVents\generated_scripts\!-Garagedeur.lua
2025-08-09 00:12:33.997 Status: [web:443] Incoming connection from: 146.70.185.32
2025-08-09 00:43:41.972 Status: [web:443] Incoming connection from: 91.231.89.120
2025-08-09 00:45:01.195 Status: [web:443] Incoming connection from: 91.231.89.123
2025-08-09 00:51:30.750 Status: [web:443] Incoming connection from: 91.196.152.73
2025-08-09 00:53:33.098 Status: [web:443] Incoming connection from: 91.196.152.51
2025-08-09 01:01:18.755 Status: [web:443] Incoming connection from: 138.246.253.24
2025-08-09 01:08:56.132 Status: [web:443] Incoming connection from: 104.248.130.34
2025-08-09 01:34:53.600 Status: [web:443] Incoming connection from: 91.231.89.125
2025-08-09 01:44:01.197 Status: [web:443] Incoming connection from: 195.189.97.10
2025-08-09 01:46:33.638 Status: [web:443] Incoming connection from: 91.196.152.152
2025-08-09 01:48:47.796 Status: [web:443] Incoming connection from: 194.50.16.252
2025-08-09 02:00:46.090 Status: [web:443] Incoming connection from: 159.89.133.223
2025-08-09 02:03:51.880 Status: [web:443] Incoming connection from: 185.177.72.5
2025-08-09 02:03:57.378 Status: [web:443] Incoming connection from: 51.254.49.96
2025-08-09 02:42:02.496 Status: [web:443] Incoming connection from: 195.189.97.10
2025-08-09 02:42:34.193 Status: [web:443] Incoming connection from: 202.93.141.18
2025-08-09 02:46:41.846 Status: [web:443] Incoming connection from: 216.73.216.85
2025-08-09 02:54:39.393 Status: [web:443] Incoming connection from: 20.65.194.129
2025-08-09 02:57:58.667 Status: [web:443] Incoming connection from: 194.50.16.252
2025-08-09 03:01:12.541 Status: [web:443] Incoming connection from: 51.254.49.96
2025-08-09 03:13:17.729 Status: [web:443] Incoming connection from: 194.50.16.252
2025-08-09 03:28:57.708 Status: [web:443] Incoming connection from: 162.216.150.4
2025-08-09 04:06:28.047 Status: [web:443] Incoming connection from: 207.180.255.216
2025-08-09 04:09:31.560 Status: [web:443] Incoming connection from: 185.242.226.109
2025-08-09 04:11:47.178 Status: [web:443] Incoming connection from: 66.249.79.238
2025-08-09 04:17:14.634 Status: [web:443] Incoming connection from: 91.148.248.68
2025-08-09 04:31:32.851 Status: [web:443] Incoming connection from: 167.71.164.160
2025-08-09 04:39:48.760 Status: [web:443] Incoming connection from: 20.65.193.168
2025-08-09 04:42:12.138 Status: [web:443] Incoming connection from: 172.236.228.38
2025-08-09 05:03:59.839 Status: [web:443] Incoming connection from: 196.251.114.43
2025-08-09 05:36:59.244 Status: [web:443] Incoming connection from: 138.246.253.24
2025-08-09 05:44:37.344 Status: [web:443] Incoming connection from: 34.140.38.148
2025-08-09 06:12:42.492 Status: [web:443] Incoming connection from: 3.131.215.38
2025-08-09 06:16:14.027 Status: [web:443] Incoming connection from: 178.20.47.92
2025-08-09 06:31:27.003 Status: [web:443] Incoming connection from: 68.183.231.190
2025-08-09 06:47:28.786 Status: [web:443] Incoming connection from: 64.62.156.192
2025-08-09 06:53:10.137 Status: [web:443] Incoming connection from: 149.50.96.114
2025-08-09 06:56:49.745 Status: [web:443] Incoming connection from: 64.62.156.196
2025-08-09 06:58:56.869 Status: [web:443] Incoming connection from: 64.62.156.198
2025-08-09 07:01:27.680 Status: [web:443] Incoming connection from: 64.62.156.192
2025-08-09 07:05:23.008 Status: [web:443] Incoming connection from: 64.62.156.193
2025-08-09 07:05:34.770 Status: [web:443] Incoming connection from: 64.62.156.200
2025-08-09 07:05:53.774 Status: [web:443] Incoming connection from: 64.62.156.197
2025-08-09 07:06:27.975 Status: [web:443] Incoming connection from: 64.62.156.195

[jvdz]

Afther update to the last version i get all this connection. What is it and how to stop ??

2025-08-09 00:12:33.997 Status: [web:443] Incoming connection from: 146.70.185.32
2025-08-09 00:43:41.972 Status: [web:443] Incoming connection from: 91.231.89.120

This is discussed many times and guess you have a port forwarded from the Internet directly to your Domoticz server... right?
These are bots trying to figure out what is connected to this public port, so I hope you have security properly setup in domoticz!
You really shouldn't open any direct access to a domotica Server from the Internet, but rather use a VPN.
When you really want/need this direct access, my preference is to "break the connection from the Internet" by using a reverse proxy like NGINX and then have Fail2Ban scan the logs for errors, at which time those source IP addresses trying to get in are banned for a period.

[gizmocuz]

Bad idea to open port 443 (or 80, 8080) for the internet.
If you can, make your router listen on a port like 5438, and forward this to your Domoticz ip/port

And indeed, what said above, best to use a VPN (Like Wireguard)