NEWS
[Neuer Adapter] Proxmox VM
-
@meister-mopper
ok
hier der weg den ich gehe wenn ich die Seite das erste mal aufrufen ( gelöschter Browser Cache) Chrome
dann erweitert drücken
dann Weiter zu 192.168.42.90 (unsicher)
hier sehe ich das ich pam ausgewählt habe. mit pve komme ich mit meinem User nicht rein. dann melde ich mich an. -
@meister-mopper
ok
hier der weg den ich gehe wenn ich die Seite das erste mal aufrufen ( gelöschter Browser Cache) Chrome
dann erweitert drücken
dann Weiter zu 192.168.42.90 (unsicher)
hier sehe ich das ich pam ausgewählt habe. mit pve komme ich mit meinem User nicht rein. dann melde ich mich an.Und somit wird auch bei dir via https kommuniziert. Der PAM-login ist richtig, da dies auch über ssh funktioniert.
PVE-User können sich nur in der GUI einloggen.
-
Und somit wird auch bei dir via https kommuniziert. Der PAM-login ist richtig, da dies auch über ssh funktioniert.
PVE-User können sich nur in der GUI einloggen.
-
@alero sagte in [Neuer Adapter] Proxmox VM:
das würde ich gerne noch hin bekommen.
Im Chrome und Edge bleibt dieser Hinweis. Wenn du ihn nicht magst, musst du dich wohl mit ACME und Proxmox auseinandersetzen müssen :man-shrugging:
-
@alero sagte in [Neuer Adapter] Proxmox VM:
das würde ich gerne noch hin bekommen.
Im Chrome und Edge bleibt dieser Hinweis. Wenn du ihn nicht magst, musst du dich wohl mit ACME und Proxmox auseinandersetzen müssen :man-shrugging:
@meister-mopper
habe heirzu schon ein Video gefunden. kann ich das dann so machen?
Proxmox SSL Certificates with Let's Encrypt
Zertifikate ist nicht so meins. Habe angst das mein proxmox nachher nicht mehr läuft bzw. ich mich nicht mehr anmelden kann. -
@meister-mopper
habe heirzu schon ein Video gefunden. kann ich das dann so machen?
Proxmox SSL Certificates with Let's Encrypt
Zertifikate ist nicht so meins. Habe angst das mein proxmox nachher nicht mehr läuft bzw. ich mich nicht mehr anmelden kann. -
hi,
habe mir den proxmox adapter installiert leider bekomme ich keine Verbindung:proxmox.0 2023-10-13 15:31:07.983 error 401: wrong User data, could not log in, please try again with correct user and pw proxmox.0 2023-10-13 15:31:07.983 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason proxmox.0 2023-10-13 15:31:07.982 error Unable to authenticate with Proxmox host. Please check your credentials proxmox.0 2023-10-13 15:31:04.888 debug Use Proxmox API: https://192.168.42.90:8006/api2/json
IP, Port, User und PW sind richtig. Damit kann ich mich auf dem Proxmox Server anmelden. Muss ich noch was im Proxmox freigeben?
@alero sagte in [Neuer Adapter] Proxmox VM:
IP, Port, User und PW sind richtig. Damit kann ich mich auf dem Proxmox Server anmelden. Muss ich noch was im Proxmox freigeben?
Moin,
war zu faul, alles zu lesen, Du hast die falsche Domäne, das ist immer PAM, nicht
PVE
VG
Bernd -
@alero sagte in [Neuer Adapter] Proxmox VM:
IP, Port, User und PW sind richtig. Damit kann ich mich auf dem Proxmox Server anmelden. Muss ich noch was im Proxmox freigeben?
Moin,
war zu faul, alles zu lesen, Du hast die falsche Domäne, das ist immer PAM, nicht
PVE
VG
Bernd -
-
Hallo
Hat noch jemand das Problem mit
has no existing object, this might lead to an error in future versions?Issue hab ich gerade erstellt.
@negalein welche adapter version..ahh ich seh 2.2.0
da wurde das object nicht angelegt
proxmox.0.storage_proxmox_local-lvmlösche den mal .. und starte den adapter neu
zigbee hab ich, zwave auch, nuc's genauso und HA auch
-
@negalein welche adapter version..ahh ich seh 2.2.0
da wurde das object nicht angelegt
proxmox.0.storage_proxmox_local-lvmlösche den mal .. und starte den adapter neu
wenn du grad an dem Thema bist, ich hab mal alle Objects von Proxmox geloescht und den Adapter dann neu gestartet, hier kommt das bei den vmid , Adapter Version 2.2.0 :
2023-10-27 09:16:32.292 - info: host.themachine instance system.adapter.proxmox.0 started with pid 78860 2023-10-27 09:16:33.146 - info: proxmox.0 (78860) starting. Version 2.2.0 in /opt/iobroker/node_modules/iobroker.proxmox, node: v20.9.0, js-controller: 5.0.14 2023-10-27 09:16:33.156 - warn: proxmox.0 (78860) Using Proxmox API: https://192.168.0.210:8006/api2/json 2023-10-27 09:16:33.605 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.docker.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.672 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.bookworm-ilovegym.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.742 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.themachine.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.789 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.redis.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.826 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.octoprint.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.902 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.grafana.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.960 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.wireguard.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.023 - info: proxmox.0 (78860) State value to set for "proxmox.0.qemu.pfSense.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.054 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.Network-Test.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.141 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.node-red.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.219 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.uptimekuma.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.275 - info: proxmox.0 (78860) State value to set for "proxmox.0.qemu.iobroker.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.335 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.redisdb.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:32.256 - info: host.themachine "system.adapter.proxmox.0" enabled 2023-10-27 09:16:32.292 - info: host.themachine instance system.adapter.proxmox.0 started with pid 78860 2023-10-27 09:16:33.146 - info: proxmox.0 (78860) starting. Version 2.2.0 in /opt/iobroker/node_modules/iobroker.proxmox, node: v20.9.0, js-controller: 5.0.14 2023-10-27 09:16:33.156 - warn: proxmox.0 (78860) Using Proxmox API: https://192.168.0.210:8006/api2/json 2023-10-27 09:16:33.605 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.docker.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.672 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.bookworm-ilovegym.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.742 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.themachine.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.789 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.redis.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.826 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.octoprint.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.902 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.grafana.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.960 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.wireguard.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.023 - info: proxmox.0 (78860) State value to set for "proxmox.0.qemu.pfSense.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.054 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.Network-Test.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.141 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.node-red.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.219 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.uptimekuma.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.275 - info: proxmox.0 (78860) State value to set for "proxmox.0.qemu.iobroker.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.335 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.redisdb.vmid" has to be type "string" but received type "number" -
wenn du grad an dem Thema bist, ich hab mal alle Objects von Proxmox geloescht und den Adapter dann neu gestartet, hier kommt das bei den vmid , Adapter Version 2.2.0 :
2023-10-27 09:16:32.292 - info: host.themachine instance system.adapter.proxmox.0 started with pid 78860 2023-10-27 09:16:33.146 - info: proxmox.0 (78860) starting. Version 2.2.0 in /opt/iobroker/node_modules/iobroker.proxmox, node: v20.9.0, js-controller: 5.0.14 2023-10-27 09:16:33.156 - warn: proxmox.0 (78860) Using Proxmox API: https://192.168.0.210:8006/api2/json 2023-10-27 09:16:33.605 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.docker.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.672 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.bookworm-ilovegym.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.742 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.themachine.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.789 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.redis.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.826 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.octoprint.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.902 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.grafana.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.960 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.wireguard.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.023 - info: proxmox.0 (78860) State value to set for "proxmox.0.qemu.pfSense.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.054 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.Network-Test.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.141 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.node-red.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.219 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.uptimekuma.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.275 - info: proxmox.0 (78860) State value to set for "proxmox.0.qemu.iobroker.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.335 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.redisdb.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:32.256 - info: host.themachine "system.adapter.proxmox.0" enabled 2023-10-27 09:16:32.292 - info: host.themachine instance system.adapter.proxmox.0 started with pid 78860 2023-10-27 09:16:33.146 - info: proxmox.0 (78860) starting. Version 2.2.0 in /opt/iobroker/node_modules/iobroker.proxmox, node: v20.9.0, js-controller: 5.0.14 2023-10-27 09:16:33.156 - warn: proxmox.0 (78860) Using Proxmox API: https://192.168.0.210:8006/api2/json 2023-10-27 09:16:33.605 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.docker.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.672 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.bookworm-ilovegym.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.742 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.themachine.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.789 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.redis.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.826 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.octoprint.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.902 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.grafana.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:33.960 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.wireguard.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.023 - info: proxmox.0 (78860) State value to set for "proxmox.0.qemu.pfSense.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.054 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.Network-Test.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.141 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.node-red.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.219 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.uptimekuma.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.275 - info: proxmox.0 (78860) State value to set for "proxmox.0.qemu.iobroker.vmid" has to be type "string" but received type "number" 2023-10-27 09:16:34.335 - info: proxmox.0 (78860) State value to set for "proxmox.0.lxc.redisdb.vmid" has to be type "string" but received type "number" -
Proxmox V8.0.4
-
Adapter v2.2.0
Proxmox v8.0.4Löschen der Objekte und restart.
Ich habe den String proxmox.0.lxc_pihole.vmid nicht in den letzten 2 Tagen im Log gefunden, scheint also nur bei/mit/vor/nach dem Erstellen der States zu passieren. :)
2023-10-27 09:59:39.426 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_pihole.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:39.738 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_zigbee2mqtt.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:39.998 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_mqtt.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:40.287 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_influxdb.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:40.466 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_bind.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:40.774 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_mariadb.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:41.163 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_grafana.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:41.600 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_samba.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:41.718 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_scrypted.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:42.019 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_plex.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:42.223 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_wireguard.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:42.431 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_openssl.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:42.627 - info: proxmox.0 (1159091) State value to set for "proxmox.0.qemu_iobroker.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:42.794 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_iobroker-test.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:42.932 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_tautulli.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:43.177 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_wikijs.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:43.307 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_mediamtx.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:43.619 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_redis.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:43.760 - info: proxmox.0 (1159091) State value to set for "proxmox.0.qemu_iobroker-devel.vmid" has to be type "string" but received type "number" 2023-10-27 09:59:43.917 - info: proxmox.0 (1159091) State value to set for "proxmox.0.lxc_bookworm-template-sudo-tim.vmid" has to be type "string" but received type "number" -
@arteck sagte in [Neuer Adapter] Proxmox VM:
isch guck später nach
... wenn du schon dabei bist... hier kam gerade waehrend des Backups des LXC, indem iobroker laeuft, diese Errors:
-
@arteck sagte in [Neuer Adapter] Proxmox VM:
isch guck später nach
... wenn du schon dabei bist... hier kam gerade waehrend des Backups des LXC, indem iobroker laeuft, diese Errors:
@ilovegym sagte in [Neuer Adapter] Proxmox VM:
/nodes/hpg380/storage/VMBackup/content
da ist der storage nicht da.. und da du nur 1 node hast oder nur angegeben hast, kann der nicht switchen
früher war die meldung unterdrückt
-
@ilovegym sagte in [Neuer Adapter] Proxmox VM:
/nodes/hpg380/storage/VMBackup/content
da ist der storage nicht da.. und da du nur 1 node hast oder nur angegeben hast, kann der nicht switchen
früher war die meldung unterdrückt
ja, weil er gerade am backup schreiben ist.. hmmpff d.h. die Meldung kommt jetzt immer, wenn ich ein Backup mache in Proxmox.. ? mit dem LXC.. ?
Kann man da das Timeout hoeher setzen.. fuer den Fehler? er kommt genau einmal, wie im Logfile, dann ist wieder ruhe.. -
@negalein welche adapter version..ahh ich seh 2.2.0
da wurde das object nicht angelegt
proxmox.0.storage_proxmox_local-lvmlösche den mal .. und starte den adapter neu
@arteck sagte in [Neuer Adapter] Proxmox VM:
lösche den mal .. und starte den adapter neu
Danke, funktioniert wieder.
-
ja, weil er gerade am backup schreiben ist.. hmmpff d.h. die Meldung kommt jetzt immer, wenn ich ein Backup mache in Proxmox.. ? mit dem LXC.. ?
Kann man da das Timeout hoeher setzen.. fuer den Fehler? er kommt genau einmal, wie im Logfile, dann ist wieder ruhe..
Support us
404
Online32.4k
Benutzer81.5k
Themen1.3m
Beiträge