Search results

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?

Also ich meinte journalctl -f offen haben während du dich im Browser anmeldest. Sowas wie Jul 28 14:50:02 nana unix_chkpwd[165445]: password check failed for user (root) Jul 28 14:50:02 nana IPCC.xs[20070]: pam_unix(proxmox-ve-auth:auth): authentication failure; logname= uid=0 euid=0 tty= ruser=...

Kannst du dir journalctl -f beim Anmelden ansehen? Speziell pvedaemon sollte was zur Anmeldung sagen. Und gibt's irgendwas in der Browser Konsole?

Hey, hast du den richtigen realm ausgewählt?

Like in the UI, these are limits for those specific things. Backup/Restore, Migrations, Cloning and Disk Move. With default, like the placeholders indicate, you set all (of these) to the same. Well, no. What would that even mean? All NICs present? Also virtual bridges? What about traffic...

Hey, [1] are datacenter options. So this if for the things listed there. This is not for the BW of a NIC attached to a CT or VM. For that you have to set the limit on the NIC itself(VM > Hardware > Network Device, or CT > Network under "Advanced" on both). [1]...

short correction: there is a service, pmgbanner.service, that runs on boot and should update this. And for the sake of completeness, [1] are the relevant docs for changing the IP. [1] https://pmg.proxmox.com/wiki/index.php/Getting_started_with_Proxmox_Mail_Gateway#Changing_Hostname_or_IP

auto enp0s31f6 just does ip link set enp0s31f6 up every time the system boots or ifreload, basically automatically start this interface. And this missing explains your problem(well kind of, the vmbr0 should do that automatically), just overlooked the missing auto, good catch by @Steamly :)

Hey, you can configure which network is used for migrations in the datacenter options[1]. For VM traffic you'd create a new bridge and have the second NIC as its slave, then just attach this bridge to VMs as a network device, if done on all the nodes, all VMs connected to this seconds bridge...

exit 0 is good. Could you remove the post up and down entries(just add # to the start of the line), then run ifreload -avvv again and check if the PVE host itself is reachable, or can reach anything on the network(also ip a, still state DOWN?). This should help narrowing down where the problem is.

Hey, looks like you ran out of storage. You have to clear up some space by manually deleting some things off you system. What does df -h say? Something like apt-get clean could help, you can also use du -hs * to find what takes up a lot of space.

Hey, /etc/issue is written by the installer, it is not dynamic. You can ignore it, or change it to whatever you'd like.