zigbee2mqtt icon indicating copy to clipboard operation
zigbee2mqtt copied to clipboard

Zigbee2mqtt docker ota function not using proxy setting?

Open jasmir opened this issue 9 months ago • 2 comments

What happened?

Starting the container:

docker run -d --name zigbee2mqtt --privileged --restart=unless-stopped -e TZ=Europe/Berlin \
-e HTTP_PROXY='http://myproxy.local:8000' -e HTTPS_PROXY='http://myproxy.local:8000' \
-e http_proxy='http://myproxy.local:8000' -e https_proxy='http://myproxy.local:8000' \
-p 8080:8080 -v '/data/zigbee2mqtt:/app/data' --network=host koenkk/zigbee2mqtt:latest

Going to the Webinterface -> OTA -> on a Device there "check for updates" Got: error 2025-03-21 08:58:43z2m: Failed to check if update available for 'Rauchmelder_Wohnzimmer' (fetch failed)

TCP-Dump on the Host shows, that there are outgoing packets to 185.199.108.133(github) directly at this exactly time, instead of using the proxy

What did you expect to happen?

I expect that the OTA function will use the proxy from that variables. -or- That there will be config items in the configuration.yaml for that purpose. But I didn't find any of these in the docs.

How to reproduce it (minimal and precise)

See docker-run, above

Zigbee2MQTT version

2.1.3 commit: ba337bd329aeb4ca17735c0cf09b31293c8cff06

Adapter firmware version

7.4.5 [GA]

Adapter

SLZB-06M

Setup

As docker container koenkk/zigbee2mqtt:latest

Debug log

No response

jasmir avatar Mar 21 '25 10:03 jasmir

Retested with 2.2.0 -> same problem

jasmir avatar Apr 02 '25 22:04 jasmir

Retested with 2.3.0 commit: aec59cb774aa09a793ae41cd60e6a5cef15b293c, same problem. Is there a way to work around this? Or do I use the variables wrong?

jasmir avatar May 01 '25 19:05 jasmir

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

github-actions[bot] avatar Jul 01 '25 00:07 github-actions[bot]

retested for 2.4.0 -> still the same issue

jasmir avatar Jul 01 '25 07:07 jasmir

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

github-actions[bot] avatar Aug 31 '25 00:08 github-actions[bot]

Same Problem with 2.6.0 (commit: 0bdc3fd1f76aaad71f6231e5b38529e2d2b345e9) Is there any way to fix this by myself? Working OTA-Updates would be very neat...

jasmir avatar Aug 31 '25 09:08 jasmir

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

github-actions[bot] avatar Nov 01 '25 00:11 github-actions[bot]

Tested with 2.6.3, commit: 6e001b48ec278c6c141579c9eacc045f190fc289 -> same problem

jasmir avatar Nov 02 '25 16:11 jasmir

+1

duiffie avatar Dec 09 '25 13:12 duiffie