Docker Installation lädt admin Adapter nicht
-
Anbei dann noch die Diag von v8:
Skript v.2023-04-16 [34;107m*** BASE SYSTEM ***[0m Architecture : x86_64 Docker : v8.0.1 Virtualization : Unknown (buanet/Synology?) Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" NAME="Debian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" Systemuptime and Load: 18:08:27 up 3:20, 0 users, load average: 0.73, 0.84, 0.80 CPU threads: 4 [34;107m*** Time and Time Zones ***[0m Sat May 13 16:08:27 UTC 2023 Sat May 13 18:08:27 CEST 2023 CEST +0200 Etc/UTC [34;107m*** User and Groups ***[0m root /root root [34;107m*** X-Server-Setup ***[0m X-Server: false Desktop: Terminal: [34;107m*** MEMORY ***[0m total used free shared buff/cache available Mem: 3.9G 1.3G 246M 1.1G 2.3G 950M Swap: 4.4G 181M 4.2G Total: 8.3G 1.5G 4.4G 3890 M total memory 1304 M used memory 902 M active memory 1076 M inactive memory 246 M free memory 11 M buffer memory 2327 M swap cache 4383 M total swap 181 M used swap 4202 M free swap [34;107m*** FILESYSTEM ***[0m Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/cachedev_1 btrfs 8.8T 3.7T 5.1T 42% / tmpfs tmpfs 64M 0 64M 0% /dev tmpfs tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup shm tmpfs 64M 0 64M 0% /dev/shm /dev/mapper/cachedev_1 btrfs 8.8T 3.7T 5.1T 42% /opt/iobroker /dev/mapper/cachedev_1 btrfs 8.8T 3.7T 5.1T 42% /etc/hosts tmpfs tmpfs 1.9G 0 1.9G 0% /proc/acpi tmpfs tmpfs 1.9G 0 1.9G 0% /proc/scsi tmpfs tmpfs 1.9G 0 1.9G 0% /sys/firmware [32mMessages concerning ext4 filesystem in dmesg:[0m [Sat May 13 14:49:02 2023] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [Sat May 13 14:49:02 2023] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [Sat May 13 14:49:03 2023] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [Sat May 13 14:49:03 2023] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [Sat May 13 14:49:03 2023] EXT4-fs (loop0): couldn't mount as ext3 due to feature incompatibilities [Sat May 13 14:49:03 2023] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null) [Sat May 13 14:49:08 2023] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [Sat May 13 14:49:08 2023] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [Sat May 13 14:49:08 2023] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [Sat May 13 14:49:08 2023] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: barrier=1 [Sat May 13 14:49:31 2023] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null) [32mShow mounted filesystems (real ones only):[0m TARGET SOURCE FSTYPE OPTIONS / /dev/mapper/cachedev_1[/@syno/@docker/btrfs/subvolumes/e6ecc9255012492ebd334775a6260c88c76a08edb3c0b775424d72fe73930282] btrfs rw,nodev,relatime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,block_group_cache_tree,syno_allocator,subvolid=440,subvol=/@syno/@docker/btrfs/subvolumes/e6ecc9255012492ebd334775a6260c88c76a08edb3c0b775424d72fe73930282 |-/opt/iobroker /dev/mapper/cachedev_1[/@syno/docker/iobv81] btrfs rw,nodev,relatime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,block_group_cache_tree,syno_allocator,subvolid=257,subvol=/@syno/docker/iobv81 |-/etc/resolv.conf /dev/mapper/cachedev_1[/@syno/@docker/containers/29bbab4cb9922da718b03610b10e2a45b31c8c66902d5ccdbe4a31f4a00068ff/resolv.conf] btrfs rw,nodev,relatime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,block_group_cache_tree,syno_allocator,subvolid=256,subvol=/@syno/@docker/containers/29bbab4cb9922da718b03610b10e2a45b31c8c66902d5ccdbe4a31f4a00068ff/resolv.conf |-/etc/hostname /dev/mapper/cachedev_1[/@syno/@docker/containers/29bbab4cb9922da718b03610b10e2a45b31c8c66902d5ccdbe4a31f4a00068ff/hostname] btrfs rw,nodev,relatime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,block_group_cache_tree,syno_allocator,subvolid=256,subvol=/@syno/@docker/containers/29bbab4cb9922da718b03610b10e2a45b31c8c66902d5ccdbe4a31f4a00068ff/hostname `-/etc/hosts /dev/mapper/cachedev_1[/@syno/@docker/containers/29bbab4cb9922da718b03610b10e2a45b31c8c66902d5ccdbe4a31f4a00068ff/hosts] btrfs rw,nodev,relatime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,block_group_cache_tree,syno_allocator,subvolid=256,subvol=/@syno/@docker/containers/29bbab4cb9922da718b03610b10e2a45b31c8c66902d5ccdbe4a31f4a00068ff/hosts [32mFiles in neuralgic directories:[0m [32m/var:[0m 33M /var/ 30M /var/lib 18M /var/lib/apt/lists 18M /var/lib/apt 13M /var/lib/dpkg [32m/opt/iobroker/backups:[0m 0 /opt/iobroker/backups/ [32m/opt/iobroker/iobroker-data:[0m 18M /opt/iobroker/iobroker-data/ 14M /opt/iobroker/iobroker-data/files 13M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js 13M /opt/iobroker/iobroker-data/files/admin.admin/custom/static 13M /opt/iobroker/iobroker-data/files/admin.admin/custom [32mThe five largest files in iobroker-data are:[0m 6.3M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_js-node_modules_iobr-99c23e.847b8ad9.chunk.js.map 3.3M /opt/iobroker/iobroker-data/objects.jsonl 2.8M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_js-node_modules_iobr-99c23e.847b8ad9.chunk.js 1.6M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_mui_material_Accordion_index_js-node_modules_mui_material_AccordionDetai-57e02d.0886b730.chunk.js.map 652K /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_mui_material_index_js.40e01f69.chunk.js.map [34;107m*** NodeJS-Installation ***[0m /usr/bin/nodejs v18.16.0 /usr/bin/node v18.16.0 /usr/bin/npm 9.5.1 /usr/bin/npx 9.5.1 nodejs: Installed: 18.16.0-deb-1nodesource1 Candidate: 18.16.0-deb-1nodesource1 Version table: *** 18.16.0-deb-1nodesource1 500 500 https://deb.nodesource.com/node_18.x bullseye/main amd64 Packages 100 /var/lib/dpkg/status 12.22.12~dfsg-1~deb11u4 500 500 http://deb.debian.org/debian-security bullseye-security/main amd64 Packages 12.22.12~dfsg-1~deb11u3 500 500 http://deb.debian.org/debian bullseye/main amd64 Packages [32mTemp directories causing npm8 problem:[0m 0 No problems detected [34;107m*** ioBroker-Installation ***[0m [32mioBroker Status[0m iobroker is running on this host. Objects type: jsonl States type: jsonl MULTIHOSTSERVICE/enabled: false [32mCore adapters versions[0m js-controller: 4.0.24 admin: 6.3.5 javascript: "javascript" not found Adapters from github: 0 [32mAdapter State[0m + system.adapter.admin.0 : admin : buanet-iobroker4 - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.backitup.0 : backitup : buanet-iobroker4 - enabled + system.adapter.discovery.0 : discovery : buanet-iobroker4 - enabled + instance is alive [32mEnabled adapters with bindings[0m + system.adapter.admin.0 : admin : buanet-iobroker4 - enabled, port: 8081, bind: 0.0.0.0, run as: admin [32mioBroker-Repositories[0m stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): stable [32mInstalled ioBroker-Instances[0m Used repository: stable Adapter "admin" : 6.3.5 , installed 6.3.5 Adapter "backitup" : 2.6.19 , installed 2.6.19 Adapter "discovery" : 3.1.0 , installed 3.1.0 Controller "js-controller": 4.0.24 , installed 4.0.24 [32mObjects and States[0m Please stand by - This may take a while Objects: 143 States: 104 [34;107m*** OS-Repositories and Updates ***[0m Hit:1 http://deb.debian.org/debian bullseye InRelease Hit:2 http://deb.debian.org/debian-security bullseye-security InRelease Hit:3 https://deb.nodesource.com/node_18.x bullseye InRelease Hit:4 http://deb.debian.org/debian bullseye-updates InRelease Reading package lists... Pending Updates: 0 [34;107m*** Listening Ports ***[0m Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1000 1575259 - tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1000 1575252 - tcp6 0 0 :::8081 :::* LISTEN 1000 1576185 - [34;107m*** Log File - Last 25 Lines ***[0m 2023-05-13 17:47:43.755 - [32minfo[39m: host.buanet-iobroker4 iobroker.js-controller version 4.0.24 js-controller starting 2023-05-13 17:47:43.758 - [32minfo[39m: host.buanet-iobroker4 Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-05-13 17:47:43.759 - [32minfo[39m: host.buanet-iobroker4 hostname: buanet-iobroker4, node: v18.16.0 2023-05-13 17:47:43.759 - [32minfo[39m: host.buanet-iobroker4 ip addresses: 172.17.0.6 2023-05-13 17:47:44.092 - [32minfo[39m: host.buanet-iobroker4 connected to Objects and States 2023-05-13 17:47:44.102 - [32minfo[39m: host.buanet-iobroker4 Node.js version has changed from unknown to 18.16.0 2023-05-13 17:47:44.123 - [32minfo[39m: host.buanet-iobroker4 added notifications configuration of host 2023-05-13 17:47:44.258 - [32minfo[39m: host.buanet-iobroker4 3 instances found 2023-05-13 17:47:44.270 - [32minfo[39m: host.buanet-iobroker4 starting 3 instances 2023-05-13 17:47:44.296 - [32minfo[39m: host.buanet-iobroker4 instance system.adapter.admin.0 started with pid 1828 2023-05-13 17:47:44.522 - [32minfo[39m: host.buanet-iobroker4 Successfully updated capabilities "cap_net_admin, cap_net_bind_service, cap_net_raw" for /usr/bin/node 2023-05-13 17:47:45.624 - [32minfo[39m: admin.0 (1828) starting. Version 6.3.5 in /opt/iobroker/node_modules/iobroker.admin, node: v18.16.0, js-controller: 4.0.24 2023-05-13 17:47:45.641 - [32minfo[39m: admin.0 (1828) requesting all states 2023-05-13 17:47:45.641 - [32minfo[39m: admin.0 (1828) requesting all objects 2023-05-13 17:47:45.792 - [32minfo[39m: admin.0 (1828) received all objects 2023-05-13 17:47:45.918 - [32minfo[39m: admin.0 (1828) http server listening on port 8081 2023-05-13 17:47:45.919 - [32minfo[39m: admin.0 (1828) Use link "http://localhost:8081" to configure. 2023-05-13 17:47:45.922 - [32minfo[39m: admin.0 (1828) socket.io server listening on port 8081 2023-05-13 17:47:48.281 - [32minfo[39m: host.buanet-iobroker4 instance system.adapter.discovery.0 started with pid 1856 2023-05-13 17:47:48.835 - [32minfo[39m: discovery.0 (1856) starting. Version 3.1.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v18.16.0, js-controller: 4.0.24 2023-05-13 17:47:52.281 - [32minfo[39m: host.buanet-iobroker4 instance system.adapter.backitup.0 started with pid 1871 2023-05-13 17:47:52.895 - [32minfo[39m: backitup.0 (1871) starting. Version 2.6.19 in /opt/iobroker/node_modules/iobroker.backitup, node: v18.16.0, js-controller: 4.0.24 2023-05-13 17:47:52.996 - [32minfo[39m: backitup.0 (1871) [iobroker] backup will be activated at 02:40 every 1 day(s)======================= SUMMARY ======================= v.2023-04-16 Operatingsystem: Debian GNU/Linux 11 (bullseye) Kernel: 4.4.180+ Installation: Docker Timezone: Etc/UTC User-ID: 0 X-Server: false Pending OS-Updates: 0 Pending iob updates: 0 Nodejs-Installation: /usr/bin/nodejs v18.16.0 /usr/bin/node v18.16.0 /usr/bin/npm 9.5.1 /usr/bin/npx 9.5.1 Recommended versions are nodejs 18.x.y and npm 9.x.y Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 3.9G 1.3G 285M 1.1G 2.3G 917M Swap: 4.4G 184M 4.2G Total: 8.3G 1.5G 4.5G Active iob-Instances: 4 Active repo(s): stable ioBroker Core: js-controller 4.0.24 admin 6.3.5 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: + system.adapter.admin.0 : admin : buanet-iobroker4 - enabled, port: 8081, bind: 0.0.0.0, run as: admin Objects: 143 States: 104 Size of iob-Database: 3.3M /opt/iobroker/iobroker-data/objects.jsonl 228K /opt/iobroker/iobroker-data/states.jsonl =================== END OF SUMMARY ====================Habe extra Firefox runtergeladen, funktioniert aber leider auch nicht
-
@ferrog sagte in Docker Installation lädt admin Adapter nicht:
funktioniert aber leider auch nicht
... auch ein Loop mit dem ioBroker Zeichen !?
Hast du eine Host oder Bridge Netzwerk !
-
Ja, auch in loop.
Ich habe noch den alten "raspi" iobroker im Netz, aber nicht aktiv host bzw. slave konfiguriert. Sind die sich dann auch ohne Konfiguration im Wege? -
*** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1000 1575259 - tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1000 1575252 - tcp6 0 0 :::8081Da läuft der Admin wohl nur auf ipv6.
Edith: Vergiss es, ist bei mir auch so.
-
@ferrog sagte in Docker Installation lädt admin Adapter nicht:
Ich habe noch den alten "raspi" iobroker im Netz, aber nicht aktiv host bzw. slave konfiguriert. Sind die sich dann auch ohne Konfiguration im Wege?
Nein .. passt so .
Was ist mit :
@glasfaser sagte in Docker Installation lädt admin Adapter nicht:
Hast du eine Host oder Bridge Netzwerk !Bitte immer alle Fragen beantworten !
Wenn Bridge ... dann versuche zum Test Host .
-
@ferrog sagte in Docker Installation lädt admin Adapter nicht:
2023-05-13 17:47:43.759 - [32minfo[39m: host.buanet-iobroker4 ip addresses: 172.17.0.6
Sehe gerade ...
Also Bridge
-
Ah, gemeint war docker. Ja das war Bridge, habe gerade auch Host versucht, leider genau so. Liegt das vielleicht an der Bereitstellung des Ports durch DSM „Webstation“?
Oder kann der Port 8081 auch einfach gemappt werden? (Habe leider noch nicht zum Laufen bekommen…)
-
@ferrog sagte in Docker Installation lädt admin Adapter nicht:
Liegt das vielleicht an der Bereitstellung des Ports durch DSM „Webstation“?
Welcher Port hat er denn ,
dann würdest du aber nicht ioBroker mit 8081 erreichen !Der Loop ist ein anderer ( Fehler ) . kann Ihn aber nicht erkennen .
Zeige mal die Ausgabe von
iob logs --watchwenn du im Loop bist
-
Logs —watch von latest-v8:
2023-05-13 18:49:56.226 - [32minfo[39m: host.buanet-iobroker3 iobroker.js-controller version 4.0.24 js-controller starting 2023-05-13 18:49:56.229 - [32minfo[39m: host.buanet-iobroker3 Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-05-13 18:49:56.229 - [32minfo[39m: host.buanet-iobroker3 hostname: buanet-iobroker3, node: v18.16.0 2023-05-13 18:49:56.229 - [32minfo[39m: host.buanet-iobroker3 ip addresses: 192.168.178.3 fd9b:f2b9:802:4f06:9209:d0ff:fe32:33f3 2003:cd:f47:c000:9209:d0ff:fe32:33f3 fe80::9209:d0ff:fe32:33f3 172.17.0.1 fe80::42:caff:fe53:7492 fe80::5ca4:c5ff:fec1:c9b fe80::6054:cbff:fe48:42d2 fe80::8c55:c1ff:fee3:f31b fe80::f4c1:fbff:fe20:3a8f fe80::c866:afff:fe37:903a 2023-05-13 18:49:56.474 - [32minfo[39m: host.buanet-iobroker3 connected to Objects and States 2023-05-13 18:49:56.481 - [32minfo[39m: host.buanet-iobroker3 Node.js version has changed from unknown to 18.16.0 2023-05-13 18:49:56.501 - [32minfo[39m: host.buanet-iobroker3 added notifications configuration of host 2023-05-13 18:49:56.658 - [32minfo[39m: host.buanet-iobroker3 3 instances found 2023-05-13 18:49:56.661 - [32minfo[39m: host.buanet-iobroker3 starting 3 instances 2023-05-13 18:49:56.680 - [32minfo[39m: host.buanet-iobroker3 instance system.adapter.admin.0 started with pid 1761 2023-05-13 18:49:57.314 - [32minfo[39m: host.buanet-iobroker3 Successfully updated capabilities "cap_net_admin, cap_net_bind_service, cap_net_raw" for /usr/bin/node 2023-05-13 18:49:58.050 - [32minfo[39m: admin.0 (1761) starting. Version 6.3.5 in /opt/iobroker/node_modules/iobroker.admin, node: v18.16.0, js-controller: 4.0.24 2023-05-13 18:49:58.067 - [32minfo[39m: admin.0 (1761) requesting all states 2023-05-13 18:49:58.068 - [32minfo[39m: admin.0 (1761) requesting all objects 2023-05-13 18:49:58.127 - [32minfo[39m: admin.0 (1761) received all objects 2023-05-13 18:49:58.151 - [32minfo[39m: admin.0 (1761) Request actual repository... 2023-05-13 18:49:58.160 - [32minfo[39m: host.buanet-iobroker3 Updating repository "stable" under "http://download.iobroker.net/sources-dist.json" 2023-05-13 18:49:58.300 - [33mwarn[39m: admin.0 (1761) Repository cannot be read: Active repo - stable 2023-05-13 18:49:58.301 - [33mwarn[39m: admin.0 (1761) Active repository "stable" cannot be read 2023-05-13 18:49:58.763 - [31merror[39m: admin.0 (1761) port 8081 already in use 2023-05-13 18:49:58.764 - [32minfo[39m: admin.0 (1761) Terminated (ADAPTER_REQUESTED_TERMINATION): port 8081 already in use 2023-05-13 18:49:59.277 - [32minfo[39m: admin.0 (1761) terminating http server on port 8081 2023-05-13 18:49:59.289 - [31merror[39m: host.buanet-iobroker3 instance system.adapter.admin.0 terminated by request of the instance itself and will not be restarted, before user restarts it. 2023-05-13 18:49:59.290 - [32minfo[39m: host.buanet-iobroker3 Do not restart adapter system.adapter.admin.0 because desired by instance 2023-05-13 18:50:00.676 - [32minfo[39m: host.buanet-iobroker3 instance system.adapter.discovery.0 started with pid 1785 2023-05-13 18:50:01.342 - [32minfo[39m: discovery.0 (1785) starting. Version 3.1.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v18.16.0, js-controller: 4.0.24 2023-05-13 18:50:04.690 - [32minfo[39m: host.buanet-iobroker3 instance system.adapter.backitup.0 started with pid 1804 2023-05-13 18:50:05.314 - [32minfo[39m: backitup.0 (1804) starting. Version 2.6.19 in /opt/iobroker/node_modules/iobroker.backitup, node: v18.16.0, js-controller: 4.0.24 2023-05-13 18:50:05.446 - [32minfo[39m: backitup.0 (1804) [iobroker] backup will be activated at 02:40 every 1 day(s) -
@ferrog sagte in Docker Installation lädt admin Adapter nicht:
Logs
2023-05-13 17:47:52.996Bitte aktuell zeigen !!
-
Ahh, sorry falsche Datei, ist korrigiert. Da gibts auch errors…
-
@ferrog sagte in Docker Installation lädt admin Adapter nicht:
2023-05-13 18:49:58.764 - [32minfo[39m: admin.0 (1761) Terminated (ADAPTER_REQUESTED_TERMINATION): port 8081 already in use
Da läuft was doppelt , deshalb startet jetzt in diesem Log der ioBroker nicht
-
@glasfaser sagte in Docker Installation lädt admin Adapter nicht:
@ferrog sagte in Docker Installation lädt admin Adapter nicht:
Liegt das vielleicht an der Bereitstellung des Ports durch DSM „Webstation“?
Welcher Port hat er denn ,
dann würdest du aber nicht ioBroker mit 8081 erreichen !Kann du nicht meine Fragen beantworten !?
-
@glasfaser sagte in Docker Installation lädt admin Adapter nicht:
Kann du nicht meine Fragen beantworten !?
bitte lesen und befolgen!
https://forum.iobroker.net/topic/51555/hinweise-für-gute-forenbeiträge/1 -
Ich habe das nicht als Frage verstanden.
Natürlich reicht die Webstation den Port 8081 an den Docker Container weiter.
-
@ferrog sagte in Docker Installation lädt admin Adapter nicht:
Natürlich reicht die Webstation den Port 8081 an den Docker Container weiter.
Lösche alle diese Einträge !
Hier wird nur der Port vorgegeben :
siehe Beispiel Containereinstellung
und das ausschalten / haken bei dir raus
-
WOW, vielen Dank! Daran hats gelegen.
Und großen Respekt an die Schnelligkeit eurer Unterstützung!Zum Hintergrund: Belegt Webstation dann in dem Container den besagten Port?
-
@ferrog sagte in Docker Installation lädt admin Adapter nicht:
Und großen Respekt an die Schnelligkeit eurer Unterstützung!
... aber mühselig erfragt
Zum Hintergrund: Belegt Webstation dann in dem Container den besagten Port?
Jipp , deshalb meine Frage :
@glasfaser sagte in Docker Installation lädt admin Adapter nicht:
@glasfaser sagte in Docker Installation lädt admin Adapter nicht:
@ferrog sagte in Docker Installation lädt admin Adapter nicht:
Liegt das vielleicht an der Bereitstellung des Ports durch DSM „Webstation“?Welcher Port hat er denn ,
dann würdest du aber nicht ioBroker mit 8081 erreichen ! -
@ferrog sagte in Docker Installation lädt admin Adapter nicht:
WOW, vielen Dank! Daran hats gelegen.
Dann setze den Thread auf [gelöst]
