Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Einsteigerfragen
  4. Webinterface nicht mehr aufrufbar

NEWS

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    17
    1
    3.9k

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    1.2k

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    25
    1
    2.5k

Webinterface nicht mehr aufrufbar

Geplant Angeheftet Gesperrt Verschoben Einsteigerfragen
16 Beiträge 3 Kommentatoren 866 Aufrufe 2 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • G GiB64

    @thomas-braun Danke aber ganz blöde Frage, wie mache ich das? Hatte gedacht das es mit

    sudo apt update && sudo apt upgrade
    

    erledigt ist aber leider nicht. Auch die Hilfe bei Influx hat mir nicht wirklich weiter geholfen...

    Thomas BraunT Online
    Thomas BraunT Online
    Thomas Braun
    Most Active
    schrieb am zuletzt editiert von
    #6

    @gib64

    Aus dem August:
    https://forum.iobroker.net/topic/67822/grafana-repo-braucht-neuen-schlüssel

    Aus dem Januar:
    https://forum.iobroker.net/topic/62040/linux-debian-grafana-repo-muss-aktualisiert-werden

    Solange hängt das also schon schief bei dir...

    Linux-Werkzeugkasten:
    https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
    NodeJS Fixer Skript:
    https://forum.iobroker.net/topic/68035/iob-node-fix-skript
    iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

    G 1 Antwort Letzte Antwort
    0
    • Thomas BraunT Thomas Braun

      @gib64

      Aus dem August:
      https://forum.iobroker.net/topic/67822/grafana-repo-braucht-neuen-schlüssel

      Aus dem Januar:
      https://forum.iobroker.net/topic/62040/linux-debian-grafana-repo-muss-aktualisiert-werden

      Solange hängt das also schon schief bei dir...

      G Offline
      G Offline
      GiB64
      schrieb am zuletzt editiert von
      #7

      @thomas-braun Mag sein, mir fehlt noch ein wenig der Überblich als Windowsuser... Ich hatte es so wie von Dir beschrieben gemacht und

      apt-key list | grep -i grafana | wc -l
      

      ergab die gewünschte 0:

      pi@raspberry64:~ $ apt-key list | grep -i grafana | wc -l
      Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
      0
      pi@raspberry64:~ $ sudo wget -q -O /usr/share/keyrings/grafana.key https://apt.grafana.com/gpg.key
      pi@raspberry64:~ $ echo "deb [signed-by=/usr/share/keyrings/grafana.key] https://apt.grafana.com stable main" | sudo tee /etc/apt/sources.list.d/grafana.list
      deb [signed-by=/usr/share/keyrings/grafana.key] https://apt.grafana.com stable main
      pi@raspberry64:~ $ sudo apt update
      Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
      Hit:2 http://deb.debian.org/debian bullseye InRelease
      Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
      Get:4 https://deb.nodesource.com/node_16.x bullseye InRelease [4,586 B]
      Get:5 https://repos.influxdata.com/debian bullseye InRelease [7,040 B]
      Get:6 https://apt.grafana.com stable InRelease [5,983 B]
      Hit:7 http://archive.raspberrypi.org/debian bullseye InRelease
      Err:5 https://repos.influxdata.com/debian bullseye InRelease
        The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
      Get:8 https://apt.grafana.com stable/main arm64 Packages [112 kB]
      Get:9 https://apt.grafana.com stable/main armhf Packages [96.5 kB]
      Fetched 220 kB in 2s (113 kB/s)
      Reading package lists... Done
      Building dependency tree... Done
      Reading state information... Done
      1 package can be upgraded. Run 'apt list --upgradable' to see it.
      W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repos.influxdata.com/debian bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
      W: Failed to fetch https://repos.influxdata.com/debian/dists/bullseye/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
      W: Some index files failed to download. They have been ignored, or old ones used instead.
      
      

      da das update dann immer noch Fehler zeigte wollte ich dann den Key löschen und neu anlegen. Leider habe ich dann den falschen gelöscht.

      Wie kann ich diesen denn wieder herstellen oder ist der nicht wichtig?: :cold_sweat:

      /etc/apt/trusted.gpg.d/raspberrypi-archive-stable.gpg
      -----------------------------------------------------
      pub   rsa2048 2012-06-17 [SC]
            CF8A 1AF5 02A2 AA2D 763B  AE7E 82B1 2992 7FA3 303E
      uid           [ unknown] Raspberry Pi Archive Signing Key
      sub   rsa2048 2012-06-17 [E]
      
      
      Thomas BraunT 1 Antwort Letzte Antwort
      0
      • G GiB64

        @thomas-braun Mag sein, mir fehlt noch ein wenig der Überblich als Windowsuser... Ich hatte es so wie von Dir beschrieben gemacht und

        apt-key list | grep -i grafana | wc -l
        

        ergab die gewünschte 0:

        pi@raspberry64:~ $ apt-key list | grep -i grafana | wc -l
        Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
        0
        pi@raspberry64:~ $ sudo wget -q -O /usr/share/keyrings/grafana.key https://apt.grafana.com/gpg.key
        pi@raspberry64:~ $ echo "deb [signed-by=/usr/share/keyrings/grafana.key] https://apt.grafana.com stable main" | sudo tee /etc/apt/sources.list.d/grafana.list
        deb [signed-by=/usr/share/keyrings/grafana.key] https://apt.grafana.com stable main
        pi@raspberry64:~ $ sudo apt update
        Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
        Hit:2 http://deb.debian.org/debian bullseye InRelease
        Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
        Get:4 https://deb.nodesource.com/node_16.x bullseye InRelease [4,586 B]
        Get:5 https://repos.influxdata.com/debian bullseye InRelease [7,040 B]
        Get:6 https://apt.grafana.com stable InRelease [5,983 B]
        Hit:7 http://archive.raspberrypi.org/debian bullseye InRelease
        Err:5 https://repos.influxdata.com/debian bullseye InRelease
          The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
        Get:8 https://apt.grafana.com stable/main arm64 Packages [112 kB]
        Get:9 https://apt.grafana.com stable/main armhf Packages [96.5 kB]
        Fetched 220 kB in 2s (113 kB/s)
        Reading package lists... Done
        Building dependency tree... Done
        Reading state information... Done
        1 package can be upgraded. Run 'apt list --upgradable' to see it.
        W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repos.influxdata.com/debian bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
        W: Failed to fetch https://repos.influxdata.com/debian/dists/bullseye/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
        W: Some index files failed to download. They have been ignored, or old ones used instead.
        
        

        da das update dann immer noch Fehler zeigte wollte ich dann den Key löschen und neu anlegen. Leider habe ich dann den falschen gelöscht.

        Wie kann ich diesen denn wieder herstellen oder ist der nicht wichtig?: :cold_sweat:

        /etc/apt/trusted.gpg.d/raspberrypi-archive-stable.gpg
        -----------------------------------------------------
        pub   rsa2048 2012-06-17 [SC]
              CF8A 1AF5 02A2 AA2D 763B  AE7E 82B1 2992 7FA3 303E
        uid           [ unknown] Raspberry Pi Archive Signing Key
        sub   rsa2048 2012-06-17 [E]
        
        
        Thomas BraunT Online
        Thomas BraunT Online
        Thomas Braun
        Most Active
        schrieb am zuletzt editiert von Thomas Braun
        #8

        @gib64

        apt-key list | grep -i grafana | wc -l
        sudo wget -q -O /usr/share/keyrings/grafana.key https://apt.grafana.com/gpg.key
        

        sagt?

        €dit: Grafana ist doch okay nun. Da ist aber noch die zweite Baustelle bei influxdb. Dazu steht im Thread aus dem Januar aber was drin.

        Linux-Werkzeugkasten:
        https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
        NodeJS Fixer Skript:
        https://forum.iobroker.net/topic/68035/iob-node-fix-skript
        iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

        G 1 Antwort Letzte Antwort
        0
        • Thomas BraunT Thomas Braun

          @gib64

          apt-key list | grep -i grafana | wc -l
          sudo wget -q -O /usr/share/keyrings/grafana.key https://apt.grafana.com/gpg.key
          

          sagt?

          €dit: Grafana ist doch okay nun. Da ist aber noch die zweite Baustelle bei influxdb. Dazu steht im Thread aus dem Januar aber was drin.

          G Offline
          G Offline
          GiB64
          schrieb am zuletzt editiert von
          #9

          @thomas-braun Der ausversehen gelöscht Raspberrypi-Key scheint doch wichtig zu sein. Nachdem ich den Influx Key erneuert habe kommt:

          pi@raspberry64:~ $ sudo apt update
          Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
          Hit:2 http://deb.debian.org/debian bullseye InRelease
          Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
          Get:4 https://repos.influxdata.com/debian bullseye InRelease [7,040 B]
          Get:5 https://deb.nodesource.com/node_16.x bullseye InRelease [4,586 B]
          Hit:6 http://archive.raspberrypi.org/debian bullseye InRelease
          Err:4 https://repos.influxdata.com/debian bullseye InRelease
            The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
          Err:6 http://archive.raspberrypi.org/debian bullseye InRelease
            The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 82B129927FA3303E
          Fetched 11.6 kB in 1s (7,993 B/s)
          Reading package lists... Done
          Building dependency tree... Done
          Reading state information... Done
          All packages are up to date.
          W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repos.influxdata.com/debian bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
          W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://archive.raspberrypi.org/debian bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 82B129927FA3303E
          W: Failed to fetch https://repos.influxdata.com/debian/dists/bullseye/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
          W: Failed to fetch http://archive.raspberrypi.org/debian/dists/bullseye/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 82B129927FA3303E
          W: Some index files failed to download. They have been ignored, or old ones used instead.
          
          
          Thomas BraunT 1 Antwort Letzte Antwort
          0
          • G GiB64

            @thomas-braun Der ausversehen gelöscht Raspberrypi-Key scheint doch wichtig zu sein. Nachdem ich den Influx Key erneuert habe kommt:

            pi@raspberry64:~ $ sudo apt update
            Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
            Hit:2 http://deb.debian.org/debian bullseye InRelease
            Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
            Get:4 https://repos.influxdata.com/debian bullseye InRelease [7,040 B]
            Get:5 https://deb.nodesource.com/node_16.x bullseye InRelease [4,586 B]
            Hit:6 http://archive.raspberrypi.org/debian bullseye InRelease
            Err:4 https://repos.influxdata.com/debian bullseye InRelease
              The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
            Err:6 http://archive.raspberrypi.org/debian bullseye InRelease
              The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 82B129927FA3303E
            Fetched 11.6 kB in 1s (7,993 B/s)
            Reading package lists... Done
            Building dependency tree... Done
            Reading state information... Done
            All packages are up to date.
            W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repos.influxdata.com/debian bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
            W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://archive.raspberrypi.org/debian bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 82B129927FA3303E
            W: Failed to fetch https://repos.influxdata.com/debian/dists/bullseye/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
            W: Failed to fetch http://archive.raspberrypi.org/debian/dists/bullseye/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 82B129927FA3303E
            W: Some index files failed to download. They have been ignored, or old ones used instead.
            
            
            Thomas BraunT Online
            Thomas BraunT Online
            Thomas Braun
            Most Active
            schrieb am zuletzt editiert von
            #10

            @gib64 sagte in Webinterface nicht mehr aufrufbar:

            82B129927FA3303E

            wget http://archive.raspberrypi.org/debian/raspberrypi.gpg.key
            sudo apt-key add raspberrypi.gpg.key
            rm raspberrypi.gpg.key
            

            Linux-Werkzeugkasten:
            https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
            NodeJS Fixer Skript:
            https://forum.iobroker.net/topic/68035/iob-node-fix-skript
            iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

            G 1 Antwort Letzte Antwort
            0
            • Thomas BraunT Thomas Braun

              @gib64 sagte in Webinterface nicht mehr aufrufbar:

              82B129927FA3303E

              wget http://archive.raspberrypi.org/debian/raspberrypi.gpg.key
              sudo apt-key add raspberrypi.gpg.key
              rm raspberrypi.gpg.key
              
              G Offline
              G Offline
              GiB64
              schrieb am zuletzt editiert von GiB64
              #11

              @thomas-braun Danke lief fehlerfrei durch aber ich bekomme immer noch Influx angemeckert obwohl ich den Key erneuert hatte:

              pi@raspberry64:~ $ sudo apt update
              Hit:1 http://archive.raspberrypi.org/debian bullseye InRelease
              Hit:2 http://deb.debian.org/debian bullseye InRelease
              Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
              Hit:4 http://security.debian.org/debian-security bullseye-security InRelease
              Get:5 https://deb.nodesource.com/node_16.x bullseye InRelease [4,586 B]
              Get:6 https://repos.influxdata.com/debian bullseye InRelease [7,040 B]
              Err:6 https://repos.influxdata.com/debian bullseye InRelease
                The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
              Fetched 11.6 kB in 2s (7,264 B/s)
              Reading package lists... Done
              Building dependency tree... Done
              Reading state information... Done
              All packages are up to date.
              W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repos.influxdata.com/debian bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
              W: Failed to fetch https://repos.influxdata.com/debian/dists/bullseye/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
              W: Some index files failed to download. They have been ignored, or old ones used instead.
              pi@raspberry64:~ $
              
              

              Edit: kann es sein das beim Import was schief gelaufen ist?:

              pi@raspberry64:~ $ apt-key list
              Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
              /etc/apt/trusted.gpg
              --------------------
              pub   rsa2048 2012-06-17 [SC]
                    CF8A 1AF5 02A2 AA2D 763B  AE7E 82B1 2992 7FA3 303E
              uid           [ unknown] Raspberry Pi Archive Signing Key
              sub   rsa2048 2012-06-17 [E]
              
              /etc/apt/trusted.gpg.d/debian-archive-bookworm-automatic.gpg
              ------------------------------------------------------------
              pub   rsa4096 2023-01-21 [SC] [expires: 2031-01-19]
                    B8B8 0B5B 623E AB6A D877  5C45 B7C5 D7D6 3509 47F8
              uid           [ unknown] Debian Archive Automatic Signing Key (12/bookworm) <ftpmaster@debian.org>
              sub   rsa4096 2023-01-21 [S] [expires: 2031-01-19]
              
              /etc/apt/trusted.gpg.d/debian-archive-bookworm-security-automatic.gpg
              ---------------------------------------------------------------------
              pub   rsa4096 2023-01-21 [SC] [expires: 2031-01-19]
                    05AB 9034 0C0C 5E79 7F44  A8C8 254C F3B5 AEC0 A8F0
              uid           [ unknown] Debian Security Archive Automatic Signing Key (12/bookworm) <ftpmaster@debian.org>
              sub   rsa4096 2023-01-21 [S] [expires: 2031-01-19]
              
              /etc/apt/trusted.gpg.d/debian-archive-bookworm-stable.gpg
              ---------------------------------------------------------
              pub   ed25519 2023-01-23 [SC] [expires: 2031-01-21]
                    4D64 FEC1 19C2 0290 67D6  E791 F8D2 585B 8783 D481
              uid           [ unknown] Debian Stable Release Key (12/bookworm) <debian-release@lists.debian.org>
              
              /etc/apt/trusted.gpg.d/debian-archive-bullseye-automatic.gpg
              ------------------------------------------------------------
              pub   rsa4096 2021-01-17 [SC] [expires: 2029-01-15]
                    1F89 983E 0081 FDE0 18F3  CC96 73A4 F27B 8DD4 7936
              uid           [ unknown] Debian Archive Automatic Signing Key (11/bullseye) <ftpmaster@debian.org>
              sub   rsa4096 2021-01-17 [S] [expires: 2029-01-15]
              
              /etc/apt/trusted.gpg.d/debian-archive-bullseye-security-automatic.gpg
              ---------------------------------------------------------------------
              pub   rsa4096 2021-01-17 [SC] [expires: 2029-01-15]
                    AC53 0D52 0F2F 3269 F5E9  8313 A484 4904 4AAD 5C5D
              uid           [ unknown] Debian Security Archive Automatic Signing Key (11/bullseye) <ftpmaster@debian.org>
              sub   rsa4096 2021-01-17 [S] [expires: 2029-01-15]
              
              /etc/apt/trusted.gpg.d/debian-archive-bullseye-stable.gpg
              ---------------------------------------------------------
              pub   rsa4096 2021-02-13 [SC] [expires: 2029-02-11]
                    A428 5295 FC7B 1A81 6000  62A9 605C 66F0 0D6C 9793
              uid           [ unknown] Debian Stable Release Key (11/bullseye) <debian-release@lists.debian.org>
              
              /etc/apt/trusted.gpg.d/debian-archive-buster-automatic.gpg
              ----------------------------------------------------------
              pub   rsa4096 2019-04-14 [SC] [expires: 2027-04-12]
                    80D1 5823 B7FD 1561 F9F7  BCDD DC30 D7C2 3CBB ABEE
              uid           [ unknown] Debian Archive Automatic Signing Key (10/buster) <ftpmaster@debian.org>
              sub   rsa4096 2019-04-14 [S] [expires: 2027-04-12]
              
              /etc/apt/trusted.gpg.d/debian-archive-buster-security-automatic.gpg
              -------------------------------------------------------------------
              pub   rsa4096 2019-04-14 [SC] [expires: 2027-04-12]
                    5E61 B217 265D A980 7A23  C5FF 4DFA B270 CAA9 6DFA
              uid           [ unknown] Debian Security Archive Automatic Signing Key (10/buster) <ftpmaster@debian.org>
              sub   rsa4096 2019-04-14 [S] [expires: 2027-04-12]
              
              /etc/apt/trusted.gpg.d/debian-archive-buster-stable.gpg
              -------------------------------------------------------
              pub   rsa4096 2019-02-05 [SC] [expires: 2027-02-03]
                    6D33 866E DD8F FA41 C014  3AED DCC9 EFBF 77E1 1517
              uid           [ unknown] Debian Stable Release Key (10/buster) <debian-release@lists.debian.org>
              
              pi@raspberry64:~ $
              
              
              Thomas BraunT 1 Antwort Letzte Antwort
              0
              • G GiB64

                @thomas-braun Danke lief fehlerfrei durch aber ich bekomme immer noch Influx angemeckert obwohl ich den Key erneuert hatte:

                pi@raspberry64:~ $ sudo apt update
                Hit:1 http://archive.raspberrypi.org/debian bullseye InRelease
                Hit:2 http://deb.debian.org/debian bullseye InRelease
                Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
                Hit:4 http://security.debian.org/debian-security bullseye-security InRelease
                Get:5 https://deb.nodesource.com/node_16.x bullseye InRelease [4,586 B]
                Get:6 https://repos.influxdata.com/debian bullseye InRelease [7,040 B]
                Err:6 https://repos.influxdata.com/debian bullseye InRelease
                  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
                Fetched 11.6 kB in 2s (7,264 B/s)
                Reading package lists... Done
                Building dependency tree... Done
                Reading state information... Done
                All packages are up to date.
                W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repos.influxdata.com/debian bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
                W: Failed to fetch https://repos.influxdata.com/debian/dists/bullseye/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
                W: Some index files failed to download. They have been ignored, or old ones used instead.
                pi@raspberry64:~ $
                
                

                Edit: kann es sein das beim Import was schief gelaufen ist?:

                pi@raspberry64:~ $ apt-key list
                Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
                /etc/apt/trusted.gpg
                --------------------
                pub   rsa2048 2012-06-17 [SC]
                      CF8A 1AF5 02A2 AA2D 763B  AE7E 82B1 2992 7FA3 303E
                uid           [ unknown] Raspberry Pi Archive Signing Key
                sub   rsa2048 2012-06-17 [E]
                
                /etc/apt/trusted.gpg.d/debian-archive-bookworm-automatic.gpg
                ------------------------------------------------------------
                pub   rsa4096 2023-01-21 [SC] [expires: 2031-01-19]
                      B8B8 0B5B 623E AB6A D877  5C45 B7C5 D7D6 3509 47F8
                uid           [ unknown] Debian Archive Automatic Signing Key (12/bookworm) <ftpmaster@debian.org>
                sub   rsa4096 2023-01-21 [S] [expires: 2031-01-19]
                
                /etc/apt/trusted.gpg.d/debian-archive-bookworm-security-automatic.gpg
                ---------------------------------------------------------------------
                pub   rsa4096 2023-01-21 [SC] [expires: 2031-01-19]
                      05AB 9034 0C0C 5E79 7F44  A8C8 254C F3B5 AEC0 A8F0
                uid           [ unknown] Debian Security Archive Automatic Signing Key (12/bookworm) <ftpmaster@debian.org>
                sub   rsa4096 2023-01-21 [S] [expires: 2031-01-19]
                
                /etc/apt/trusted.gpg.d/debian-archive-bookworm-stable.gpg
                ---------------------------------------------------------
                pub   ed25519 2023-01-23 [SC] [expires: 2031-01-21]
                      4D64 FEC1 19C2 0290 67D6  E791 F8D2 585B 8783 D481
                uid           [ unknown] Debian Stable Release Key (12/bookworm) <debian-release@lists.debian.org>
                
                /etc/apt/trusted.gpg.d/debian-archive-bullseye-automatic.gpg
                ------------------------------------------------------------
                pub   rsa4096 2021-01-17 [SC] [expires: 2029-01-15]
                      1F89 983E 0081 FDE0 18F3  CC96 73A4 F27B 8DD4 7936
                uid           [ unknown] Debian Archive Automatic Signing Key (11/bullseye) <ftpmaster@debian.org>
                sub   rsa4096 2021-01-17 [S] [expires: 2029-01-15]
                
                /etc/apt/trusted.gpg.d/debian-archive-bullseye-security-automatic.gpg
                ---------------------------------------------------------------------
                pub   rsa4096 2021-01-17 [SC] [expires: 2029-01-15]
                      AC53 0D52 0F2F 3269 F5E9  8313 A484 4904 4AAD 5C5D
                uid           [ unknown] Debian Security Archive Automatic Signing Key (11/bullseye) <ftpmaster@debian.org>
                sub   rsa4096 2021-01-17 [S] [expires: 2029-01-15]
                
                /etc/apt/trusted.gpg.d/debian-archive-bullseye-stable.gpg
                ---------------------------------------------------------
                pub   rsa4096 2021-02-13 [SC] [expires: 2029-02-11]
                      A428 5295 FC7B 1A81 6000  62A9 605C 66F0 0D6C 9793
                uid           [ unknown] Debian Stable Release Key (11/bullseye) <debian-release@lists.debian.org>
                
                /etc/apt/trusted.gpg.d/debian-archive-buster-automatic.gpg
                ----------------------------------------------------------
                pub   rsa4096 2019-04-14 [SC] [expires: 2027-04-12]
                      80D1 5823 B7FD 1561 F9F7  BCDD DC30 D7C2 3CBB ABEE
                uid           [ unknown] Debian Archive Automatic Signing Key (10/buster) <ftpmaster@debian.org>
                sub   rsa4096 2019-04-14 [S] [expires: 2027-04-12]
                
                /etc/apt/trusted.gpg.d/debian-archive-buster-security-automatic.gpg
                -------------------------------------------------------------------
                pub   rsa4096 2019-04-14 [SC] [expires: 2027-04-12]
                      5E61 B217 265D A980 7A23  C5FF 4DFA B270 CAA9 6DFA
                uid           [ unknown] Debian Security Archive Automatic Signing Key (10/buster) <ftpmaster@debian.org>
                sub   rsa4096 2019-04-14 [S] [expires: 2027-04-12]
                
                /etc/apt/trusted.gpg.d/debian-archive-buster-stable.gpg
                -------------------------------------------------------
                pub   rsa4096 2019-02-05 [SC] [expires: 2027-02-03]
                      6D33 866E DD8F FA41 C014  3AED DCC9 EFBF 77E1 1517
                uid           [ unknown] Debian Stable Release Key (10/buster) <debian-release@lists.debian.org>
                
                pi@raspberry64:~ $
                
                
                Thomas BraunT Online
                Thomas BraunT Online
                Thomas Braun
                Most Active
                schrieb am zuletzt editiert von
                #12

                @gib64 sagte in Webinterface nicht mehr aufrufbar:

                Edit: kann es sein das beim Import was schief gelaufen ist?:

                Nein, die Pakete sind mehrfach signiert.

                Zu influx:

                ls -lAh /etc/apt/sources.list.d/
                

                sagt? Ich vermute da liegen zwei Dateien mit Bezug zu influx drin.

                Linux-Werkzeugkasten:
                https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                NodeJS Fixer Skript:
                https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                G 1 Antwort Letzte Antwort
                0
                • Thomas BraunT Thomas Braun

                  @gib64 sagte in Webinterface nicht mehr aufrufbar:

                  Edit: kann es sein das beim Import was schief gelaufen ist?:

                  Nein, die Pakete sind mehrfach signiert.

                  Zu influx:

                  ls -lAh /etc/apt/sources.list.d/
                  

                  sagt? Ich vermute da liegen zwei Dateien mit Bezug zu influx drin.

                  G Offline
                  G Offline
                  GiB64
                  schrieb am zuletzt editiert von
                  #13

                  @thomas-braun said in Webinterface nicht mehr aufrufbar:

                  ls -lAh /etc/apt/sources.list.d/

                  pi@raspberry64:~ $ ls -lAh /etc/apt/sources.list.d/
                  total 12K
                  -rw-r--r-- 1 root root   0 Oct  5 15:19 grafana.list
                  -rw-r--r-- 1 root root 101 Oct  5 15:27 influxdb.list
                  -rw-r--r-- 1 root root 208 Dec  1  2022 nodesource.list
                  -rw-r--r-- 1 root root 191 Sep 22  2022 raspi.list
                  pi@raspberry64:~ $
                  
                  
                  Thomas BraunT 1 Antwort Letzte Antwort
                  0
                  • G GiB64

                    @thomas-braun said in Webinterface nicht mehr aufrufbar:

                    ls -lAh /etc/apt/sources.list.d/

                    pi@raspberry64:~ $ ls -lAh /etc/apt/sources.list.d/
                    total 12K
                    -rw-r--r-- 1 root root   0 Oct  5 15:19 grafana.list
                    -rw-r--r-- 1 root root 101 Oct  5 15:27 influxdb.list
                    -rw-r--r-- 1 root root 208 Dec  1  2022 nodesource.list
                    -rw-r--r-- 1 root root 191 Sep 22  2022 raspi.list
                    pi@raspberry64:~ $
                    
                    
                    Thomas BraunT Online
                    Thomas BraunT Online
                    Thomas Braun
                    Most Active
                    schrieb am zuletzt editiert von Thomas Braun
                    #14

                    @gib64

                    sudo rm /etc/apt/sources.list.d/influxdb.list
                    wget -q https://repos.influxdata.com/influxdata-archive_compat.key
                    
                    echo '393e8779c89ac8d958f81f942f9ad7fb82a25e133faddaf92e15b16e6ac9ce4c influxdata-archive_compat.key' | sha256sum -c && cat influxdata-archive_compat.key | gpg --dearmor | sudo tee /usr/share/keyrings/influxdata-archive_compat.gpg > /dev/null
                    
                    echo 'deb [signed-by=/usr/share/keyrings/influxdata-archive_compat.gpg] https://repos.influxdata.com/debian stable main' | sudo tee /etc/apt/sources.list.d/influxdata.list
                    
                    rm influxdata-archive_compat.key
                    

                    Dann nochmal

                    sudo apt update
                    

                    Linux-Werkzeugkasten:
                    https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                    NodeJS Fixer Skript:
                    https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                    iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                    1 Antwort Letzte Antwort
                    0
                    • G Offline
                      G Offline
                      GiB64
                      schrieb am zuletzt editiert von
                      #15

                      @thomas-braun Vielen Dank! Jetzt ist alles auf Stand ohne Fehler. Aber mal ehrlich, wie hätte ich da als Windows User drauf kommen sollen?

                      Thomas BraunT 1 Antwort Letzte Antwort
                      0
                      • G GiB64

                        @thomas-braun Vielen Dank! Jetzt ist alles auf Stand ohne Fehler. Aber mal ehrlich, wie hätte ich da als Windows User drauf kommen sollen?

                        Thomas BraunT Online
                        Thomas BraunT Online
                        Thomas Braun
                        Most Active
                        schrieb am zuletzt editiert von
                        #16

                        @gib64 sagte in Webinterface nicht mehr aufrufbar:

                        Aber mal ehrlich, wie hätte ich da als Windows User drauf kommen sollen?

                        Lesen bildet. Linux und Debian ist sehr gut dokumentiert.

                        Linux-Werkzeugkasten:
                        https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                        NodeJS Fixer Skript:
                        https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                        iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                        1 Antwort Letzte Antwort
                        0
                        Antworten
                        • In einem neuen Thema antworten
                        Anmelden zum Antworten
                        • Älteste zuerst
                        • Neuste zuerst
                        • Meiste Stimmen


                        Support us

                        ioBroker
                        Community Adapters
                        Donate

                        593

                        Online

                        32.7k

                        Benutzer

                        82.4k

                        Themen

                        1.3m

                        Beiträge
                        Community
                        Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                        ioBroker Community 2014-2025
                        logo
                        • Anmelden

                        • Du hast noch kein Konto? Registrieren

                        • Anmelden oder registrieren, um zu suchen
                        • Erster Beitrag
                          Letzter Beitrag
                        0
                        • Home
                        • Aktuell
                        • Tags
                        • Ungelesen 0
                        • Kategorien
                        • Unreplied
                        • Beliebt
                        • GitHub
                        • Docu
                        • Hilfe