error; Reverse Proxy replied with neither registered nor unregistered status

Begonnen von erdnar, 29 Dezember 2024, 14:09:22

Vorheriges Thema - Nächstes Thema

erdnar

Hallo und da ich gelernt habe, das Weihnachten vom 25.12. bis 6.1. geht, allen frohe Weihnachten  ;D

Ich habe seit heute einen Fehler, den ich vor 4 Jahren schon mal hatte:error; Reverse Proxy replied with neither registered nor unregistered status: out:  err:ssh: Could not resolve hostname fhem-va.fhem.de: Name or service not knownDamals konnte ich alexa einfach neu starten, das geht nun leider nicht.
Im LOG erkennt man, dass alexa um 9:34Uhr noch reagiert hat, aber dann (aus meiner Sicht) 11:57Uhr nicht mehr wollte...
2024-12-29 09:31:34 caching: Heizung__sz_Wand-temperature: 14.8
[29.12.2024, 09:31:34] [FHEM]     caching: CurrentTemperature: 14.8 (as number; from '14.8')
  2024-12-29 09:31:52 caching: Heizung__pz_Wand-temperature: 18.0
[29.12.2024, 09:31:52] [FHEM]     caching: CurrentTemperature: 18 (as number; from '18.0')
[29.12.2024, 09:34:14] >>>> [ssh] {"directive":{"header":{"messageId":"9d20e328-57e0-48d9-8c11-bba2e35f91bc","namespace":"Alexa.PowerController","name":"TurnOn","payloadVersion":"3","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"76810315-C5D6BA19075F5F4E"},"endpointId":"650b1e80-f33f-50f1-1b85-9b099252acb8695f","cookie":{"device":"D_curt_Schreibtisch_dummy","fuuid":"650b1e80-f33f-50f1-1b85-9b099252acb8695f"}},"payload":{}}}
[29.12.2024, 09:34:14] [FHEM] D_curt_Schreibtisch_dummy: executing set cmd for On with value 1
[29.12.2024, 09:34:14] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=set%20D_curt_Schreibtisch_dummy%20on&fwcsrf=csrf_464230115418499&XHR=1
[29.12.2024, 09:34:14] <<<< [ssh] {"context":{"properties":[{"namespace":"Alexa.PowerController","name":"powerState","value":"ON","timeOfSample":"2024-12-29T08:34:14.783Z","uncertaintyInMilliseconds":500}]},"event":{"header":{"namespace":"Alexa","name":"Response","payloadVersion":"3","messageId":"97e740cb-60e1-4ba6-a751-708cd2f7f846","correlationToken":"-"},"endpoint":{"scope":{"type":"BearerToken","token":"76810315-C5D6BA19075F5F4E"},"endpointId":"650b1e80-f33f-50f1-1b85-9b099252acb8695f"},"payload":{}}}
  2024-12-29 09:34:15 caching: D_curt_Schreibtisch_dummy-state: ON
[29.12.2024, 09:34:15] [FHEM]     caching: On: 1 (as number; from 'ON')
  2024-12-29 09:34:16 caching: MQ2gos185-state: on
[29.12.2024, 09:34:16] [FHEM]     caching: On: 1 (as number; from 'on')
  2024-12-29 09:34:16 caching: MQ2gos242-state: on
[29.12.2024, 09:34:16] [FHEM]     caching: On: 1 (as number; from 'on')

>snipp<

  2024-12-29 11:55:07 caching: HUEDevice2-onoff: 0
[29.12.2024, 11:55:07] [FHEM]     caching: On: 0 (as number; from '0')
  2024-12-29 11:55:15 caching: Heizung__az-temperature: 20.6
[29.12.2024, 11:55:15] [FHEM]     caching: CurrentTemperature: 20.6 (as number; from '20.6')
  2024-12-29 11:55:15 caching: Heizung__az-valveposition: 29
[29.12.2024, 11:55:15] [FHEM]     caching: Custom Actuation: 29 (as number; from '29')
  2024-12-29 11:56:23 caching: HUEDevice2-onoff: 1
[29.12.2024, 11:56:23] [FHEM]     caching: On: 1 (as number; from '1')
  2024-12-29 11:56:36 caching: Heizung_fs_fl-measured-temp: 21.0
[29.12.2024, 11:56:36] [FHEM]     caching: CurrentTemperature: 21 (as number; from '21.0')
  2024-12-29 11:56:59 caching: Heizung__cz_Wand-temperature: 21.1
[29.12.2024, 11:56:59] [FHEM]     caching: CurrentTemperature: 21.1 (as number; from '21.1')
  2024-12-29 11:57:15 caching: Heizung__wz_Wand-temperature: 21.1
[29.12.2024, 11:57:15] [FHEM]     caching: CurrentTemperature: 21.1 (as number; from '21.1')
[29.12.2024, 11:57:24] Got SIGTERM, shutting down alexa-fhem...
[29.12.2024, 11:57:24] Reading alexaFHEM.ProxyConnection set to stopping;; alexa-fhem terminating
[29.12.2024, 11:57:24] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20stopping%3B%3B%20alexa-fhem%20terminating%3B%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_464230115418499&XHR=1
[29.12.2024, 11:57:24] Stopping SSH ...
[29.12.2024, 11:57:24] Reading alexaFHEM.ProxyConnection set to stopped
[29.12.2024, 11:57:24] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20stopped%3B%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_464230115418499&XHR=1
[29.12.2024, 11:57:24] *** SSH: exited with 0
  2024-12-29 11:57:24 caching: HUEDevice65541-reachable: 0
[29.12.2024, 11:57:24] [FHEM]     caching: Reachable: false (as boolean; from '0')
  2024-12-29 11:57:24 caching: HUEDevice65546-reachable: 0
[29.12.2024, 11:57:24] [FHEM]     caching: Reachable: false (as boolean; from '0')
[29.12.2024, 11:58:20] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[29.12.2024, 11:58:20] os.homedir()=/opt/fhem
[29.12.2024, 11:58:20] this is alexa-fhem 0.5.61
[29.12.2024, 11:58:20] connecting to FHEM ...
[29.12.2024, 11:58:20] [FHEM] defaults to: will not send proactive events
[29.12.2024, 11:58:21] [FHEM] trying longpoll to listen for fhem events
[29.12.2024, 11:58:21] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1735469901484
[29.12.2024, 11:58:34] [FHEM] got csrfToken: csrf_51835216842232
[29.12.2024, 11:58:34] [FHEM] Checking devices and attributes...
[29.12.2024, 11:58:34] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&fwcsrf=csrf_51835216842232&XHR=1
[29.12.2024, 11:58:34] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&fwcsrf=csrf_51835216842232&XHR=1
[29.12.2024, 11:58:34] [FHEM] waiting for events ...
[29.12.2024, 11:58:34] [FHEM] Fetching FHEM devices...
[29.12.2024, 11:58:34] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName%3D..*&fwcsrf=csrf_51835216842232&XHR=1
[29.12.2024, 11:58:45] [FHEM] alexa device is alexa
[29.12.2024, 11:58:45] [FHEM] alexa will not send proactive events
[29.12.2024, 11:58:45] [FHEM] alexa uses ID: 5d4727a8-f33f-50f1-bb36-d4876e229aa5da04
[29.12.2024, 11:58:45] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7B%24defs%7B%22alexa%22%7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.61%22%7D%3B%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_51835216842232&XHR=1
[29.12.2024, 11:58:45] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bget%20alexa%20proxyToken%3B%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_51835216842232&XHR=1
[29.12.2024, 11:58:45] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Blist%20alexa%20.eventToken%3B%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_51835216842232&XHR=1
[29.12.2024, 11:58:45] Server listening on: http://127.0.0.1:43127 for proxy connections
[29.12.2024, 11:58:45] *** SSH: checking proxy configuration
[29.12.2024, 11:58:45] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[29.12.2024, 11:58:45] Passed config: {
  sshproxy: {
    ssh: '/usr/bin/ssh',
    description: 'FHEM Connector',
    options: [ '-i', '/opt/fhem/.ssh/id_rsa', '-p', 58824, 'fhem-va.fhem.de' ],
    'bind-ip': '127.0.0.1',
    server: Server {
      maxHeaderSize: undefined,
      insecureHTTPParser: undefined,
      _events: [Object: null prototype],
      _eventsCount: 3,
      _maxListeners: undefined,
      _connections: 0,
      _handle: [TCP],
      _usingWorkers: false,
      _workers: [],
      _unref: false,
      allowHalfOpen: true,
      pauseOnConnect: false,
      noDelay: false,
      keepAlive: false,
      keepAliveInitialDelay: 0,
      httpAllowHalfOpen: false,
      timeout: 0,
      keepAliveTimeout: 5000,
      maxHeadersCount: null,
      maxRequestsPerSocket: 0,
      headersTimeout: 60000,
      requestTimeout: 0,
      _connectionKey: '4:127.0.0.1:0',
      [Symbol(IncomingMessage)]: [Function: IncomingMessage],
      [Symbol(ServerResponse)]: [Function: ServerResponse],
      [Symbol(kCapture)]: false,
      [Symbol(async_id_symbol)]: 190,
      [Symbol(kUniqueHeaders)]: null
    }
  },
  connections: [
    {
      port: '8083',
      webname: 'fhem',
      name: 'FHEM',
      filter: 'alexaName=..*',
      server: '127.0.0.1',
      uid: 999
    }
  ]
}
[29.12.2024, 11:58:45] sshautoconf: SSH key seems to exist
[29.12.2024, 11:58:45] sshautoconf: aborted with Reverse Proxy replied with neither registered nor unregistered status: out:  err:ssh: Could not resolve hostname fhem-va.fhem.de: Name or service not known
[29.12.2024, 11:58:45] *** SSH: proxy configuration failed: Reverse Proxy replied with neither registered nor unregistered status: out:  err:ssh: Could not resolve hostname fhem-va.fhem.de: Name or service not known
*** FHEM: connected
[29.12.2024, 11:58:46] [FHEM] got: 84 results
[29.12.2024, 11:58:46] [FHEM] Alexa.ArbeitszimmerRollo is blind
[29.12.2024, 11:58:46] [FHEM] Alexa.ArbeitszimmerRollo has
[29.12.2024, 11:58:46] [FHEM]   CurrentPosition [pct]

>snipp<

[29.12.2024, 13:06:36] Got SIGTERM, shutting down alexa-fhem...
[29.12.2024, 13:06:36] Reading alexaFHEM.ProxyConnection set to stopping;; alexa-fhem terminating
[29.12.2024, 13:06:36] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20stopping%3B%3B%20alexa-fhem%20terminating%3B%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_122579110290667&XHR=1
[29.12.2024, 13:07:36] using config from ./alexa-fhem.cfg
*** CONFIG: parsed completely
[29.12.2024, 13:07:36] os.homedir()=/opt/fhem
[29.12.2024, 13:07:36] this is alexa-fhem 0.5.65
[29.12.2024, 13:07:36] connecting to FHEM ...
[29.12.2024, 13:07:36] [FHEM] defaults to: will not send proactive events
[29.12.2024, 13:07:37] [FHEM] trying longpoll to listen for fhem events
[29.12.2024, 13:07:37] [FHEM] starting longpoll: http://127.0.0.1:8083/fhem?XHR=1&inform=type=status;addglobal=1;filter=.*;since=null;fmt=JSON×tamp=1735474057479
[29.12.2024, 13:07:50] [FHEM] got csrfToken:
[29.12.2024, 13:07:50] [FHEM] Checking devices and attributes...
[29.12.2024, 13:07:50] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7BAttrVal(%22global%22%2C%22userattr%22%2C%22%22)%7D&XHR=1
[29.12.2024, 13:07:50] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20TYPE%3Dalexa&XHR=1
[29.12.2024, 13:07:50] [FHEM] waiting for events ...
[29.12.2024, 13:07:50] [FHEM] Fetching FHEM devices...
[29.12.2024, 13:07:50] [FHEM] fetching: http://127.0.0.1:8083/fhem?cmd=jsonlist2%20alexaName%3D..*&XHR=1
[29.12.2024, 13:07:55] [FHEM] alexa device is alexa
[29.12.2024, 13:07:55] [FHEM] alexa will not send proactive events
[29.12.2024, 13:07:55] [FHEM] alexa uses ID: 5d4727a8-f33f-50f1-bb36-d4876e229aa5da04
[29.12.2024, 13:07:55] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3B%7B%24defs%7B%22alexa%22%7D-%3E%7B%22alexa-fhem%20version%22%7D%20%3D%20%220.5.65%22%7D%3B%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[29.12.2024, 13:07:55] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bget%20alexa%20proxyToken%3B%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[29.12.2024, 13:07:55] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Blist%20alexa%20.eventToken%3B%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[29.12.2024, 13:07:55] Server listening on: http://127.0.0.1:35843 for proxy connections
[29.12.2024, 13:07:55] *** SSH: checking proxy configuration
[29.12.2024, 13:07:55] sshautoconf: home=/opt/fhem, spath=/opt/fhem/.alexa, cpath=./alexa-fhem.cfg, sshpath=/opt/fhem/.ssh
[29.12.2024, 13:07:55] Passed config: {
  sshproxy: {
    ssh: '/usr/bin/ssh',
    description: 'FHEM Connector',
    options: [ '-i', '/opt/fhem/.ssh/id_rsa', '-p', 58824, 'fhem-va.fhem.de' ],
    'bind-ip': '127.0.0.1',
    server: Server {
      maxHeaderSize: undefined,
      insecureHTTPParser: undefined,
      _events: [Object: null prototype],
      _eventsCount: 3,
      _maxListeners: undefined,
      _connections: 0,
      _handle: [TCP],
      _usingWorkers: false,
      _workers: [],
      _unref: false,
      allowHalfOpen: true,
      pauseOnConnect: false,
      noDelay: false,
      keepAlive: false,
      keepAliveInitialDelay: 0,
      httpAllowHalfOpen: false,
      timeout: 0,
      keepAliveTimeout: 5000,
      maxHeadersCount: null,
      maxRequestsPerSocket: 0,
      headersTimeout: 60000,
      requestTimeout: 0,
      _connectionKey: '4:127.0.0.1:0',
      [Symbol(IncomingMessage)]: [Function: IncomingMessage],
      [Symbol(ServerResponse)]: [Function: ServerResponse],
      [Symbol(kCapture)]: false,
      [Symbol(async_id_symbol)]: 231,
      [Symbol(kUniqueHeaders)]: null
    }
  },
  connections: [
    {
      port: '8083',
      webname: 'fhem',
      name: 'FHEM',
      filter: 'alexaName=..*',
      server: '127.0.0.1',
      uid: 999
    }
  ]
}
[29.12.2024, 13:07:55] sshautoconf: SSH key seems to exist
[29.12.2024, 13:07:55] sshautoconf: aborted with Reverse Proxy replied with neither registered nor unregistered status: out:  err:ssh: Could not resolve hostname fhem-va.fhem.de: Name or service not known
[29.12.2024, 13:07:55] *** SSH: proxy configuration failed: Reverse Proxy replied with neither registered nor unregistered status: out:  err:ssh: Could not resolve hostname fhem-va.fhem.de: Name or service not known
*** FHEM: connected
[29.12.2024, 13:07:55] [FHEM] got: 84 results
[29.12.2024, 13:07:55] [FHEM] Alexa.ArbeitszimmerRollo is blind

>snipp<

[29.12.2024, 13:07:56] Reading alexaFHEM.ProxyConnection set to error;; Reverse Proxy replied with neither registered nor unregistered status: out:  err:ssh: Could not resolve hostname fhem-va.fhem.de: Name or service not known
[29.12.2024, 13:07:56] [FHEM]   executing: http://127.0.0.1:8083/fhem?cmd=%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20error%3B%3B%20Reverse%20Proxy%20replied%20with%20neither%20registered%20nor%20unregistered%20status%3A%20out%3A%20%20err%3Assh%3A%20Could%20not%20resolve%20hostname%20fhem-va.fhem.de%3A%20Name%20or%20service%20not%20known%0D%0A%3B%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&XHR=1
[29.12.2024, 13:08:02] BearerToken '...F5F4E' read from alexa
[29.12.2024, 13:08:02] [FHEM] got .eventToken
[29.12.2024, 13:08:02] refreshing token
[29.12.2024, 13:08:03] failed to refresh token: invalid_grant: 'The request has an invalid grant parameter : refresh_token. User may have revoked or didn't grant the permission.'
Hier noch etwas aus dem Fhem-Log:
2024.12.29 11:57:25.882 4: WEB_127.0.0.1_58986 GET /fhem?cmd=%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20stopping%3B%3B%20alexa-fhem%20terminating%3B%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_464230115418499&XHR=1; BUFLEN:0
2024.12.29 11:57:25.915 4: WEB: /fhem?cmd=%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%201%3B%3Bundef%7D%3Bsetreading%20alexa%20alexaFHEM.ProxyConnection%20stopping%3B%3B%20alexa-fhem%20terminating%3B%7B%24defs%7B%22alexa%22%7D-%3E%7B%22active%22%7D%20%3D%200%3B%3Bundef%7D&fwcsrf=csrf_464230115418499&XHR=1 / RL:20 / text/plain; charset=UTF-8 / Content-Encoding: gzip
 / Cache-Control: no-cache, no-store, must-revalidate
Ich habe dann mal ein alexa-Update gemacht, Fhem und später auch den Server (Ubuntu 18.04.6 LTS (GNU/Linux 4.15.0-213-generic x86_64)) neu gestartet.
Leider alles ohne Ergebnis.
Durchgeführte Änderungen am System in den letzten Tagen, die mir einfallen:
- csrfToken von none auf random (wegen FhemAppV4, mittlerweile wieder auf none)
- umbenennen einiger Räume im Fhem
Leider kann ich mit den Meldungen im LOG nicht wirklich was anfangen und hoffe auf Hilfe...
Vorab vielen Dank
Erdnar

duu75

Gleiches Problem bei mir auch.
Heute früh ging noch alles.

Dann wollte ich nur ein neues Thermometer als Alexa Device hinzufügen und nach FHEM Alexa Restart bekomme ich auch  nur noch DNS Error für fhem-va.fhem.de

Habe alexa-fhem 0.5.65
Ubuntu Server 20.04.6 LTS

Ich bekomme allerdings scheinbar auch ein frisches Token.
[29.12.2024, 14:48:27] [FHEM] got .eventToken
[29.12.2024, 14:48:27] refreshing token
[29.12.2024, 14:48:28] got fresh token

Habe aber trotzdem das Problem.
Und ich habe am System sonst gar nichts geändert.
Weder in Alexa App oder FHEM Server Updates oder sonstiges.

stauraum


erdnar

Habe gerade meine letzte Sicherung getestet, auch damit geht es nicht.
Das Problem kommt also von DRAUSSEN  :o
ER

Edith...: da ist wohl ein Fhem-Server im Weihnachtsurlaub ...

gandi1791

Moin,
bei mir das gleiche Problem.
Scheint ein zentrales Problem zu sein.
fhem auf proxmox container
minicul>ESP-01>868>MAX!; minicul>ESP-01>433>SignalDuino>RSL/Jaro/IT
ESP-01>HM-MOD-RPI-PCB>HM
MySensorsGW>NodeMCU>Sensoren, Aktoren, div.
Broadlink RM Pro+ >433 Steckdosen, IR TV/Receiver; Hue, Alexa Echo Plus, div.Dot 2/3/4;DVB-T Stick>mqtt>TFA 30.3180

Loctite

Ich habe mein System von einem Raspberry Pi 3 auf einen Futros Mini PC mit Lubuntu umgezogen und genau das gleiche.
Hab schon hier im Forum gesucht heute Morgen, aber nichts gefunden.

Bin da jetzt seit heute morgen am versuchen (auch noch andere Dinge am umstellen) und habe nun zum Glück diesen Beitrag gefunden.

Auf der Konsole erhalte ich das:
sudo -u fhem ssh -p 58824 fhem-va.fhem.de status
ssh: Could not resolve hostname fhem-va.fhem.de: Name or service not known


Hurzelchen

Hallo zusammen!

Hier das gleiche Problem. Ihr seid also nicht alleine:  ;)

ssh: Could not resolve hostname fhem-va.fhem.de: Name or service not known

Otto123

Es sollte in nächster Zeit wieder gehen ... DNS Änderungen brauchen immer eine Weile. ;)
Viele Grüße aus Leipzig  ⇉  nächster Stammtisch an der Lindennaundorfer Mühle
RaspberryPi B B+ B2 B3 B3+ ZeroW,HMLAN,HMUART,Homematic,Fritz!Box 7590,WRT3200ACS-OpenWrt,Sonos,VU+,Arduino nano,ESP8266,MQTT,Zigbee,deconz

duu75

Zitat von: Otto123 am 29 Dezember 2024, 16:49:05Es sollte in nächster Zeit wieder gehen ... DNS Änderungen brauchen immer eine Weile. ;)

Funktioniert aktuell bei mir schon wieder!
Danke für das schnelle Fixen!

erdnar

Zitat von: Otto123 am 29 Dezember 2024, 16:49:05Es sollte in nächster Zeit wieder gehen ... DNS Änderungen brauchen immer eine Weile. ;)

Kaum schreibst du es, funktioniert es auch schon wieder ...
Danke & Grüße aus Karl-Marx-Stadt  O:-)

WarLord

FHEM auf RaspberryPi B+
HMLAN Adapter + Div HM Komponenten

Heatseeker

Ahhhh! und ich probiere schon seit Std da Zeitgleich mein Server einmal komplett runtergefahren musste... Nun habe ich nochmal den ganzen Server runtergefahren und nicht nur die FHEM-VM und nun läuft es... Und ich dachte das Problem wäre, wie immer, bei mir!

Danke für die Info!

Loctite

Ja das passte natürlich super !
Neues System aktivieren und natürlich gleichzeitig so etwas  ;D  ;D  ;D

Sehr schön das es wieder läuft !

gandi1791

fhem auf proxmox container
minicul>ESP-01>868>MAX!; minicul>ESP-01>433>SignalDuino>RSL/Jaro/IT
ESP-01>HM-MOD-RPI-PCB>HM
MySensorsGW>NodeMCU>Sensoren, Aktoren, div.
Broadlink RM Pro+ >433 Steckdosen, IR TV/Receiver; Hue, Alexa Echo Plus, div.Dot 2/3/4;DVB-T Stick>mqtt>TFA 30.3180