Search results

Hey, Wireguard[1] or other VPNs is probably what you are looking for. Depending on whether you have a static IP you may also need DDNS or some small VPS somewhere with a static IP that your VPN clients all connect to. [1] https://www.wireguard.com/

Jap daran liegts, accessed ist vor dem update größer (also neuer), als nach dem update. Als Referenz, hier der relevant Code [1] für diesen Fehler. Es wird also erwartet, dass sich die atime nach einem update der Datei geändert hat, idealerweise in Richtung Gegenwart :) [1]...

Hey, es wird geprüft ob das Dateisystem atime updates respektiert, also diese korrekt speichert. Hier scheint CIFS das nicht zu tun, garbage collection stellt mit der accestime feststellt ob ein chunk weg kann. Grob gesagt werden gebrauchte chunks eben damit als "gebraucht" markiert, dieser...

Hey, hmm, no. Namespaces should not disappear, regardless of being empty or not. Does the cache still have it? ls <CACHE_PATH>/ns And what does proxmox-backup-debug api get /admin/datastore/<DATASTORE_NAME>/namespace say?

Hey, could you post the task log from an earlier backup. Could you also iperf3 -s on the PBS and iperf3 -c <PBS_IP> on the PVE host, what does it report?

Hey, not really. Maybe check if there are reports of problems with the specific model and a specific kernel version, this is not very common, especially with recent hardware. But still, a quick search could save you some headache later on.

Hey, [1] is probably a good start. But generally you add the physical NIC to a bridge("Linux Bridge"), then do IP configuration on the bridge. If you plan to create a bond, you first add the physical NICs to the bond[2], and then the bond to the bridge. For ceph[3] you configure the IP, not the...

did you ifreload -av after changing it to /24? Just to be sure, but could you also check systemctl status pveproxy, and ss -tulpn | grep 8006? Not really, there is only a UI over HTTPS, there is no HTTP one. What you saw was just a warning about the self-signed certificate, which is expected...

Hey, what does ip a and cat /etc/network/interfaces say? Can you ping the PVE host? note: SSH uses port 22, 443 is for HTTPS

Hey, fürs manuelle Backup starten kannst du dir [1] ansehen, und einen job anzulegen/zu bearbeiten [2]. [1] https://pve.proxmox.com/pve-docs/api-viewer/index.html#/nodes/{node}/vzdump [2] https://pve.proxmox.com/pve-docs/api-viewer/index.html#/cluster/backup/{id}

Hey, given this is an english forum I suggest sticking to english, assuming you'd like people to read your post, understand it and give answers :) Could you try changing to IDE[1] for the disk? It is really old, and most of the time not what you want your VM to use, but what it lacks in being...

pvesh is hitting the API, this is not calling anything directly. Could you try curl with an API token? For an example look at [1]. [1] https://pve.proxmox.com/wiki/Proxmox_VE_API#Example:_Use_API_Token

Hey, did you take a look at [1]? It covers quite a lot options. Generally with 1Gbit/s networking just transferring 100GB of data will take about 15mins, and this is if all of the available BW is used. There is no alternative to physically moving disks if you want to not be limited to 1Gbit/s...

Hey, what do these pvesh get /nodes/localhost/network pvesh get /nodes/localhost/network --type=any_bridge say? How does your /etc/network/interfaces look?

Also that is fine, the cluster itself is not very picky. The only thing are migrations, from an older to a newer major version is always supported, from a newer to older (so PVE 8 to a PVE 7 node) not officially, but in practice this will also work just fine, we just don't support it officially...

Hey, ideally nodes in a cluster should have the same version. But having them diverge, especially within the same major version, is no problem.

< und > waren Teil vom Platzhalten. Also <PASSWORD> muss weg, dein PW hin, alles nach dem = bis zum & wird als Passwort interpretiert. (Falls & im PW einfach url encoden)

Eher der Header, der request selbst und die response wäre interessant gewesen, also nicht "Aufrufliste" was anscheinend Standardmäßig ausgewählt. Hätte ich aber vermutlich erwähnen sollen. Nicht so wichtig. Könntest du einfach mal mit curl den API Endpoint selbst aufrufen? curl -X POST \...

Wenn du einen der zwei Requests anklickst sollte da mehr dazu stehen. Aber generell sollte das funktionieren, die Antwort, welche hier fehlt würde dann ca. so aussehen status "401" success 0 message "authentication failure\n" data null jedenfalls würde es eine Antwort geben. Beim IP...

Hmm, und in der Browser Konsole(also nicht die shell in PVE, die normale Browser-Konsole)? Irgendwelche Fehler/Warnungen? Und im Netzwerk-Tab (vom Browser, da wo auch die Konsole ist) sollte es einen POST request zu /api2/extjs/access/ticket beim Anmelden geben, ist der OK? Was kommt da als Antwort?