Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. "gelöst" iobroker nach Umzug kein Internet mehr

    NEWS

    • Amazon Alexa - ioBroker Skill läuft aus ?

    • Monatsrückblick – September 2025

    • Neues Video "KI im Smart Home" - ioBroker plus n8n

    "gelöst" iobroker nach Umzug kein Internet mehr

    This topic has been deleted. Only users with topic management privileges can see it.
    • I
      io_laurent @guergen last edited by

      @guergen Mein System ist auf einer SSD per USB am Raspi. Also vom alten Raspi alles abgezogen, an den neuen angeschlossen und in der Fritz!Box hab ich dem neuen Raspi die IP, welcher der vorherige Raspi fest vergeben hatte, fest zugewiesen.
      Das war so mein naiver Plan.
      System:
      RASPBERRYPI
      Plattform: linux
      RAM: 7.7 GB
      Node.js: v16.18.1
      NPM: 8.19.2
      INFO

      Plattform: linux
      Betriebssystem: linux
      Architektur: arm
      CPUs: 4
      Geschwindigkeit: 1800 MHz
      Modell: ARMv7 Processor rev 3 (v7l)
      RAM: 7.7 GB
      System-Betriebszeit: 00:48:51
      Node.js: v16.18.1
      time: 1668776516673
      timeOffset: -60
      Adapter-Anzahl: 537
      NPM: 8.19.2
      Datenträgergröße: 58.3 GB
      Freier Festplattenspeicher: 36.9 GB
      Betriebszeit: 00:48:16
      Aktive Instanzen: 17
      Pfad: /opt/iobroker/

      G 1 Reply Last reply Reply Quote 0
      • G
        guergen @io_laurent last edited by

        @io_laurent Dann würde ich mal den iob stoppen und ein fix drüber laufen lassen, vielleicht fängt er sich ja wieder

        I 1 Reply Last reply Reply Quote 0
        • I
          io_laurent @guergen last edited by

          @guergen hat leider nichts gebracht.

          G 1 Reply Last reply Reply Quote 0
          • G
            guergen @io_laurent last edited by guergen

            @io_laurent Ich gehe dann davon aus, dass die Userrechte im Linux nicht passen...

            Versuch dich mal hiernach ran zu tasten:
            https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten

            Und dann mal

            sudo ln -s /usr/bin/node /usr/bin/nodejs &> /dev/null
            
            uname -m && test -f /opt/scripts/.docker_config/.thisisdocker && echo "Docker-Installation" || echo "Kein Docker" && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && echo $XDG_SESSION_TYPE && echo $DESKTOP_SESSION && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
            

            aufrufen und alles hier posten

            I 1 Reply Last reply Reply Quote 0
            • I
              io_laurent @guergen last edited by

              @guergen

              armv7l
              Kein Docker
              /usr/bin/nodejs
              /usr/bin/node
              /usr/bin/npm
              v16.18.1
              v16.18.1
              8.19.2
              4.0.23
              pi
              pi adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi iobroker
              tty
              
              /home/pi
              Err:1 https://deb.nodesource.com/node_16.x bullseye InRelease                                                                       
                Temporary failure resolving 'deb.nodesource.com'
              Err:2 http://archive.raspberrypi.org/debian bullseye InRelease                                                                      
                Temporary failure resolving 'archive.raspberrypi.org'
              Err:3 https://repos.influxdata.com/debian bullseye InRelease                                                                        
                Temporary failure resolving 'repos.influxdata.com'
              Err:4 https://downloads.plex.tv/repo/deb public InRelease                                                         
                Temporary failure resolving 'downloads.plex.tv'
              Err:5 http://raspbian.raspberrypi.org/raspbian bullseye InRelease            
                Temporary failure resolving 'raspbian.raspberrypi.org'
              Reading package lists... Done              
              Building dependency tree... Done
              Reading state information... Done
              5 packages can be upgraded. Run 'apt list --upgradable' to see them.
              W: Failed to fetch http://raspbian.raspberrypi.org/raspbian/dists/bullseye/InRelease  Temporary failure resolving 'raspbian.raspberrypi.org'
              W: Failed to fetch https://repos.influxdata.com/debian/dists/bullseye/InRelease  Temporary failure resolving 'repos.influxdata.com'
              W: Failed to fetch https://deb.nodesource.com/node_16.x/dists/bullseye/InRelease  Temporary failure resolving 'deb.nodesource.com'
              W: Failed to fetch https://downloads.plex.tv/repo/deb/dists/public/InRelease  Temporary failure resolving 'downloads.plex.tv'
              W: Failed to fetch http://archive.raspberrypi.org/debian/dists/bullseye/InRelease  Temporary failure resolving 'archive.raspberrypi.org'
              W: Some index files failed to download. They have been ignored, or old ones used instead.
              nodejs:
                Installed: 16.18.1-deb-1nodesource1
                Candidate: 16.18.1-deb-1nodesource1
                Version table:
               *** 16.18.1-deb-1nodesource1 500
                      500 https://deb.nodesource.com/node_16.x bullseye/main armhf Packages
                      100 /var/lib/dpkg/status
                   12.22.12~dfsg-1~deb11u1 500
                      500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
              

              Schon mal danke!

              G 1 Reply Last reply Reply Quote 0
              • G
                guergen @io_laurent last edited by

                @io_laurent Der scheint keinen Zugriof auf das Internet zu haben.
                Hast du denn mal versucht ein

                sudo apt update && sudo apt dist-upgrade -y
                

                zu machen?

                I 1 Reply Last reply Reply Quote 0
                • I
                  io_laurent @guergen last edited by

                  @guergen Ja, das sehe ich genauso. Allerdings läuft auf genau diesem Raspi piHole (wie auch zuvor auf dem alten Raspi), welcher alle meine Geräte hier mit Internet versorgt.

                  Err:1 http://archive.raspberrypi.org/debian bullseye InRelease                                                                      
                    Temporary failure resolving 'archive.raspberrypi.org'
                  Err:2 https://repos.influxdata.com/debian bullseye InRelease                                                                        
                    Temporary failure resolving 'repos.influxdata.com'
                  Err:3 https://deb.nodesource.com/node_16.x bullseye InRelease                                                                       
                    Temporary failure resolving 'deb.nodesource.com'
                  Err:4 https://downloads.plex.tv/repo/deb public InRelease                                                       
                    Temporary failure resolving 'downloads.plex.tv'
                  Err:5 http://raspbian.raspberrypi.org/raspbian bullseye InRelease            
                    Temporary failure resolving 'raspbian.raspberrypi.org'
                  Reading package lists... Done              
                  Building dependency tree... Done
                  Reading state information... Done
                  5 packages can be upgraded. Run 'apt list --upgradable' to see them.
                  W: Failed to fetch http://raspbian.raspberrypi.org/raspbian/dists/bullseye/InRelease  Temporary failure resolving 'raspbian.raspberrypi.org'
                  W: Failed to fetch https://repos.influxdata.com/debian/dists/bullseye/InRelease  Temporary failure resolving 'repos.influxdata.com'
                  W: Failed to fetch https://deb.nodesource.com/node_16.x/dists/bullseye/InRelease  Temporary failure resolving 'deb.nodesource.com'
                  W: Failed to fetch https://downloads.plex.tv/repo/deb/dists/public/InRelease  Temporary failure resolving 'downloads.plex.tv'
                  W: Failed to fetch http://archive.raspberrypi.org/debian/dists/bullseye/InRelease  Temporary failure resolving 'archive.raspberrypi.org'
                  W: Some index files failed to download. They have been ignored, or old ones used instead.
                  Reading package lists... Done
                  Building dependency tree... Done
                  Reading state information... Done
                  Calculating upgrade... Done
                  The following packages will be upgraded:
                    firmware-atheros firmware-brcm80211 firmware-libertas firmware-misc-nonfree firmware-realtek
                  5 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
                  Need to get 67.4 MB of archives.
                  After this operation, 61.7 MB of additional disk space will be used.
                  Err:1 http://archive.raspberrypi.org/debian bullseye/main armhf firmware-atheros all 1:20221012-1~bpo11+1+rpt1
                    Temporary failure resolving 'archive.raspberrypi.org'
                  Err:2 http://archive.raspberrypi.org/debian bullseye/main armhf firmware-brcm80211 all 1:20221012-1~bpo11+1+rpt1
                    Temporary failure resolving 'archive.raspberrypi.org'
                  Err:3 http://archive.raspberrypi.org/debian bullseye/main armhf firmware-libertas all 1:20221012-1~bpo11+1+rpt1
                    Temporary failure resolving 'archive.raspberrypi.org'
                  Err:4 http://archive.raspberrypi.org/debian bullseye/main armhf firmware-misc-nonfree all 1:20221012-1~bpo11+1+rpt1
                    Temporary failure resolving 'archive.raspberrypi.org'
                  Err:5 http://archive.raspberrypi.org/debian bullseye/main armhf firmware-realtek all 1:20221012-1~bpo11+1+rpt1
                    Temporary failure resolving 'archive.raspberrypi.org'
                  E: Failed to fetch http://archive.raspberrypi.org/debian/pool/main/f/firmware-nonfree/firmware-atheros_20221012-1%7ebpo11%2b1%2brpt1_all.deb  Temporary failure resolving 'archive.raspberrypi.org'
                  E: Failed to fetch http://archive.raspberrypi.org/debian/pool/main/f/firmware-nonfree/firmware-brcm80211_20221012-1%7ebpo11%2b1%2brpt1_all.deb  Temporary failure resolving 'archive.raspberrypi.org'
                  E: Failed to fetch http://archive.raspberrypi.org/debian/pool/main/f/firmware-nonfree/firmware-libertas_20221012-1%7ebpo11%2b1%2brpt1_all.deb  Temporary failure resolving 'archive.raspberrypi.org'
                  E: Failed to fetch http://archive.raspberrypi.org/debian/pool/main/f/firmware-nonfree/firmware-misc-nonfree_20221012-1%7ebpo11%2b1%2brpt1_all.deb  Temporary failure resolving 'archive.raspberrypi.org'
                  E: Failed to fetch http://archive.raspberrypi.org/debian/pool/main/f/firmware-nonfree/firmware-realtek_20221012-1%7ebpo11%2b1%2brpt1_all.deb  Temporary failure resolving 'archive.raspberrypi.org'
                  E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
                  
                  
                  G mickym 2 Replies Last reply Reply Quote 0
                  • G
                    guergen @io_laurent last edited by

                    @io_laurent Da wird wohl was im PiHole im Argen liegen

                    1 Reply Last reply Reply Quote 0
                    • mickym
                      mickym Most Active @io_laurent last edited by

                      @io_laurent Ich bin mir auch zu 100% sicher, dass es an deinem pi-hole liegt. Ich würde in der Fritz-Box DNS im DHCP erst mal wieder auf sich selbst zeigen lassen, dass Du wieder Internet Zugang hast und dann pi-hole komplett neu installieren.

                      1 Reply Last reply Reply Quote 1
                      • I
                        io_laurent last edited by

                        Es lag an den ipv6 Einstellungen meiner FritzBox, jetzt läuft alles wieder, aber vielen Dank für Tips!

                        G 1 Reply Last reply Reply Quote 0
                        • G
                          guergen @io_laurent last edited by

                          @io_laurent Dan setz oben mal "gelöst" in das Topic

                          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

                          959
                          Online

                          32.3k
                          Users

                          81.1k
                          Topics

                          1.3m
                          Posts

                          cloud internet iot
                          3
                          13
                          626
                          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