Admin-Adapter - keine IP-Adresse konfigurierbar

Eggi

@wendy2702
Sorry - folgende Ausgaben werden geschieben:

2023-02-27 13:16:11.164  - debug: admin.0 (320) Subscribes: system.adapter.discovery.0.alive, system.host.*.alive, system.host.*.notifications.*, system.adapter.*.alive, system.adapter.*.connected, system.adapter.*.inputCount, system.adapter.*.memRss, system.adapter.*.outputCount, system.adapter.*.logLevel, system.host.*.diskFree, system.host.*.diskSize, system.host.*.diskWarning, system.host.*.freemem, *.info.connection, *.info.extension, admin.0.info.newsFeed
2023-02-27 13:18:06.021  - debug: admin.0 (320) Subscribes: system.adapter.discovery.0.alive, system.host.*.alive, system.host.*.notifications.*, system.adapter.*.alive, system.adapter.*.connected, system.adapter.*.inputCount, system.adapter.*.memRss, system.adapter.*.outputCount, system.adapter.*.logLevel, system.host.*.diskFree, system.host.*.diskSize, system.host.*.diskWarning, system.host.*.freemem, *.info.connection, *.info.extension, admin.0.info.newsFeed, system.adapter.backitup.0.alive
2023-02-27 13:18:06.033  - debug: admin.0 (320) Subscribes: system.adapter.discovery.0.alive, system.host.*.alive, system.host.*.notifications.*, system.adapter.*.alive, system.adapter.*.connected, system.adapter.*.inputCount, system.adapter.*.memRss, system.adapter.*.outputCount, system.adapter.*.logLevel, system.host.*.diskFree, system.host.*.diskSize, system.host.*.diskWarning, system.host.*.freemem, *.info.connection, *.info.extension, admin.0.info.newsFeed, system.adapter.backitup.0.alive, system.adapter.backitup.0.connected
2023-02-27 13:18:06.048  - debug: admin.0 (320) Subscribes: system.adapter.discovery.0.alive, system.host.*.alive, system.host.*.notifications.*, system.adapter.*.alive, system.adapter.*.connected, system.adapter.*.inputCount, system.adapter.*.memRss, system.adapter.*.outputCount, system.adapter.*.logLevel, system.host.*.diskFree, system.host.*.diskSize, system.host.*.diskWarning, system.host.*.freemem, *.info.connection, *.info.extension, admin.0.info.newsFeed, system.adapter.backitup.0.alive, system.adapter.backitup.0.connected, system.adapter.backitup.0.info.connection
2023-02-27 13:18:06.357  - debug: admin.0 (320) successful connection to socket.io from ::ffff:192.168.8.101
2023-02-27 13:18:06.358  - debug: admin.0 (320) socket.io client system.user.admin connected
2023-02-27 13:18:06.359  - info: admin.0 (320) ==> Connected system.user.admin from ::ffff:192.168.8.101
2023-02-27 13:18:06.768  - debug: backitup.0 (393) telegram-instance: 
2023-02-27 13:18:06.817  - debug: admin.0 (320) Subscribes: backitup.0.*
2023-02-27 13:18:06.818  - debug: admin.0 (320) Subscribes: backitup.0.*, system.adapter.backitup.0.alive
2023-02-27 13:18:11.552  - debug: backitup.0 (393) Backup list be read ...
2023-02-27 13:18:11.899  - debug: backitup.0 (393) FTP: connected.
2023-02-27 13:18:15.832  - debug: backitup.0 (393) Backup list be read ...
2023-02-27 13:18:16.161  - debug: backitup.0 (393) FTP: connected.
2023-02-27 13:19:28.081  - debug: backitup.0 (393) FTP: connected.
2023-02-27 13:19:28.082  - debug: backitup.0 (393) FTP: Get file: /Backups/Smarthome/SD153/iobroker/iobroker_2023_02_27-02_40_10_Synology_backupiobroker.tar.gz
2023-02-27 13:19:28.081  - debug: backitup.0 (393) FTP: connected.
2023-02-27 13:19:28.082  - debug: backitup.0 (393) FTP: Get file: /Backups/Smarthome/SD153/iobroker/iobroker_2023_02_27-02_40_10_Synology_backupiobroker.tar.gz
2023-02-27 13:19:34.482  - debug: backitup.0 (393) FTP: Download done
2023-02-27 13:19:34.522  - info: host.iobroker received SIGTERM
2023-02-27 13:19:34.523  - info: zigbee.0 (362) cleaned everything up...
2023-02-27 13:19:34.524  - info: admin.0 (320) terminating https server on port 8081
2023-02-27 13:19:34.526  - info: backitup.0 (393) cleaned everything up...
2023-02-27 13:19:34.524  - info: zigbee.0 (362) Zigbee: disabling joining new devices.
2023-02-27 13:19:34.529  - warn: zigbee.0 (362) Failed to stop zigbee during startup
2023-02-27 13:19:34.523  - info: host.iobroker stopInstance system.adapter.admin.0 (force=false, process=true)
2023-02-27 13:19:34.523  - info: host.iobroker stopInstance system.adapter.javascript.0 (force=false, process=true)
2023-02-27 13:19:34.523  - info: host.iobroker stopInstance system.adapter.zigbee.0 (force=false, process=true)
2023-02-27 13:19:34.523  - info: host.iobroker stopInstance system.adapter.discovery.0 (force=false, process=true)
2023-02-27 13:19:34.523  - info: host.iobroker stopInstance system.adapter.backitup.0 (force=false, process=true)
2023-02-27 13:19:34.523  - info: host.iobroker stopInstance system.adapter.web.0 (force=false, process=true)
2023-02-27 13:19:34.532  - info: host.iobroker stopInstance system.adapter.vis.0 (force=false, process=false)
2023-02-27 13:19:34.532  - info: host.iobroker stopInstance system.adapter.iot.0 (force=false, process=true)
2023-02-27 13:19:34.532  - info: host.iobroker stopInstance system.adapter.cloud.0 (force=false, process=true)
2023-02-27 13:19:34.543  - info: javascript.0 (347) Got terminate signal TERMINATE_YOURSELF
2023-02-27 13:19:34.543  - info: backitup.0 (393) Got terminate signal TERMINATE_YOURSELF
2023-02-27 13:19:34.544  - info: discovery.0 (378) Got terminate signal TERMINATE_YOURSELF
2023-02-27 13:19:34.545  - info: cloud.0 (469) Got terminate signal TERMINATE_YOURSELF
2023-02-27 13:19:34.547  - info: cloud.0 (469) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-02-27 13:19:34.545  - info: iot.0 (442) Got terminate signal TERMINATE_YOURSELF
2023-02-27 13:19:34.548  - info: web.0 (409) Got terminate signal TERMINATE_YOURSELF
2023-02-27 13:19:34.550  - info: admin.0 (320) Got terminate signal TERMINATE_YOURSELF
2023-02-27 13:19:34.550  - info: iot.0 (442) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-02-27 13:19:34.551  - info: discovery.0 (378) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-02-27 13:19:34.551  - info: zigbee.0 (362) Got terminate signal TERMINATE_YOURSELF
2023-02-27 13:19:34.551  - debug: admin.0 (320) Plugin sentry destroyed
2023-02-27 13:19:34.552  - info: javascript.0 (347) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-02-27 13:19:34.552  - info: admin.0 (320) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-02-27 13:19:34.555  - info: zigbee.0 (362) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-02-27 13:19:34.584  - info: host.iobroker stopInstance system.adapter.admin.0 send kill signal
2023-02-27 13:19:34.586  - info: host.iobroker stopInstance system.adapter.javascript.0 send kill signal
2023-02-27 13:19:34.586  - info: host.iobroker stopInstance system.adapter.zigbee.0 send kill signal
2023-02-27 13:19:34.586  - info: host.iobroker stopInstance system.adapter.discovery.0 send kill signal
2023-02-27 13:19:34.586  - info: host.iobroker stopInstance system.adapter.backitup.0 send kill signal
2023-02-27 13:19:34.586  - info: host.iobroker stopInstance system.adapter.web.0 send kill signal
2023-02-27 13:19:34.586  - info: host.iobroker stopInstance system.adapter.iot.0 send kill signal
2023-02-27 13:19:34.586  - info: host.iobroker stopInstance system.adapter.cloud.0 send kill signal
2023-02-27 13:19:34.592  - debug: backitup.0 (393) Plugin sentry destroyed
2023-02-27 13:19:34.592  - info: web.0 (409) terminated http server on port 8082
2023-02-27 13:19:34.592  - info: backitup.0 (393) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-02-27 13:19:34.637  - info: web.0 (409) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-02-27 13:19:35.095  - info: host.iobroker instance system.adapter.cloud.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-02-27 13:19:35.104  - info: host.iobroker instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-02-27 13:19:35.105  - info: host.iobroker instance system.adapter.iot.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-02-27 13:19:35.110  - info: host.iobroker instance system.adapter.zigbee.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-02-27 13:19:35.117  - info: host.iobroker instance system.adapter.javascript.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-02-27 13:19:35.130  - info: host.iobroker instance system.adapter.discovery.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-02-27 13:19:35.151  - info: host.iobroker instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-02-27 13:19:35.193  - info: host.iobroker instance system.adapter.web.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-02-27 13:19:35.193  - info: host.iobroker All instances are stopped.
2023-02-27 13:19:35.358  - info: host.iobroker terminated
2023-02-27 13:19:34.482  - debug: backitup.0 (393) FTP: Download done
2023-02-27 13:19:34.522  - info: host.iobroker received SIGTERM
2023-02-27 13:19:34.523  - info: zigbee.0 (362) cleaned everything up...
2023-02-27 13:19:34.524  - info: admin.0 (320) terminating https server on port 8081
2023-02-27 13:19:34.526  - info: backitup.0 (393) cleaned everything up...
2023-02-27 13:19:34.524  - info: zigbee.0 (362) Zigbee: disabling joining new devices.
2023-02-27 13:19:34.529  - warn: zigbee.0 (362) Failed to stop zigbee during startup
2023-02-27 13:19:34.523  - info: host.iobroker stopInstance system.adapter.admin.0 (force=false, process=true)
2023-02-27 13:19:34.523  - info: host.iobroker stopInstance system.adapter.javascript.0 (force=false, process=true)
2023-02-27 13:19:34.523  - info: host.iobroker stopInstance system.adapter.zigbee.0 (force=false, process=true)
2023-02-27 13:19:34.523  - info: host.iobroker stopInstance system.adapter.discovery.0 (force=false, process=true)
2023-02-27 13:19:34.523  - info: host.iobroker stopInstance system.adapter.backitup.0 (force=false, process=true)
2023-02-27 13:19:34.523  - info: host.iobroker stopInstance system.adapter.web.0 (force=false, process=true)
2023-02-27 13:19:34.532  - info: host.iobroker stopInstance system.adapter.vis.0 (force=false, process=false)
2023-02-27 13:19:34.532  - info: host.iobroker stopInstance system.adapter.iot.0 (force=false, process=true)
2023-02-27 13:19:34.532  - info: host.iobroker stopInstance system.adapter.cloud.0 (force=false, process=true)
2023-02-27 13:19:34.543  - info: javascript.0 (347) Got terminate signal TERMINATE_YOURSELF
2023-02-27 13:19:34.543  - info: backitup.0 (393) Got terminate signal TERMINATE_YOURSELF
2023-02-27 13:19:34.544  - info: discovery.0 (378) Got terminate signal TERMINATE_YOURSELF
2023-02-27 13:19:34.545  - info: cloud.0 (469) Got terminate signal TERMINATE_YOURSELF
2023-02-27 13:19:34.547  - info: cloud.0 (469) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-02-27 13:19:34.545  - info: iot.0 (442) Got terminate signal TERMINATE_YOURSELF
2023-02-27 13:19:34.548  - info: web.0 (409) Got terminate signal TERMINATE_YOURSELF
2023-02-27 13:19:34.550  - info: admin.0 (320) Got terminate signal TERMINATE_YOURSELF
2023-02-27 13:19:34.550  - info: iot.0 (442) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-02-27 13:19:34.551  - info: discovery.0 (378) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-02-27 13:19:34.551  - info: zigbee.0 (362) Got terminate signal TERMINATE_YOURSELF
2023-02-27 13:19:34.551  - debug: admin.0 (320) Plugin sentry destroyed
2023-02-27 13:19:34.552  - info: javascript.0 (347) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-02-27 13:19:34.552  - info: admin.0 (320) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-02-27 13:19:34.555  - info: zigbee.0 (362) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-02-27 13:19:34.584  - info: host.iobroker stopInstance system.adapter.admin.0 send kill signal
2023-02-27 13:19:34.586  - info: host.iobroker stopInstance system.adapter.javascript.0 send kill signal
2023-02-27 13:19:34.586  - info: host.iobroker stopInstance system.adapter.zigbee.0 send kill signal
2023-02-27 13:19:34.586  - info: host.iobroker stopInstance system.adapter.discovery.0 send kill signal
2023-02-27 13:19:34.586  - info: host.iobroker stopInstance system.adapter.backitup.0 send kill signal
2023-02-27 13:19:34.586  - info: host.iobroker stopInstance system.adapter.web.0 send kill signal
2023-02-27 13:19:34.586  - info: host.iobroker stopInstance system.adapter.iot.0 send kill signal
2023-02-27 13:19:34.586  - info: host.iobroker stopInstance system.adapter.cloud.0 send kill signal
2023-02-27 13:19:34.592  - debug: backitup.0 (393) Plugin sentry destroyed
2023-02-27 13:19:34.592  - info: web.0 (409) terminated http server on port 8082
2023-02-27 13:19:34.592  - info: backitup.0 (393) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-02-27 13:19:34.637  - info: web.0 (409) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-02-27 13:19:35.095  - info: host.iobroker instance system.adapter.cloud.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-02-27 13:19:35.104  - info: host.iobroker instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-02-27 13:19:35.105  - info: host.iobroker instance system.adapter.iot.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-02-27 13:19:35.110  - info: host.iobroker instance system.adapter.zigbee.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-02-27 13:19:35.117  - info: host.iobroker instance system.adapter.javascript.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-02-27 13:19:35.130  - info: host.iobroker instance system.adapter.discovery.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-02-27 13:19:35.151  - info: host.iobroker instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-02-27 13:19:35.193  - info: host.iobroker instance system.adapter.web.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-02-27 13:19:35.193  - info: host.iobroker All instances are stopped.
2023-02-27 13:19:35.358  - info: host.iobroker terminated
2023-02-27 13:20:59.443  - info: host.buanet-iobroker iobroker.js-controller version 4.0.24 js-controller starting
2023-02-27 13:20:59.445  - info: host.buanet-iobroker Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
2023-02-27 13:20:59.446  - info: host.buanet-iobroker hostname: buanet-iobroker, node: v16.19.1
2023-02-27 13:20:59.446  - info: host.buanet-iobroker ip addresses: 192.168.8.113 fe80::78bb:64ff:fe49:7552
2023-02-27 13:21:00.546  - info: host.buanet-iobroker connected to Objects and States
2023-02-27 13:21:00.589  - info: host.buanet-iobroker added notifications configuration of host
2023-02-27 13:21:00.590  - info: host.buanet-iobroker Node.js version has changed from 16.17.1 to 16.19.1
2023-02-27 13:21:00.610  - info: host.buanet-iobroker Successfully updated capabilities "cap_net_admin, cap_net_bind_service, cap_net_raw" for /usr/bin/node
2023-02-27 13:21:01.030  - info: host.buanet-iobroker Delete host system.host.iobroker
2023-02-27 13:21:01.198  - info: host.buanet-iobroker Delete state "system.host.buanet-iobroker.versions.nodeCurrent"
2023-02-27 13:21:01.199  - info: host.buanet-iobroker 85 instances found
2023-02-27 13:21:01.209  - warn: host.buanet-iobroker does not start any instances on this host
2023-02-27 13:21:01.259  - info: host.buanet-iobroker Delete state "system.host.buanet-iobroker.versions.nodeNewest"
2023-02-27 13:21:01.306  - info: host.buanet-iobroker Delete state "system.host.buanet-iobroker.versions.nodeNewestNext"
2023-02-27 13:21:01.350  - info: host.buanet-iobroker Delete state "system.host.buanet-iobroker.versions.npmCurrent"
2023-02-27 13:21:01.395  - info: host.buanet-iobroker Delete state "system.host.buanet-iobroker.versions.npmNewest"
2023-02-27 13:21:01.442  - info: host.buanet-iobroker Delete state "system.host.buanet-iobroker.versions.npmNewestNext"
2023-02-27 13:21:01.487  - info: host.buanet-iobroker Some obsolete host states deleted.
2023-02-27 13:20:59.443  - info: host.buanet-iobroker iobroker.js-controller version 4.0.24 js-controller starting
2023-02-27 13:20:59.445  - info: host.buanet-iobroker Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
2023-02-27 13:20:59.446  - info: host.buanet-iobroker hostname: buanet-iobroker, node: v16.19.1
2023-02-27 13:20:59.446  - info: host.buanet-iobroker ip addresses: 192.168.8.113 fe80::78bb:64ff:fe49:7552
2023-02-27 13:21:00.546  - info: host.buanet-iobroker connected to Objects and States
2023-02-27 13:21:00.589  - info: host.buanet-iobroker added notifications configuration of host
2023-02-27 13:21:00.590  - info: host.buanet-iobroker Node.js version has changed from 16.17.1 to 16.19.1
2023-02-27 13:21:00.610  - info: host.buanet-iobroker Successfully updated capabilities "cap_net_admin, cap_net_bind_service, cap_net_raw" for /usr/bin/node
2023-02-27 13:21:01.030  - info: host.buanet-iobroker Delete host system.host.iobroker
2023-02-27 13:21:01.198  - info: host.buanet-iobroker Delete state "system.host.buanet-iobroker.versions.nodeCurrent"
2023-02-27 13:21:01.199  - info: host.buanet-iobroker 85 instances found
2023-02-27 13:21:01.209  - warn: host.buanet-iobroker does not start any instances on this host
2023-02-27 13:21:01.259  - info: host.buanet-iobroker Delete state "system.host.buanet-iobroker.versions.nodeNewest"
2023-02-27 13:21:01.306  - info: host.buanet-iobroker Delete state "system.host.buanet-iobroker.versions.nodeNewestNext"
2023-02-27 13:21:01.350  - info: host.buanet-iobroker Delete state "system.host.buanet-iobroker.versions.npmCurrent"
2023-02-27 13:21:01.395  - info: host.buanet-iobroker Delete state "system.host.buanet-iobroker.versions.npmNewest"
2023-02-27 13:21:01.442  - info: host.buanet-iobroker Delete state "system.host.buanet-iobroker.versions.npmNewestNext"
2023-02-27 13:21:01.487  - info: host.buanet-iobroker Some obsolete host states deleted.

MOD EDIT: LOG IN CODE TAGS </> GESETZT

crunchip

@eggi sagte in Admin-Adapter - keine IP-Adresse konfigurierbar:

host.buanet-iobroker

Bin grad nur am Handy, von docker war bis jetzt aber nicht die Rede
Passt der Hostname?

Eggi

@crunchip
Mal an dieser Stelle einen recht herzlichen Dank für Deine Hilfe

Bisher wurde der ioBroker auf der Synology unter Docker betrieben.
Unter Proxmox möchte ich diesen direkt in einem Container verwenden (ohne Docker).
Ja, der Hostname hat sich offensichtlich geändert --> unter der Installation lautet dieser "iobroker" - nach dem Backup "buanet-iobroker".
Kann das das Problem sein? Wie ändere ich den Hostnamen von buanet-iobroker auf iobroker zurück?

Homoran

@eggi sagte in Admin-Adapter - keine IP-Adresse konfigurierbar:

daß das Backup "Restore completed successfully"

das heisst nur, dass alle Konfigurationsdaten wiederhergestellt wurden.

Danach startet der js-controller erst mit der Installation der zugehörigen Adapter, um sie für das neue Umfeld (Hardware/node-Version...) passend zu kompilieren.

Homoran

@eggi sagte in Admin-Adapter - keine IP-Adresse konfigurierbar:

Ja, der Hostname hat sich offensichtlich geändert --> unter der Installation lautet dieser "iobroker" - nach dem Backup "buanet-iobroker".

iobroker ist der Systemuser für ioBroker.
Ob es sinnvoll ist auch den host so zu benennen kann man diskutieren.

Backitup macht eigentlich ein iobroker host this damit der aktuelle Hostname übernommen wird.
Wenn du allerdings die komplette Installation nach dem Wiedereinlesen (bis zu 1h) gestört hast, ist jetzt alles möglich.

Eggi

@homoran
Danke für Deine Hilfe
Du meinst, daß die Wiederherstellung länger dauert?
Ich habe schon eine Stunde zugewartet, ohne daß sich etwas getan hat - und im Log wird auch nicht rausgeschrieben....

Homoran

@eggi sagte in Admin-Adapter - keine IP-Adresse konfigurierbar:

Ich habe schon eine Stunde zugewartet,

ohne irgendetwas am iobroker zu "manipulieren"?

Eggi

@homoran ja

Eggi

@homoran
Ich starte mal das Backup erneut und warte bis morgen früh.....

Homoran

@eggi hab gerade Docker und Container gelesen. Dann bin ich raus.
Nutze beides wegen der komplexen Fehlermöglichkeiten nicht.

Eggi

Uuuups - der admin.0-Adapter läßt sich auf einmal aufrufen.
Nur die meisten anderen Adapter (bis auf BackItUp) bleiben auf rot:

Eggi

Hey - kann das sein, daß die Adapter schön langsam zum Leben erwachen. Wenn man diese startet werden sie zwar "rot", wenn man aber einmal auf reboot drückt, ändern sie auf "grün"

Thomas Braun

@eggi

Das ist mehr oder weniger das normale Verhalten beim Rückspielen eines Backups.

crunchip

@eggi weil die nach und nach erst geladen werden, wie bereits geschrieben. Das dauert seine Zeit, es reicht auch die Browserseite zu aktualisieren, du musst keine Instanzen manuell betätigen.
Alles andere siehst du auf der Konsole, wie ebenfalls bereits geschrieben.

Community Forum

NEWS

Admin-Adapter - keine IP-Adresse konfigurierbar

Support us

577

32.9k

82.9k

1.3m