Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. [Gelöst] Telegramm –> Bad Gateway

    NEWS

    • Neues Video über Aliase, virtuelle Geräte und Kategorien

    • Wir empfehlen: Node.js 22.x

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    [Gelöst] Telegramm –> Bad Gateway

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

      Hi,

      ich habe seit heute Nacht 3:07 Uhr folgenden Eintrag im Log:

      2018-04-29 03:07:32.894  - [31merror[39m: telegram.0 polling_error:EPARSE, EPARSE: Error parsing response: 
      <title>504 Gateway Time-out</title>
      
      <center>
      
      # 504 Gateway Time-out
      
      </center>
      
      * * *
      
      <center>nginx/1.12.2</center>
      
      

      Adapter restart hilft nicht.

      Adapter Version: 1.2.0

      Hat jemand eine Idee was das sein könnte?

      EDIT: Auch nach Update auf Version 1.2.3 keine Verbesserung. Upgrade lief ohne Fehler durch:````
      $ ./iobroker upgrade telegram
      Update telegram from @1.2.0 to @1.2.3
      host.openmediavault Adapter "system.adapter.telegram.0" is stopped.
      NPM version: 5.7.1
      npm install iobroker.telegram@1.2.3 --production --save --prefix "/opt/iobroker" (System call)
      npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.vis-mywidgets/package.json'

      host.openmediavault Adapter "system.adapter.telegram.0" is started
      npm install --production (System call) in "/opt/iobroker/node_modules/iobroker.telegram"
      npm notice created a lockfile as package-lock.json. You should commit this file.
      got /opt/iobroker/node_modules/iobroker.telegram/admin
      upload [4] telegram.admin /opt/iobroker/node_modules/iobroker.telegram/admin/words.js words.js application/javascript
      Update "system.adapter.telegram.0"
      upload [3] telegram.admin /opt/iobroker/node_modules/iobroker.telegram/admin/telegram.png telegram.png image/png
      upload [2] telegram.admin /opt/iobroker/node_modules/iobroker.telegram/admin/index_m.html index_m.html text/html
      upload [1] telegram.admin /opt/iobroker/node_modules/iobroker.telegram/admin/index.html index.html text/html
      upload [0] telegram.admin /opt/iobroker/node_modules/iobroker.telegram/admin/blockly.js blockly.js application/javascript
      Adapter "telegram" updated
      process exited with code 0

      1 Reply Last reply Reply Quote 0
      • Dutchman
        Dutchman Developer Most Active Administrators last edited by

        Ja, siehe mein Post hier : viewtopic.php?t=13821

        –-----------------------

        Send from mobile device

        Das schöne ios hat Auto Korrektur zum k****

        Wer Schreibfehler findet darf sie behalten oder auf eBay verkaufen, mindest Umsatz 10% für die community

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

          OK.

          Danke für die Info.

          Dann warten wir mal.

          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

          32.0k
          Users

          80.5k
          Topics

          1.3m
          Posts

          2
          3
          554
          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