Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Kein Zugriff auf Admin Oberfläche

    NEWS

    • ioBroker 10-Jahres Community Treffen - ein kleiner ReCap

    • Tester für Responsive Initiative gesucht

    • 50€: Mach mit bei einer Smarthome Studie mit ioBroker!

    Kein Zugriff auf Admin Oberfläche

    This topic has been deleted. Only users with topic management privileges can see it.
    • joergfrde
      joergfrde @AlCalzone last edited by

      @AlCalzone Hat ohne Probleme funktioniert, danke

      1 Reply Last reply Reply Quote 0
      • N
        nousefor82 last edited by nousefor82

        Hallo,

        ich komme auch nicht mehr auf die Admin Oberfläche.

        Ich habe gestern den Admin upgedatet.

        C:\Users\Jörg\ioBroker>node -v
v10.19.0

C:\Users\Jörg\ioBroker>npm -v
6.4.1

        C:\Users\Jörg\ioBroker> npm install iobroker.js-controller
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3

> iobroker.js-controller@1.5.14 preinstall C:\Users\Jörg\ioBroker\node_modules\iobroker.js-controller
> node lib/preinstallCheck.js

NPM version: 6.4.1
npm version >= 5: disabling package-lock

> unix-dgram@0.2.3 install C:\Users\Jörg\ioBroker\node_modules\unix-dgram
> node-gyp rebuild


C:\Users\Jörg\ioBroker\node_modules\unix-dgram>if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
gyp ERR! configure error
gyp ERR! stack Error: Can't find Python executable "python2.7", you can set the PYTHON env variable.
gyp ERR! stack     at PythonFinder.failNoPython (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:484:19)
gyp ERR! stack     at PythonFinder.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:509:16)
gyp ERR! stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\graceful-fs\polyfills.js:284:29
gyp ERR! stack     at FSReqWrap.oncomplete (fs.js:153:21)
gyp ERR! System Windows_NT 10.0.17763
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\Jörg\ioBroker\node_modules\unix-dgram
gyp ERR! node -v v10.19.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok

> iobroker.js-controller@1.5.14 install C:\Users\Jörg\ioBroker\node_modules\iobroker.js-controller
> node iobroker.js setup first

npm WARN enoent ENOENT: no such file or directory, open 'C:\Users\Jörg\ioBroker\node_modules\tmp\package.json'
npm WARN enoent ENOENT: no such file or directory, open 'C:\Users\Jörg\ioBroker\node_modules\iobroker.zigbee\node_modules\cc-znp\package.json'
npm WARN ws@7.2.1 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer dependencies yourself.
npm WARN ws@7.2.1 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.
npm WARN onvif-snapshot@1.0.2 requires a peer of onvif@^0.5.5 but none is installed. You must install peer dependencies yourself.
npm WARN ws@7.2.1 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer dependencies yourself.
npm WARN ws@7.2.1 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.5 (node_modules\osx-temperature-sensor):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.5: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@0.2.3 (node_modules\unix-dgram):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@0.2.3 install: `node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1

+ iobroker.js-controller@1.5.14
added 35 packages from 20 contributors, removed 173 packages, updated 40 packages, moved 15 packages and audited 833 packages in 77.298s
found 17 vulnerabilities (11 low, 6 high)
  run `npm audit fix` to fix them, or `npm audit` for details

        C:\Users\Jörg\ioBroker>node node_modules/iobroker.js-controller/controller.js --logs
2020-02-12 21:47:34.750  - info: host.DESKTOP-P9BVQ1I iobroker.js-controller version 1.5.14 js-controller starting
2020-02-12 21:47:34.756  - info: host.DESKTOP-P9BVQ1I Copyright (c) 2014-2018 bluefox, 2014 hobbyquaker
2020-02-12 21:47:34.757  - info: host.DESKTOP-P9BVQ1I hostname: DESKTOP-P9BVQ1I, node: v10.19.0
2020-02-12 21:47:34.772  - info: host.DESKTOP-P9BVQ1I ip addresses: 2002:bcc2:441c:0:65e2:1607:2b76:8b96 2002:bcc2:441c:0:9ce6:2d48:78e4:d66b fe80::65e2:1607:2b76:8b96 192.168.188.60
2020-02-12 21:47:35.166  - info: host.DESKTOP-P9BVQ1I  inMem-states listening on port 9000
2020-02-12 21:47:36.256  - info: host.DESKTOP-P9BVQ1I  inMem-objects listening on port 9001
2020-02-12 21:47:36.272  - error: Another instance is running or some application uses port!
2020-02-12 21:47:36.274  - error: uncaught exception: listen EADDRINUSE: address already in use 127.0.0.1:9000
2020-02-12 21:47:36.286  - info: host.DESKTOP-P9BVQ1I terminated
2020-02-12 21:47:36.331  - info: iobroker _restart
2020-02-12 21:47:36.353  - info: host.DESKTOP-P9BVQ1I InMemoryDB connected
2020-02-12 21:47:36.496  - info: host.DESKTOP-P9BVQ1I 66 instances found
host.DESKTOP-P9BVQ1I check instance "system.adapter.admin.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.discovery.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.web.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.vis.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.hue.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.vis-hqwidgets.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.lupusec.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.javascript.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.alexa2.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.cloud.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.daswetter.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.tr-064.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.yr.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.dwd.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.vis-jqui-mfd.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.vis-weather.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.sonos.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.sayit.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.feiertage.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.spotify-premium.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.vis-timeandweather.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.vis-colorpicker.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.ical.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.shelly.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.pushover.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.yamaha.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.telegram.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.text2command.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.vis-players.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.mihome-vacuum.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.harmony.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.vis-metro.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.vis-fancyswitch.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.vis-history.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.vis-google-fonts.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.ical.1" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.javascript.1" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.synology.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.hm-rpc.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.hm-rega.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.hm-rpc.1" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.fullybrowser.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.vis-justgage.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.unifi.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.node-red.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.backitup.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.pollenflug.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.info.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.zigbee.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.mihome.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.iqontrol.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.iot.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.onvif.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.trashschedule.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.parser.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.ical.2" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.simple-api.0" for host "DESKTOP-P9BVQ1I"
host.DESKTOP-P9BVQ1I check instance "system.adapter.yahka.0" for host "DESKTOP-P9BVQ1I"
2020-02-12 21:47:36.829  - info: host.DESKTOP-P9BVQ1I starting 55 instances
listen EADDRINUSE: address already in use 127.0.0.1:9001
Error: listen EADDRINUSE: address already in use 127.0.0.1:9001
    at Server.setupListenHandle [as _listen2] (net.js:1280:14)
    at listenInCluster (net.js:1328:12)
    at doListen (net.js:1461:7)
    at process._tickCallback (internal/process/next_tick.js:63:19)
    at Function.Module.runMain (internal/modules/cjs/loader.js:834:11)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3)

        System: Win10

        Mit der Bitte um Hilfe,

        Jörg!

        AlCalzone 1 Reply Last reply Reply Quote 0
        • AlCalzone
          AlCalzone Developer @nousefor82 last edited by

          @nousefor82 sagte in Kein Zugriff auf Admin Oberfläche:

          Error: Can't find Python executable "python2.7", you can set the PYTHON env variable.

          ==> https://www.npmjs.com/package/windows-build-tools installieren.

          N 1 Reply Last reply Reply Quote 0
          • N
            nousefor82 @AlCalzone last edited by

            @AlCalzone

            Servus, danke.

            Leider hat "der" hingeschrieben, dass python bereits installiert ist.

            Auf 8081 lässt sich immer noch nicht zugreifen.

            VG

            1 Reply Last reply Reply Quote 0
            • N
              nousefor82 last edited by

              Noch jemand eine Idee, woran es liegen könnte, dass ich plötzlich nicht mehr auf die Admin Oberfläche zugreifen kann?

              arteck 1 Reply Last reply Reply Quote 0
              • arteck
                arteck Developer Most Active @nousefor82 last edited by

                @nousefor82 du hast eine manell installierte iobroker version.. da können wir lange suchen..

                nimm den installer und portiere deine jetzige in die neue rein.. fertig

                N 1 Reply Last reply Reply Quote 0
                • N
                  nousefor82 @arteck last edited by nousefor82

                  @arteck

                  Hi,

                  hab ich probiert...wurde mit eine Fehlermeldung beendet:

                  Fehler beim Ausführen eines Post - Installationsschrittes.
Die Installation wird möglicherweise nicht korrekt abgeschlossen.
Kritischer Installationsfehler. Keine aktive ioBroker Admin-Instanz auf Port 8091. 
Abbruch der Installation.

                  Danke!

                  1 Reply Last reply Reply Quote 0
                  • N
                    nousefor82 last edited by

                    Oh Mann...das nervt grad.

                    Ich habe mal gelesen, dass man über die objects.json die scripte extrahieren kann.

                    Habe das mal probiert bin mir aber nicht sicher, von wo bis wo die im code aktuell gehen, bzw. was ich da kopieren muss.

                    Ein Neuinstallation läuft durch...hab dann probiert über backitup ein backup einzuspielen (Stand, bei dem noch alles funktioniert hatte), jetzt komm ich auch nicht mehr auf die neue Admin - Oberfläche.

                    Noch jemand eine Idee, wie ich auf die 8081 kommen könnte?

                    Vielen Dank!

                    1 Reply Last reply Reply Quote 0
                    • N
                      nousefor82 last edited by

                      So, komme wieder drauf...weiß nur nicht warum.

                      Habe folgendes eingegeben mit nachfolgenden Fehlermeldungen...trotzdem kann ich wieder zugreifen...

                      C:\Users\Jörg\ioBroker>iobroker stop

C:\Users\Jörg\ioBroker>node node_modules/iobroker.js-controller/iobroker.js stop
iobroker controller daemon is not running

C:\Users\Jörg\ioBroker>ps auxww|grep io
Der Befehl "ps" ist entweder falsch geschrieben oder
konnte nicht gefunden werden.

C:\Users\Jörg\ioBroker>iobroker upgrade self

C:\Users\Jörg\ioBroker>node node_modules/iobroker.js-controller/iobroker.js upgrade self
Update js-controller from @1.5.14 to @2.2.8
NPM version: 6.4.1
npm install iobroker.js-controller@2.2.8 --unsafe-perm --production --save --prefix "C:/Users/Jörg/ioBroker" (System call)
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor.
gyp ERR! configure error
gyp ERR! stack Error: Can't find Python executable "python2.7", you can set the PYTHON env variable.
gyp ERR! stack     at PythonFinder.failNoPython (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:484:19)
gyp ERR! stack     at PythonFinder.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:509:16)
gyp ERR! stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\graceful-fs\polyfills.js:284:29
gyp ERR! stack     at FSReqWrap.oncomplete (fs.js:153:21)
gyp ERR! System Windows_NT 10.0.17763
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\Jörg\ioBroker\node_modules\iobroker.js-controller\node_modules\unix-dgram
gyp ERR! node -v v10.19.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
gyp ERR! configure error
gyp ERR! stack Error: Can't find Python executable "python2.7", you can set the PYTHON env variable.
gyp ERR! stack     at PythonFinder.failNoPython (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:484:19)
gyp ERR! stack     at PythonFinder.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:509:16)
gyp ERR! stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\graceful-fs\polyfills.js:284:29
gyp ERR! stack     at FSReqWrap.oncomplete (fs.js:153:21)
gyp ERR! System Windows_NT 10.0.17763
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\Jörg\ioBroker\node_modules\iobroker.js-controller\node_modules\diskusage
gyp ERR! node -v v10.19.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
npm WARN ajv-keywords@2.1.1 requires a peer of ajv@^5.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules\iobroker.js-controller\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@2.0.3 (node_modules\iobroker.js-controller\node_modules\unix-dgram):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@2.0.3 install: `node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: diskusage@1.1.3 (node_modules\iobroker.js-controller\node_modules\diskusage):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: diskusage@1.1.3 install: `node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1

Host "DESKTOP-P9BVQ1I" (win32) updated
Starting node restart.js

C:\Users\Jörg\ioBroker>iobroker stop

C:\Users\Jörg\ioBroker>node node_modules/iobroker.js-controller/iobroker.js stop
iobroker controller daemon is not running

C:\Users\Jörg\ioBroker>iobroker upgrade admin

C:\Users\Jörg\ioBroker>node node_modules/iobroker.js-controller/iobroker.js upgrade admin
Adapter "admin"          is not installed.

C:\Users\Jörg\ioBroker>iobroker install admin

C:\Users\Jörg\ioBroker>node node_modules/iobroker.js-controller/iobroker.js install admin
adapter "admin" already installed. Use "upgrade" to upgrade to a newer version.

C:\Users\Jörg\ioBroker>iobroker
                      1 Reply Last reply Reply Quote 0
                      • N
                        nousefor82 last edited by

                        Das war wohl nix....kein Zugriff mehr möglich. Aber solang ich den Zugriff hatte, habe ich per Hand sämtliche Scripte etc. gesichert.

                        Habe nun komplett neu installiert. LEider noch die Version 1.5.14 .... trau mich nicht mehr mir

                        iobroker upgrade self

                        abzudaten...
                        😕

                        1 Reply Last reply Reply Quote 0
                        • rweise
                          rweise last edited by rweise

                          Bei mir 2 Installationen mit 7.2.1 kein Zugriff mehr. Der IOBroker hat aber im Hintergrund anstandslos gearbeitet. Die Lösung war ein Downgrade zu 7.2.0. hat auf beiden Geräten fuktioniert. Natürlich dann in der Konsole.

                          1. cd /opt/iobroker
                          2. iobroker stop
                          3. npm install iobroker.admin@7.2.0 --production
                          4. iobroker start

                          und schon ging es wieder 🙂
                          Ähm, hab es erst außerhalb von /opt/iobroker versucht. Dann macht er aber kein Downgrade...

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

                            @rweise sagte in Kein Zugriff auf Admin Oberfläche:

                            Ähm, hab es erst außerhalb von /opt/iobroker versucht. Dann macht er aber kein Downgrade...

                            Du sieht schon, dass der Thread 4 Jahre alt ist?
                            Und du verwendest die falschen Befehle im falschen Verzeichnis...

                            Mit

                            iob upgrade admin@7.20.0

                            hätte es funktioniert. Und wo ist das Log von deinem Beta-Testing?

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

                              @thomas-braun
                              Sorry, hab den falschen Thread erwischt...

                              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

                              862
                              Online

                              30.4k
                              Users

                              76.7k
                              Topics

                              1.2m
                              Posts

                              admin
                              8
                              27
                              1559
                              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