Search results

Like what? What did you change, and no, read the error message, this is not the same. Make sure the fingerprint is correct.

Hey, you can either change the name of the token when adding the remotes, or delete the existing token(probably called pdm-admin) on the PVE nodes.

Hey, since PVE 8.3 you can directly import OVA[1] files trough our UI. [1] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_ova_ovf_import

Changing the repos does not impact the running system, it just changes where updates are pulled from.

Hey, have you set the "Notification Mode" to "Notification System" under "Datastore" > "Options"?

Hey, you can do that through the UI. "Updates" > "Repositories" > "Add", then disable the one you are currently using and apt update.

Hey, you can unlock it with qm unlock 111.

Hey, this should not be a problem. What is the output of ifreload -avvv after adding address 192.168.10.2/24 to vmbr1? Also, what is ip a after ifreload? Should work anyway, but change iface vmbr1 inet manual to iface vmbr1 inet static if you set an ip.

Hey, you can use the Token-ID as the user and the secret as the password when adding the storage. There is no difference between doing it through the UI or using pvesm add

ohh, I see. You probably want to set smtp_helo_name[1], for that, have a look at the PMG config template system[2]. [1] https://www.postfix.org/postconf.5.html#smtp_helo_name [2] https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmgconfig_template_engine

Hey, you can't really use domains in your SPF record, what you can add is something like a:A.EXAMPLE.COM, but that will just be the IP that IPv4 address that A.EXAMPLE.COM resolves to. With SPF the mailserver's IP is checked, and that is not something you really configure in postfix on your...

Hey, we don't have "supported hardware" or anything alike, if it runs linux it'll very likely run PVE just fine.

Hey, was ist Insomnia? Generell bekommst du mit curl -k -d 'username=root@pam' --data-urlencode 'password=******' https://192.168.55.41:8006/api2/json/access/ticket ein Ticket womit du dann mit curl -k -b "PMGAuthCookie=PMG:root@pam:67BEBAE7::tNW3PaAFWguKQ/..." \ -X POST \ -H...

Hey, you can bond[1] the two interfaces, PBS still would only have one IP, but traffic would go through both interfaces. How this traffic is balanced between the two can be configured. [1] https://pve.proxmox.com/wiki/Network_Configuration#sysadmin_network_bond

Hey, naja, hängt von deinem Setup ab. Aber prinzipiell ca. so auto eth0 iface eth0 inet static address 192.0.2.7/24 gateway 192.0.2.254 auto eth1 iface eth1 inet static address 10.0.0.4/24 IPs, Netzmasken und Interfacenamen sind natürlich noch anzupassen. Hier [1] noch die...

Hey, when booting there should be a small noVNC menu on the left that also allows sending keys, did you give that a try? Alternatively you could also just boot some live linux iso and chroot into your OS.

Hey, that sounds weird. Could you post the output of ip a and cat /etc/network/interfaces of both hosts? You can put the output in <output> tags, and depending on how much it is wrapping it in could also make sense.

As described in [1], you'll also have to update the corosync config[2], but we do not recommend changing hostnames of nodes within a cluster. [1] https://pve.proxmox.com/wiki/Renaming_a_PVE_node#Change_Hostname [2] https://pve.proxmox.com/pve-docs/chapter-pvecm.html#pvecm_edit_corosync_conf

Hey, you just need to update[1] these two (assuming this is a standalone node) - /etc/hosts - /etc/hostname [1] https://pve.proxmox.com/wiki/Renaming_a_PVE_node#Change_Hostname

So the PVE host can ping the server that hosts the SMB share?