Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. „Cannot update rating: certificate has expired“ admin.0

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    „Cannot update rating: certificate has expired“ admin.0

    This topic has been deleted. Only users with topic management privileges can see it.
    • Thomas Braun
      Thomas Braun Most Active @Stormbringer last edited by

      Da stimmt was mit dem Routing nicht, würde ich sagen.

      echad@chet:~ $ ping 53.17.152.58
PING 53.17.152.58 (53.17.152.58) 56(84) bytes of data.

--- 53.17.152.58 ping statistics ---
13 packets transmitted, 0 received, 100% packet loss, time 12269ms

echad@chet:~ $ traceroute 53.17.152.58
traceroute to 53.17.152.58 (53.17.152.58), 30 hops max, 60 byte packets
 1  fritz.box (192.168.178.1)  1.218 ms  1.140 ms  9.438 ms
 2  * * *
 3  de-dus23e-rc1-ae23.dus.unity-media.net (81.210.141.25)  28.275 ms  29.957 ms  29.874 ms
 4  de-fra01b-rc2-ae-21-0.aorta.net (84.116.138.202)  32.040 ms  33.290 ms  33.234 ms
 5  de-bfe18a-rt01-lag-1.aorta.net (84.116.190.34)  31.771 ms  31.733 ms  31.617 ms
 6  ae32-100-pcr1.fnt.cw.net (195.2.18.217)  24.261 ms ae8-100-tcr1.fnt.cw.net (195.2.26.93)  24.660 ms  26.200 ms
 7  telia-gw.fnt.cw.net (195.2.22.238)  28.908 ms  18.342 ms ae34-pcr1.fnt.cw.net (195.2.31.38)  20.242 ms
 8  ffm-bb1-link.ip.twelve99.net (62.115.124.116)  28.383 ms telia-gw.fnt.cw.net (195.2.22.238)  28.267 ms  24.401 ms
 9  ffm-b10-link.ip.twelve99.net (62.115.137.211)  21.119 ms ffm-bb1-link.ip.twelve99.net (62.115.124.116)  25.984 ms ffm-b1-link.ip.twelve99.net (62.115.121.1)  29.601 ms
10  kddi-ic319844-ffm-b1.ip.twelve99-cust.net (62.115.32.106)  28.393 ms ffm-b1-link.ip.twelve99.net (62.115.121.1)  31.634 ms kddi-ic301630-ffm-b10.ip.twelve99-cust.net (62.115.32.110)  28.311 ms
11  195.82.60.158 (195.82.60.158)  25.131 ms  22.316 ms kddi-ic301630-ffm-b10.ip.twelve99-cust.net (62.115.32.110)  23.491 ms
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
echad@chet:~ $

      Die IP kommt aus einem IP-Pool von Daimler-Benz?

      echad@chet:~ $ whois 53.17.152.58

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2023, American Registry for Internet Numbers, Ltd.
#


NetRange:       53.0.0.0 - 53.255.255.255
CIDR:           53.0.0.0/8
NetName:        RIPE-ERX-53
NetHandle:      NET-53-0-0-0-1
Parent:          ()
NetType:        Early Registrations, Maintained by RIPE NCC
OriginAS:
Organization:   RIPE Network Coordination Centre (RIPE)
RegDate:        1992-03-17
Updated:        2014-10-14
Comment:        These addresses have been further assigned to users in the RIPE NCC region. Contact information can be found in the RIPE database at http://www.ripe.net/whois
Ref:            https://rdap.arin.net/registry/ip/53.0.0.0

ResourceLink:  https://apps.db.ripe.net/search/query.html
ResourceLink:  whois.ripe.net


OrgName:        RIPE Network Coordination Centre
OrgId:          RIPE
Address:        P.O. Box 10096
City:           Amsterdam
StateProv:
PostalCode:     1001EB
Country:        NL
RegDate:
Updated:        2013-07-29
Ref:            https://rdap.arin.net/registry/entity/RIPE

ReferralServer:  whois://whois.ripe.net
ResourceLink:  https://apps.db.ripe.net/search/query.html

OrgTechHandle: RNO29-ARIN
OrgTechName:   RIPE NCC Operations
OrgTechPhone:  +31 20 535 4444
OrgTechEmail:  hostmaster@ripe.net
OrgTechRef:    https://rdap.arin.net/registry/entity/RNO29-ARIN

OrgAbuseHandle: ABUSE3850-ARIN
OrgAbuseName:   Abuse Contact
OrgAbusePhone:  +31205354444
OrgAbuseEmail:  abuse@ripe.net
OrgAbuseRef:    https://rdap.arin.net/registry/entity/ABUSE3850-ARIN


#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2023, American Registry for Internet Numbers, Ltd.
#



Found a referral to whois.ripe.net.

% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See http://www.ripe.net/db/support/db-terms-conditions.pdf

% Note: this output has been filtered.
%       To receive output for a database update, use the "-B" flag.

% Information related to '53.0.0.0 - 53.255.255.255'

% Abuse contact for '53.0.0.0 - 53.255.255.255' is 'ipadmin@daimler.com'

inetnum:        53.0.0.0 - 53.255.255.255
netname:        MERCEDES-BENZ-NET1
org:            ORG-DA474-RIPE
descr:          Mercedes-Benz Group AG
country:        DE
admin-c:        EH4384-RIPE
tech-c:         EH4384-RIPE
status:         LEGACY
mnt-by:         RIPE-NCC-LEGACY-MNT
mnt-by:         DAIMLER-MNT
created:        1970-01-01T00:00:00Z
last-modified:  2022-04-12T08:04:16Z
source:         RIPE

organisation:   ORG-DA474-RIPE
org-name:       Mercedes-Benz Group AG
country:        DE
org-type:       LIR
address:        ITT/TN HPC L525
address:        70546
address:        Stuttgart
address:        GERMANY
phone:          +497111760844
fax-no:         +497111779060844
abuse-c:        AR13603-RIPE
mnt-ref:        RIPE-NCC-HM-MNT
mnt-ref:        DAIMLER-MNT
mnt-by:         RIPE-NCC-HM-MNT
mnt-by:         DAIMLER-MNT
admin-c:        EH4384-RIPE
admin-c:        EH4384-RIPE
created:        2012-12-11T14:21:36Z
last-modified:  2022-02-02T07:09:15Z
source:         RIPE # Filtered

person:         Edda Hoppe
address:        Daimler AG
address:        HPC L525
address:        D-70546 Stuttgart
address:        Germany
phone:          +49 711 17 56394
fax-no:         +49 711 17 79087921
nic-hdl:        EH4384-RIPE
created:        2022-01-13T13:28:17Z
last-modified:  2022-01-13T13:37:14Z
source:         RIPE # Filtered
mnt-by:         DAIMLER-MNT

% Information related to '53.0.0.0/8AS31399'

route:          53.0.0.0/8
descr:          MERCEDES-BENZ-NET1
origin:         AS31399
mnt-by:         DAIMLER-MNT
created:        2006-03-14T10:05:37Z
last-modified:  2022-04-12T08:05:43Z
source:         RIPE

% This query was served by the RIPE Database Query Service version 1.105 (ABERDEEN)
      S 1 Reply Last reply Reply Quote 0
      • S
        Stormbringer @Thomas Braun last edited by

        @thomas-braun Danke für die schnelle Antwort, ich hab die IPs vorsichtshalber geändert bevor ich sie poste, war wohl falsch 🤦

        Thomas Braun 1 Reply Last reply Reply Quote 0
        • Thomas Braun
          Thomas Braun Most Active @Stormbringer last edited by Thomas Braun

          @stormbringer

          Das ist ja sehr sinnvoll.... -_-

          IP-Adressen nie ändern, auch nicht IPs aus deinem internen Netzwerk.

          S 1 Reply Last reply Reply Quote 0
          • S
            Stormbringer @Thomas Braun last edited by

            @thomas-braun loool sorry dachte IPs posten ist ned grad sicher aber wenn ich deine Befehle nachmache kommt:

            traceroute: unknown host

            Thomas Braun 1 Reply Last reply Reply Quote 0
            • Thomas Braun
              Thomas Braun Most Active @Stormbringer last edited by

              @stormbringer sagte in „Cannot update rating: certificate has expired“ admin.0:

              IPs posten ist ned grad sicher

              IPs sind logischerweise öffentlich. So funktioniert halt das Internet. Ohne korrkete IP kannst du den Host ja nicht erreichen.

              S 1 Reply Last reply Reply Quote 0
              • S
                Stormbringer @Thomas Braun last edited by Stormbringer

                @thomas-braun
                so lang es nicht die eigene ist oder? ok, dann mal ungeschwärzt 😉 sorry

                ado.0
   2023-01-28 18:13:59.912	error	Disconnected from Tado cloud service ..., retry in 30 seconds !
tado.0
   2023-01-28 18:13:59.911	error	Error in data refresh at step DoZones: Error: connect ETIMEDOUT 52.17.162.58:443
tado.0
   2023-01-28 18:13:59.911	error	Error: connect ETIMEDOUT 52.17.162.58:443
bring.0
   2023-01-28 18:11:54.930	warn	Error: Cannot get items for list 464cbd1a-6e16-4c83-abf3-35fb0a7f8874: Error: connect ETIMEDOUT 52.55.251.61:443
host.io-frost-prox
   2023-01-28 18:11:16.647	error	instance system.adapter.tado.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
host.io-frost-prox
   2023-01-28 18:11:16.647	error	Caught by controller[2]: at TLSSocket.emit (node:domain:489:12)
host.io-frost-prox
   2023-01-28 18:11:16.647	error	Caught by controller[2]: at TLSSocket.emit (node:events:513:28)
host.io-frost-prox
   2023-01-28 18:11:16.647	error	Caught by controller[2]: at TLSSocket.socketErrorListener (node:_http_client:494:9)
host.io-frost-prox
   2023-01-28 18:11:16.647	error	Caught by controller[2]: at ClientRequest.emit (node:domain:489:12)
host.io-frost-prox
   2023-01-28 18:11:16.647	error	Caught by controller[2]: at ClientRequest.emit (node:events:525:35)
host.io-frost-prox
   2023-01-28 18:11:16.647	error	Caught by controller[2]: at ClientRequest.eventHandlers.<computed> (/opt/iobroker/node_modules/follow-redirects/index.js:14:24)
host.io-frost-prox
   2023-01-28 18:11:16.646	error	Caught by controller[2]: at RedirectableRequest.emit (node:domain:489:12)
host.io-frost-prox
   2023-01-28 18:11:16.646	error	Caught by controller[2]: at RedirectableRequest.emit (node:events:513:28)
host.io-frost-prox
   2023-01-28 18:11:16.646	error	Caught by controller[2]: at RedirectableRequest.handleRequestError (/opt/iobroker/node_modules/iobroker.tado/node_modules/axios/lib/adapters/http.js:526:25)
host.io-frost-prox
   2023-01-28 18:11:16.646	error	Caught by controller[2]: at Function.AxiosError.from (/opt/iobroker/node_modules/iobroker.tado/node_modules/axios/lib/core/AxiosError.js:89:14)
host.io-frost-prox
   2023-01-28 18:11:16.646	error	Caught by controller[2]: Error: connect ETIMEDOUT 52.17.162.58:443
host.io-frost-prox
   2023-01-28 18:11:16.646	error	Caught by controller[2]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
host.io-frost-prox
   2023-01-28 18:11:16.646	error	Caught by controller[1]: }
host.io-frost-prox
   2023-01-28 18:11:16.646	error	Caught by controller[1]: }
host.io-frost-prox
   2023-01-28 18:11:16.646	error	Caught by controller[1]: port: 443
host.io-frost-prox
   2023-01-28 18:11:16.646	error	Caught by controller[1]: address: '52.17.162.58',
host.io-frost-prox
   2023-01-28 18:11:16.646	error	Caught by controller[1]: syscall: 'connect',
host.io-frost-prox
   2023-01-28 18:11:16.646	error	Caught by controller[1]: code: 'ETIMEDOUT',
host.io-frost-prox
   2023-01-28 18:11:16.646	error	Caught by controller[1]: errno: -110,
host.io-frost-prox
   2023-01-28 18:11:16.646	error	Caught by controller[1]: at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16) {
host.io-frost-prox
   2023-01-28 18:11:16.646	error	Caught by controller[1]: cause: Error: connect ETIMEDOUT 52.17.162.58:443
host.io-frost-prox
   2023-01-28 18:11:16.646	error	Caught by controller[1]: },
host.io-frost-prox
   2023-01-28 18:11:16.646	error	Caught by controller[1]: [Symbol(kCapture)]: false
host.io-frost-prox
   2023-01-28 18:11:16.646	error	Caught by controller[1]: _currentUrl: 'https://my.tado.com/api/v2/devices/SU3965463552/temperatureOffset',
host.io-frost-prox
   2023-01-28 18:11:16.646	error	Caught by controller[1]: },
host.io-frost-prox
   2023-01-28 18:11:16.646	error	Caught by controller[1]: [Symbol(kUniqueHeaders)]: null
host.io-frost-prox
   2023-01-28 18:11:16.646	error	Caught by controller[1]: [Symbol(kOutHeaders)]: [Object: null prototype],
host.io-frost-prox
   2023-01-28 18:11:16.646	error	Caught by controller[1]: [Symbol(corked)]: 0,
host.io-frost-prox
   2023-01-28 18:11:16.646	error	Caught by controller[1]: [Symbol(kNeedDrain)]: false,
host.io-frost-prox
   2023-01-28 18:11:16.646	error	Caught by controller[1]: [Symbol(kEndCalled)]: false,
host.io-frost-prox
   2023-01-28 18:11:16.646	error	Caught by controller[1]: [Symbol(kBytesWritten)]: 0,
host.io-frost-prox
   2023-01-28 18:11:16.646	error	Caught by controller[1]: [Symbol(kCapture)]: false,
host.io-frost-prox
   2023-01-28 18:11:16.645	error	Caught by controller[1]: _redirectable: [Circular *1],
host.io-frost-prox
   2023-01-28 18:11:16.645	error	Caught by controller[1]: protocol: 'https:',
host.io-frost-prox
   2023-01-28 18:11:16.645	error	Caught by controller[1]: host: 'my.tado.com',
host.io-frost-prox
   2023-01-28 18:11:16.645	error	Caught by controller[1]: reusedSocket: false,
host.io-frost-prox
   2023-01-28 18:11:16.645	error	Caught by controller[1]: maxHeadersCount: null,
host.io-frost-prox
   2023-01-28 18:11:16.645	error	Caught by controller[1]: parser: null,
host.io-frost-prox
   2023-01-28 18:11:16.645	error	Caught by controller[1]: upgradeOrConnect: false,
host.io-frost-prox
   2023-01-28 18:11:16.645	error	Caught by controller[1]: timeoutCb: null,
host.io-frost-prox
   2023-01-28 18:11:16.645	error	Caught by controller[1]: aborted: false,
host.io-frost-prox
   2023-01-28 18:11:16.645	error	Caught by controller[1]: res: null,
host.io-frost-prox
   2023-01-28 18:11:16.645	error	Caught by controller[1]: _ended: false,
host.io-frost-prox
   2023-01-28 18:11:16.645	error	Caught by controller[1]: path: '/api/v2/devices/SU3965463552/temperatureOffset',
host.io-frost-prox
   2023-01-28 18:11:16.645	error	Caught by controller[1]: insecureHTTPParser: undefined,
host.io-frost-prox
   2023-01-28 18:11:16.645	error	Caught by controller[1]: maxHeaderSize: undefined,
host.io-frost-prox
   2023-01-28 18:11:16.645	error	Caught by controller[1]: method: 'GET',
host.io-frost-prox
   2023-01-28 18:11:16.645	error	Caught by controller[1]: socketPath: undefined,
host.io-frost-prox
   2023-01-28 18:11:16.645	error	Caught by controller[1]: agent: [Agent],
host.io-frost-prox
   2023-01-28 18:11:16.645	error	Caught by controller[1]: _onPendingData: [Function: nop],
host.io-frost-prox
   2023-01-28 18:11:16.645	error	Caught by controller[1]: _keepAliveTimeout: 0,
host.io-frost-prox
   2023-01-28 18:11:16.645	error	Caught by controller[1]: '\r\n',
host.io-frost-prox
   2023-01-28 18:11:16.645	error	Caught by controller[1]: 'Connection: close\r\n' +
host.io-frost-prox
   2023-01-28 18:11:16.645	error	Caught by controller[1]: 'Host: my.tado.com\r\n' +
host.io-frost-prox
   2023-01-28 18:11:16.645	error	Caught by controller[1]: 'Accept-Encoding: gzip, compress, deflate, br\r\n' +
host.io-frost-prox
   2023-01-28 18:11:16.645	error	Caught by controller[1]: 'Content-Length: 2\r\n' +
host.io-frost-prox
   2023-01-28 18:11:16.645	error	Caught by controller[1]: 'User-Agent: axios/1.2.1\r\n' +
host.io-frost-prox
   2023-01-28 18:11:16.645	error	Caught by controller[1]: 'Content-Type: application/json\r\n' +
host.io-frost-prox
   2023-01-28 18:11:16.645	error	Caught by controller[1]: 'Authorization: Bearer g\r\n' +
host.io-frost-prox
   2023-01-28 18:11:16.645	error	Caught by controller[1]: 'Accept: application/json, text/plain, */*\r\n' +
host.io-frost-prox
   2023-01-28 18:11:16.645	error	Caught by controller[1]: _header: 'GET /api/v2/devices/SU3965463552/temperatureOffset HTTP/1.1\r\n' +
host.io-frost-prox
   2023-01-28 18:11:16.644	error	Caught by controller[1]: socket: [TLSSocket],
host.io-frost-prox
   2023-01-28 18:11:16.644	error	Caught by controller[1]: _closed: false,
host.io-frost-prox
   2023-01-28 18:11:16.644	error	Caught by controller[1]: _headerSent: true,
host.io-frost-prox
   2023-01-28 18:11:16.644	error	Caught by controller[1]: finished: false,
host.io-frost-prox
   2023-01-28 18:11:16.644	error	Caught by controller[1]: _trailer: '',
host.io-frost-prox
   2023-01-28 18:11:16.644	error	Caught by controller[1]: _hasBody: true,
host.io-frost-prox
   2023-01-28 18:11:16.644	error	Caught by controller[1]: _contentLength: '2',
host.io-frost-prox
   2023-01-28 18:11:16.644	error	Caught by controller[1]: strictContentLength: false,
host.io-frost-prox
   2023-01-28 18:11:16.644	error	Caught by controller[1]: _removedTE: false,
host.io-frost-prox
   2023-01-28 18:11:16.644	error	Caught by controller[1]: _removedContLen: false,
host.io-frost-prox
   2023-01-28 18:11:16.644	error	Caught by controller[1]: _removedConnection: false,
host.io-frost-prox
   2023-01-28 18:11:16.644	error	Caught by controller[1]: sendDate: false,
host.io-frost-prox
   2023-01-28 18:11:16.644	error	Caught by controller[1]: useChunkedEncodingByDefault: false,
host.io-frost-prox
   2023-01-28 18:11:16.644	error	Caught by controller[1]: _defaultKeepAlive: true,
host.io-frost-prox
   2023-01-28 18:11:16.644	error	Caught by controller[1]: maxRequestsOnConnectionReached: false,
host.io-frost-prox
   2023-01-28 18:11:16.644	error	Caught by controller[1]: shouldKeepAlive: false,
host.io-frost-prox
   2023-01-28 18:11:16.644	error	Caught by controller[1]: chunkedEncoding: false,
host.io-frost-prox
   2023-01-28 18:11:16.644	error	Caught by controller[1]: _last: true,
host.io-frost-prox
   2023-01-28 18:11:16.644	error	Caught by controller[1]: destroyed: false,
host.io-frost-prox
   2023-01-28 18:11:16.644	error	Caught by controller[1]: writable: true,
host.io-frost-prox
   2023-01-28 18:11:16.644	error	Caught by controller[1]: outputSize: 0,
host.io-frost-prox
   2023-01-28 18:11:16.644	error	Caught by controller[1]: outputData: [],
host.io-frost-prox
   2023-01-28 18:11:16.644	error	Caught by controller[1]: _maxListeners: 100,
host.io-frost-prox
   2023-01-28 18:11:16.643	error	Caught by controller[1]: _eventsCount: 7,
host.io-frost-prox
   2023-01-28 18:11:16.643	error	Caught by controller[1]: _events: [Object: null prototype],
host.io-frost-prox
   2023-01-28 18:11:16.643	error	Caught by controller[1]: _currentRequest: ClientRequest {
host.io-frost-prox
   2023-01-28 18:11:16.643	error	Caught by controller[1]: _onNativeResponse: [Function (anonymous)],
host.io-frost-prox
   2023-01-28 18:11:16.643	error	Caught by controller[1]: _requestBodyBuffers: [ [Object] ],
host.io-frost-prox
   2023-01-28 18:11:16.643	error	Caught by controller[1]: _requestBodyLength: 2,
host.io-frost-prox
   2023-01-28 18:11:16.643	error	Caught by controller[1]: _redirects: [],
host.io-frost-prox
   2023-01-28 18:11:16.643	error	Caught by controller[1]: _redirectCount: 0,
host.io-frost-prox
   2023-01-28 18:11:16.643	error	Caught by controller[1]: _ending: true,
host.io-frost-prox
   2023-01-28 18:11:16.643	error	Caught by controller[1]: _ended: false,
host.io-frost-prox
   2023-01-28 18:11:16.643	error	Caught by controller[1]: },
host.io-frost-prox
   2023-01-28 18:11:16.643	error	Caught by controller[1]: pathname: '/api/v2/devices/SU3965463552/temperatureOffset'
host.io-frost-prox
   2023-01-28 18:11:16.643	error	Caught by controller[1]: nativeProtocols: [Object],
host.io-frost-prox
   2023-01-28 18:11:16.643	error	Caught by controller[1]: agent: undefined,
host.io-frost-prox
   2023-01-28 18:11:16.643	error	Caught by controller[1]: port: '',
host.io-frost-prox
   2023-01-28 18:11:16.643	error	Caught by controller[1]: hostname: 'my.tado.com',
host.io-frost-prox
   2023-01-28 18:11:16.643	error	Caught by controller[1]: beforeRedirects: [Object],
host.io-frost-prox
   2023-01-28 18:11:16.643	error	Caught by controller[1]: beforeRedirect: [Function: dispatchBeforeRedirect],
host.io-frost-prox
   2023-01-28 18:11:16.643	error	Caught by controller[1]: auth: undefined,
host.io-frost-prox
   2023-01-28 18:11:16.643	error	Caught by controller[1]: agents: [Object],
host.io-frost-prox
   2023-01-28 18:11:16.643	error	Caught by controller[1]: headers: [Object: null prototype],
host.io-frost-prox
   2023-01-28 18:11:16.642	error	Caught by controller[1]: method: 'GET',
host.io-frost-prox
   2023-01-28 18:11:16.642	error	Caught by controller[1]: path: '/api/v2/devices/SU3965463552/temperatureOffset',
host.io-frost-prox
   2023-01-28 18:11:16.642	error	Caught by controller[1]: protocol: 'https:',
host.io-frost-prox
   2023-01-28 18:11:16.642	error	Caught by controller[1]: maxBodyLength: Infinity,
host.io-frost-prox
   2023-01-28 18:11:16.642	error	Caught by controller[1]: maxRedirects: 21,
host.io-frost-prox
   2023-01-28 18:11:16.642	error	Caught by controller[1]: _options: {
host.io-frost-prox
   2023-01-28 18:11:16.642	error	Caught by controller[1]: _maxListeners: 100,
host.io-frost-prox
   2023-01-28 18:11:16.642	error	Caught by controller[1]: _eventsCount: 3,
host.io-frost-prox
   2023-01-28 18:11:16.642	error	Caught by controller[1]: },
host.io-frost-prox
   2023-01-28 18:11:16.642	error	Caught by controller[1]: socket: [Function: handleRequestSocket]
host.io-frost-prox
   2023-01-28 18:11:16.642	error	Caught by controller[1]: error: [Function: handleRequestError],
host.io-frost-prox
   2023-01-28 18:11:16.642	error	Caught by controller[1]: response: [Function: handleResponse],
host.io-frost-prox
   2023-01-28 18:11:16.642	error	Caught by controller[1]: _events: [Object: null prototype] {
host.io-frost-prox
   2023-01-28 18:11:16.642	error	Caught by controller[1]: },
host.io-frost-prox
   2023-01-28 18:11:16.642	error	Caught by controller[1]: [Symbol(kOnFinished)]: []
host.io-frost-prox
   2023-01-28 18:11:16.642	error	Caught by controller[1]: closeEmitted: false,
host.io-frost-prox
   2023-01-28 18:11:16.642	error	Caught by controller[1]: closed: false,
host.io-frost-prox
   2023-01-28 18:11:16.642	error	Caught by controller[1]: errored: null,
host.io-frost-prox
   2023-01-28 18:11:16.642	error	Caught by controller[1]: autoDestroy: true,
host.io-frost-prox
   2023-01-28 18:11:16.642	error	Caught by controller[1]: emitClose: true,
host.io-frost-prox
   2023-01-28 18:11:16.642	error	Caught by controller[1]: errorEmitted: false,
host.io-frost-prox
   2023-01-28 18:11:16.642	error	Caught by controller[1]: prefinished: false,
host.io-frost-prox
   2023-01-28 18:11:16.642	error	Caught by controller[1]: constructed: true,
host.io-frost-prox
   2023-01-28 18:11:16.642	error	Caught by controller[1]: pendingcb: 0,
host.io-frost-prox
   2023-01-28 18:11:16.642	error	Caught by controller[1]: allNoop: true,
host.io-frost-prox
   2023-01-28 18:11:16.642	error	Caught by controller[1]: allBuffers: true,
host.io-frost-prox
   2023-01-28 18:11:16.642	error	Caught by controller[1]: bufferedIndex: 0,
host.io-frost-prox
   2023-01-28 18:11:16.642	error	Caught by controller[1]: buffered: [],
host.io-frost-prox
   2023-01-28 18:11:16.642	error	Caught by controller[1]: afterWriteTickInfo: null,
host.io-frost-prox
   2023-01-28 18:11:16.642	error	Caught by controller[1]: writelen: 0,
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: writecb: null,
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: onwrite: [Function: bound onwrite],
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: bufferProcessing: false,
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: sync: true,
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: corked: 0,
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: writing: false,
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: length: 0,
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: defaultEncoding: 'utf8',
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: decodeStrings: true,
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: destroyed: false,
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: finished: false,
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: ended: false,
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: ending: false,
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: needDrain: false,
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: finalCalled: false,
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: highWaterMark: 16384,
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: objectMode: false,
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: _writableState: WritableState {
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: request: <ref *1> Writable {
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: },
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: data: '{}'
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: method: 'get',
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: url: 'https://my.tado.com/api/v2/devices/SU3965463552/temperatureOffset',
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: },
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: 'Accept-Encoding': 'gzip, compress, deflate, br'
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: 'Content-Length': '2',
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: 'User-Agent': 'axios/1.2.1',
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: 'Content-Type': 'application/json',
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: Authorization: 'Bearer g',
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: Accept: 'application/json, text/plain, */*',
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: headers: AxiosHeaders {
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: validateStatus: [Function: validateStatus],
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: env: { FormData: [Function], Blob: null },
host.io-frost-prox
   2023-01-28 18:11:16.641	error	Caught by controller[1]: maxBodyLength: -1,
host.io-frost-prox
   2023-01-28 18:11:16.640	error	Caught by controller[1]: maxContentLength: -1,
host.io-frost-prox
   2023-01-28 18:11:16.640	error	Caught by controller[1]: xsrfHeaderName: 'X-XSRF-TOKEN',
host.io-frost-prox
   2023-01-28 18:11:16.640	error	Caught by controller[1]: xsrfCookieName: 'XSRF-TOKEN',
host.io-frost-prox
   2023-01-28 18:11:16.640	error	Caught by controller[1]: timeout: 0,
host.io-frost-prox
   2023-01-28 18:11:16.640	error	Caught by controller[1]: transformResponse: [ [Function: transformResponse] ],
host.io-frost-prox
   2023-01-28 18:11:16.640	error	Caught by controller[1]: transformRequest: [ [Function: transformRequest] ],
host.io-frost-prox
   2023-01-28 18:11:16.640	error	Caught by controller[1]: adapter: [ 'xhr', 'http' ],
host.io-frost-prox
   2023-01-28 18:11:16.640	error	Caught by controller[1]: },
host.io-frost-prox
   2023-01-28 18:11:16.640	error	Caught by controller[1]: clarifyTimeoutError: false
host.io-frost-prox
   2023-01-28 18:11:16.640	error	Caught by controller[1]: forcedJSONParsing: true,
host.io-frost-prox
   2023-01-28 18:11:16.640	error	Caught by controller[1]: silentJSONParsing: true,
host.io-frost-prox
   2023-01-28 18:11:16.640	error	Caught by controller[1]: transitional: {
host.io-frost-prox
   2023-01-28 18:11:16.640	error	Caught by controller[1]: config: {
host.io-frost-prox
   2023-01-28 18:11:16.640	error	Caught by controller[1]: errno: -110,
host.io-frost-prox
   2023-01-28 18:11:16.640	error	Caught by controller[1]: code: 'ETIMEDOUT',
host.io-frost-prox
   2023-01-28 18:11:16.640	error	Caught by controller[1]: syscall: 'connect',
host.io-frost-prox
   2023-01-28 18:11:16.640	error	Caught by controller[1]: address: '52.17.162.58',
host.io-frost-prox
   2023-01-28 18:11:16.640	error	Caught by controller[1]: port: 443,
host.io-frost-prox
   2023-01-28 18:11:16.640	error	Caught by controller[1]: at TLSSocket.emit (node:domain:489:12) {
host.io-frost-prox
   2023-01-28 18:11:16.640	error	Caught by controller[1]: at TLSSocket.emit (node:events:513:28)
host.io-frost-prox
   2023-01-28 18:11:16.640	error	Caught by controller[1]: at TLSSocket.socketErrorListener (node:_http_client:494:9)
host.io-frost-prox
   2023-01-28 18:11:16.640	error	Caught by controller[1]: at ClientRequest.emit (node:domain:489:12)
host.io-frost-prox
   2023-01-28 18:11:16.640	error	Caught by controller[1]: at ClientRequest.emit (node:events:525:35)
host.io-frost-prox
   2023-01-28 18:11:16.640	error	Caught by controller[1]: at ClientRequest.eventHandlers.<computed> (/opt/iobroker/node_modules/follow-redirects/index.js:14:24)
host.io-frost-prox
   2023-01-28 18:11:16.640	error	Caught by controller[1]: at RedirectableRequest.emit (node:domain:489:12)
host.io-frost-prox
   2023-01-28 18:11:16.640	error	Caught by controller[1]: at RedirectableRequest.emit (node:events:513:28)
host.io-frost-prox
   2023-01-28 18:11:16.640	error	Caught by controller[1]: at RedirectableRequest.handleRequestError (/opt/iobroker/node_modules/iobroker.tado/node_modules/axios/lib/adapters/http.js:526:25)
host.io-frost-prox
   2023-01-28 18:11:16.640	error	Caught by controller[1]: at Function.AxiosError.from (/opt/iobroker/node_modules/iobroker.tado/node_modules/axios/lib/core/AxiosError.js:89:14)
host.io-frost-prox
   2023-01-28 18:11:16.639	error	Caught by controller[1]: AxiosError: connect ETIMEDOUT 52.17.162.58:443
tado.0
   2023-01-28 18:11:16.026	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
tado.0
   2023-01-28 18:11:16.026	info	terminating
tado.0
   2023-01-28 18:11:16.026	info	cleaned everything up...
tado.0
   2023-01-28 18:11:16.020	error	Exception-Code: ETIMEDOUT: connect ETIMEDOUT 52.17.162.58:443
tado.0
   2023-01-28 18:11:16.020	error	Error: connect ETIMEDOUT 52.17.162.58:443 at Function.AxiosError.from (/opt/iobroker/node_modules/iobroker.tado/node_modules/axios/lib/core/AxiosError.js:89:14) at RedirectableRequest.handleRequestError (/opt/iobroker/node_modules/iobroker.tado/node_modules/axios/lib/adapters/http.js:526:25) at RedirectableRequest.emit (node:events:513:28) at RedirectableRequest.emit (node:domain:489:12) at ClientRequest.eventHandlers.<computed> (/opt/iobroker/node_modules/follow-redirects/index.js:14:24) at ClientRequest.emit (node:events:525:35) at ClientRequest.emit (node:domain:489:12) at TLSSocket.socketErrorListener (node:_http_client:494:9) at TLSSocket.emit (node:events:513:28) at TLSSocket.emit (node:domain:489:12)
tado.0
   2023-01-28 18:11:16.020	error	unhandled promise rejection: connect ETIMEDOUT 52.17.162.58:443
tado.0
   2023-01-28 18:11:16.020	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
tado.0
   2023-01-28 18:11:16.019	error	Error: connect ETIMEDOUT 52.17.162.58:443

                Thomas Braun 1 Reply Last reply Reply Quote 0
                • Thomas Braun
                  Thomas Braun Most Active @Stormbringer last edited by

                  @stormbringer sagte in „Cannot update rating: certificate has expired“ admin.0:

                  so lang es nicht die eigene ist oder?

                  Auch die ist nicht zu verschleiern. Wozu auch? Wenn da keine Dienste ohne Absicherung nach außen geführt sind (was man nicht macht) kein Problem und interne IPs sind eh nicht erreichbar von extern.

                  S 1 Reply Last reply Reply Quote 0
                  • S
                    Stormbringer @Thomas Braun last edited by

                    @thomas-braun ok danke. und könntest du mir nen Tipp geben wo das Routing verstellt ist? Habe eigentlich nix gemacht...

                    Thomas Braun 1 Reply Last reply Reply Quote 0
                    • Thomas Braun
                      Thomas Braun Most Active @Stormbringer last edited by

                      @stormbringer

                      Im Internet. Da kannst du wohl nix machen.

                      S 1 Reply Last reply Reply Quote 0
                      • S
                        Stormbringer @Thomas Braun last edited by

                        @thomas-braun auch wenn mehrere Adapter bzw. IPs betroffen sind? Und du meinst das hängt auch mit dem "Cannot update rating: certificate has expired" zusammen

                        Thomas Braun 1 Reply Last reply Reply Quote 0
                        • Thomas Braun
                          Thomas Braun Most Active @Stormbringer last edited by

                          @stormbringer sagte in „Cannot update rating: certificate has expired“ admin.0:

                          auch wenn mehrere Adapter bzw. IPs betroffen sind?

                          Das ist möglich, wenn dein Internetprovider da ein Problem hat.

                          S 1 Reply Last reply Reply Quote 0
                          • M
                            mrjeschke last edited by

                            Für mich als Laien sieht das nach einem Serverproblem aus.

                            b7ffa639-601e-4474-a9a8-fef8cd516d04-image.png

                            1 Reply Last reply Reply Quote 1
                            • S
                              Stormbringer @Thomas Braun last edited by

                              @thomas-braun Heizung im Winter ist fies 🤦 Sehe gerade da gibt es nochmal einen Post:

                              https://forum.iobroker.net/topic/62471/tado-adapter-wird-nicht-mehr-grün

                              Strange.... Homeassisant kriegt die Daten problemlos rein und die App auch... Sind die nicht auch auf das angewiesen?

                              Thomas Braun 1 Reply Last reply Reply Quote 0
                              • Thomas Braun
                                Thomas Braun Most Active @Stormbringer last edited by

                                @stormbringer sagte in „Cannot update rating: certificate has expired“ admin.0:

                                Homeassisant kriegt die Daten problemlos rein und die App auch... Sind die nicht auch auf das angewiesen?

                                Nicht auf das offenbar abgelaufene Zertifikat.

                                S 1 Reply Last reply Reply Quote 0
                                • S
                                  Stormbringer @Thomas Braun last edited by

                                  @thomas-braun ok, das ist schade.... mal schauen... Notfalls kann man die Adapter ja auch wieder ersetzen und mit dem HASS Adapter integrieren. Glaub inzwischen das wäre eh das Beste alle Geräteverknüpfungen über den HASS Adapter laufen zu lassen und ioBroker nur noch die Logik machen zu lassen 🙄
                                  Aber danke für deine Hilfe und noch einen schönen Abend 😉

                                  Thomas Braun 1 Reply Last reply Reply Quote 0
                                  • Thomas Braun
                                    Thomas Braun Most Active @Stormbringer last edited by

                                    @stormbringer

                                    In meinem Log taucht das jetzt auch auf:

                                    2023-01-28 19:01:02.145  - warn: admin.0 (676) Cannot update rating: certificate has expired
2023-01-28 19:03:24.452  - info: info.0 (1587) Reading/updating systemdata.
2023-01-28 19:03:25.099  - info: info.0 (1587) cpu Temp res = {"main":43.816,"cores":[],"max":43.816,"socket":[],"chipset":null}
                                    S 1 Reply Last reply Reply Quote 1
                                    • S
                                      Stormbringer @Thomas Braun last edited by

                                      @thomas-braun Cloud Adapter gehen noch? Aber du stehst nicht auf Cloud oder?

                                      Thomas Braun 1 Reply Last reply Reply Quote 0
                                      • Thomas Braun
                                        Thomas Braun Most Active @Stormbringer last edited by

                                        @stormbringer

                                        Sowohl iobroker.iot wie iobroker.cloud dudeln hier wie immer.

                                        S 1 Reply Last reply Reply Quote 0
                                        • wendy2702
                                          wendy2702 last edited by

                                          Habe es mal ans Core Team gemeldet.

                                          S 1 Reply Last reply Reply Quote 0
                                          • S
                                            Stormbringer @Thomas Braun last edited by

                                            @thomas-braun die gehen bei mir auch. tado, bring, vesync flippen. tado im winter ist halt echt fies 🙈

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate
                                            FAQ Cloud / IOT
                                            HowTo: Node.js-Update
                                            HowTo: Backup/Restore
                                            Downloads
                                            BLOG

                                            902
                                            Online

                                            31.8k
                                            Users

                                            80.0k
                                            Topics

                                            1.3m
                                            Posts

                                            14
                                            57
                                            4282
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo