Update schlägt wohl fehl ?!

[accessburn]

Hallo,
ich bekomme beim Update folgende Ausgabe im Monitor.

2016.12.19 08:30:25 2 : Backup with command: tar -cf - "/opt/fhem/log/fhem.save" "/opt/fhem//32_speedtest.pm" "/opt/fhem//backup" "/opt/fhem//buch.xml" "/opt/fhem//cache" "/opt/fhem//CHANGED" "/opt/fhem//configdb.pm" "/opt/fhem//contrib" "/opt/fhem//demolog" "/opt/fhem//docs" "/opt/fhem//FHEM" "/opt/fhem//fhem.cfg" "/opt/fhem//fhem.cfg.demo" "/opt/fhem//fhem.pl" "/opt/fhem//fhemlogkill.sh" "/opt/fhem//index.html" "/opt/fhem//IPCom" "/opt/fhem//ir2_off.sh" "/opt/fhem//ir2_on.sh" "/opt/fhem//ir_off.sh" "/opt/fhem//ir_on.sh" "/opt/fhem//log" "/opt/fhem//mp3readd.sh" "/opt/fhem//restoreDir" "/opt/fhem//script" "/opt/fhem//tueralarm_start.sh" "/opt/fhem//tueralarm_stop.sh" "/opt/fhem//unused" "/opt/fhem//WebStreams.txt" "/opt/fhem//www" |gzip > /media/usbstick/FHEM-20161219_083025.tar.gz
HTTP/1.0 502 badgateway Content-Type: text/html Cache-Control: no-cache Content-Length: 4812 Proxy-Connection: Close Bad Response         The proxy did not receive a valid response in time. This is usually due to slow site responsiveness, or malformed content being returned from the server.                       URL: break_line("http://dns.trcoding.net:8083/fhem?XHR=1&inform=type=raw;withLog=1;filter=global&timestamp=1482132625114");         

2016.12.19 08:32:49 1 : backup tar: Removing leading `/' from member names tar: /opt/fhem//log/LaCrosse_20-2016-12.log: file changed as we read it tar: Removing leading `/' from hard link targets
2016.12.19 08:32:49 1 : backup done: FHEM-20161219_083025.tar.gz (70655308 Bytes)
2016.12.19 08:32:49 1 :
2016.12.19 08:32:49 1 : fhem
2016.12.19 08:32:49 1 : RMDIR: /opt/fhem//restoreDir/2016-12-12
2016.12.19 08:32:49 1 : UPD ./CHANGED
2016.12.19 08:32:49 1 : UPD ./fhem.pl
2016.12.19 08:32:49 1 : UPD FHEM/01_FHEMWEB.pm
2016.12.19 08:32:49 1 : UPD FHEM/10_UNIRoll.pm
2016.12.19 08:32:50 1 : UPD FHEM/36_Level.pm
2016.12.19 08:32:50 1 : UPD FHEM/39_alexa.pm
2016.12.19 08:32:50 1 : UPD FHEM/50_HP1000.pm
2016.12.19 08:32:50 1 : UPD FHEM/57_Calendar.pm
2016.12.19 08:32:50 1 : UPD FHEM/59_Wunderground.pm
2016.12.19 08:32:50 1 : UPD FHEM/66_ECMD.pm
2016.12.19 08:32:50 1 : UPD FHEM/67_ECMDDevice.pm
2016.12.19 08:32:50 1 : UPD FHEM/70_ENIGMA2.pm
2016.12.19 08:32:50 1 : UPD FHEM/72_FB_CALLMONITOR.pm
2016.12.19 08:32:54 1 : UPD FHEM/73_NUKIBridge.pm
2016.12.19 08:32:54 1 : UPD FHEM/74_NUKIDevice.pm
2016.12.19 08:32:54 1 : UPD FHEM/93_DbRep.pm
2016.12.19 08:32:54 1 : UPD FHEM/98_HMinfo.pm
2016.12.19 08:32:54 1 : UPD FHEM/98_HMtemplate.pm
2016.12.19 08:32:54 1 : UPD FHEM/98_apptime.pm
2016.12.19 08:32:54 1 : UPD FHEM/98_update.pm
2016.12.19 08:32:54 1 : UPD FHEM/HMConfig.pm
2016.12.19 08:32:54 1 : UPD FHEM/Unit.pm
2016.12.19 08:32:54 1 : saving fhem.cfg
2016.12.19 08:32:54 1 :
2016.12.19 08:32:54 1 : New entries in the CHANGED file:
2016.12.19 08:32:54 1 : - update: 73_NUKIBridge,74_NUKIDevice: New Version 0.4.0
2016.12.19 08:32:54 1 : More Feature get,set ,Callback/Webhook Funktion
2016.12.19 08:32:54 1 : - change: 98_exportdevice: command was deprecated and moved to contrib in
2016.12.19 08:32:54 1 : favor of FHEMWEB builtin functions
2016.12.19 08:32:54 1 : - bugfix: 93_DbRep: bugfix group by-clause due to incompatible changes made
2016.12.19 08:32:54 1 : in MyQL 5.7.5 (Forum #msg541103)
2016.12.19 08:32:54 1 : - feature: 66_ECMD, 67_ECMDDevice:
2016.12.19 08:32:54 1 : - if split is used, the strings at which the messages are split
2016.12.19 08:32:54 1 : are still part of the messages
2016.12.19 08:32:54 1 : - no default attributes for requestSeparator and responseSeparator
2016.12.19 08:32:54 1 : - input of raw data as perl-encoded string (for setting
mlog'>2016.12.19 08:32:54 1 :                 attributes)2016.12.19 08:32:54 1 :               - be more verbose and explicit at loglevel 52016.12.19 08:32:54 1 :               - documentation corrected and amended2016.12.19 08:32:54 1 :   - feature: 57_Calendar: BYDAY: recognizes and honors one or several weekdays 2016.12.19 08:32:54 1 :                           with and without prefix (e.g. -1SU, 2MO) with MONTHLY2016.12.19 08:32:54 1 : 2016.12.19 08:32:54 1 : 2016.12.19 08:32:54 1 : fhemtabletui2016.12.19 08:32:55 1 : nothing to do...2016.12.19 08:32:55 1 : 2016.12.19 08:32:55 1 : 2016.12.19 08:32:55 1 : fhemabfall<div class='fhemlog'>2016.12.19 08:32:55HTTP/1.0 502 badgateway Content-Type: text/html Cache-Control: no-cache Content-Length: 4833 Proxy-Connection: Close Bad Response        HTTP/1.0 502 badgateway Content-Type: text/html Cache-Control: no-cache Content-Length: 4812 Proxy-Connection: Close Bad Response         The proxy did not receive a valid response in time. This is usually due to slow site responsiveness, or malformed content being returned from the server.                       URL: break_line("http://dns.trcoding.net:8083/fhem?XHR=1&inform=type=raw;withLog=1;filter=global&timestamp=1482132983232");         

HTTP/1.0 502 badgateway Content-Type: text/html Cache-Control: no-cache Content-Length: 4812 Proxy-Connection: Close Bad Response        HTTP/1.0 502 badgateway Content-Type: text/html Cache-Control: no-cache Content-Length: 4812 Proxy-Connection: Close Bad Response         The proxy did not receive a valid response in time. This is usually due to slow site responsiveness, or malformed content being returned from the server.                       URL: break_line("http://dns.trcoding.net:8083/fhem?XHR=1&inform=type=raw;withLog=1;filter=global&timestamp=1482133238429");         

Kann mir jemand sagen was ich da tun muss?

[rudolfkoenig]

Proxy abschalten?
Evtl. hilft es auf https umzustellen in FHEM/controls.txt

[accessburn]

Proxy kann schon sein. Ich fahre über einen Firmen-PC der wohl einen Proxy nutzt. Aber ist das von mir von außen abhängig obwohl der Raspi auf dem FHEM läuft normal am Internet hängt und ich ihn nur von außen via Proxy aufrufe?

[rudolfkoenig]

Ich gehe davon aus, dass nicht update ein Problem hat (und damit mein Vorschlag http -> https sinnlos ist), sondern "nur" die Anzeige der update-Meldungen im "Firmenbrowser" kaputt ist, da der Proxy sein Muell ins Datenstrom packt. Ich tu mich aber schwer das Problem ohne Proxy zu debuggen.

[accessburn]

Gut erklärt. Danke ... Ich werde mal morgen ein Update (wenn vorhanden) zuhause fahren unter selben Bedingungen, mal sehen was passiert.