Http traffic logging from my Supla cloud ?

[PeterP]

I hope to solve my issue by checking http traffic to my mosquitto. Is there any chance to see the HTTP traffic in a Supla log?

I need to check why the Supla is not making attempts to establish the connection to my MQTT server.

I set up everything and can also activate on the Supla Website, but my mosquitto does not receive any request on it‘s listening ports.

Either the latest Supla docker image has got a problem or it‘s another thing within network.

All is within docker on the same machine.

To avoid http problems the containers are member of same docker network. Ports are open and set. User and PW also.

This is why I need to check the outbound http traffic from Supla….

So please let me know how to find out….

Any help on that problem is appreciated!

Best regards
Peter

[pzygmunt]

Let's start by checking the logs from the supla-server container. Communication with mosquitto is based on the mosquitto protocol, not HTTP.

[PeterP]

How to inspect the mentioned logs?

I mean: I've digged more deep checking of course the logs from mosquitto and also checked the docker networks to be sure both containers can see each other.

How to set up another protocol (I mean for MQTT it's set of course to mqtt) - but the traffic goes over TCP/IP and from the other 2 clients I do see in the mosquitto log the connects, even attempts if I try manually from browser to connect to mosquitto over http which of course throws an error log but from supla . no any connection attempt visible, so which log should I inspect ...?

from supla server this is the latest container log:

2026-05-23T16:33:17.353327970Z 2026-05-23 16:33:17,352 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.

2026-05-23T16:33:17.366685894Z 2026-05-23 16:33:17,366 INFO supervisord started with pid 1

2026-05-23T16:33:18.374560195Z 2026-05-23 16:33:18,373 INFO spawned: 'supla-scheduler' with pid 11

2026-05-23T16:33:18.384395812Z 2026-05-23 16:33:18,383 INFO spawned: 'supla-server' with pid 12

2026-05-23T16:33:18.409174499Z INFO[16:33:18.402240] Scheduler version 23.05

2026-05-23T16:33:18.409260054Z INFO[16:33:18.402383] Started at 2026-05-23 16:33:18

2026-05-23T16:33:18.418317884Z ERR[16:33:18.417764] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (115)

2026-05-23T16:33:18.418455641Z INFO[16:33:18.417799] Connecting to database ....

2026-05-23T16:33:18.426747611Z INFO[16:33:18.426064] Server version 26.05 [Protocol v28]

2026-05-23T16:33:18.426891831Z INFO[16:33:18.426194] Started at 2026-05-23 16:33:18

2026-05-23T16:33:18.430963187Z ERR[16:33:18.430543] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (115)

2026-05-23T16:33:18.431124056Z INFO[16:33:18.430573] Connecting to database ....

2026-05-23T16:33:19.420755758Z ERR[16:33:19.419131] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (115)

2026-05-23T16:33:19.420823442Z 2026-05-23 16:33:19,419 INFO success: supla-scheduler entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2026-05-23T16:33:19.421094772Z 2026-05-23 16:33:19,420 INFO success: supla-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2026-05-23T16:33:19.432435222Z ERR[16:33:19.432046] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (115)

2026-05-23T16:33:20.420851998Z ERR[16:33:20.420347] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (115)

2026-05-23T16:33:20.434100183Z ERR[16:33:20.433503] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (115)

2026-05-23T16:33:21.422368169Z ERR[16:33:21.421669] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (115)

2026-05-23T16:33:21.437284036Z ERR[16:33:21.435674] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (115)

2026-05-23T16:33:22.424062711Z ERR[16:33:22.423586] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (115)

2026-05-23T16:33:22.437393858Z ERR[16:33:22.436984] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (115)

2026-05-23T16:33:23.425053488Z ERR[16:33:23.424666] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (115)

2026-05-23T16:33:23.438512615Z ERR[16:33:23.438154] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (115)

2026-05-23T16:33:24.429643945Z ERR[16:33:24.428320] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (115)

2026-05-23T16:33:24.439580524Z ERR[16:33:24.439252] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (115)

2026-05-23T16:33:25.430036885Z ERR[16:33:25.429631] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (115)

2026-05-23T16:33:25.440688251Z ERR[16:33:25.440327] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (115)

2026-05-23T16:33:26.431261966Z ERR[16:33:26.430804] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (115)

2026-05-23T16:33:26.442023516Z ERR[16:33:26.441520] Failed to connect to database: Error: Can't connect to MySQL server on 'supla-db' (115)

2026-05-23T16:33:27.446942054Z INFO[16:33:27.445868] SSL version: OpenSSL 1.1.1w 11 Sep 2023

2026-05-23T16:33:27.534311584Z ERR[16:33:27.533938] An attempt to obtain remote gateway token from the AD server failed. Result code: 403

2026-05-23T16:33:33.695131073Z INFO[16:33:33.693802] Connection accepted: 192.168.1.115:38622 ClientSD: 13 Secure: 1

2026-05-23T16:33:33.708926215Z INFO[16:33:33.708077] Cipher: TLS_AES_256_GCM_SHA384, SSL Version: TLSv1.3, ClientSD: 13

2026-05-23T16:33:33.755666442Z INFO[16:33:33.754591] Device registration started. ClientSD: 13 Protocol Version: 23 ThreadID: 22 GUID: 60981CC5

2026-05-23T16:33:33.804008150Z INFO[16:33:33.803278] Device registered. ID: 2, ClientSD: 13 Protocol Version: 23 ThreadID: 22 GUID: 60981CC5 ResultCode: 3



I now restarted the supla_server container, the 'can't connect to ...' in that case did not happen, but from what I see there was no attempt to contact a mqtt broker ... (in case that is going to be logged in that log file)