Recent content by pizza

According the PBS manual, HTTP/2 is used for transfer data. Does this work when using IP server for remote sync or for FDQN? Or is a FQDN a requirement for HTTP/2?

A few questions: 1. Can I sync a PBS 3.0 server with PBS 2.4? 2. Can a remote PBS 3.0 server used as backup storage for a PVE 7.4 server?

Can it work when I use user quota on ext4 for each datastore?

I have multiple datastores on PBS on a big disk with ext4. Each datastores shows the total disk usage and the free space of the total diskspace instead of his own usage. Can this be solved or must I use zfs?

I found this (using pointopoint): https://tomjorge.me/install-proxmox-and-create-vms-with-ips-on-your-hetzner-dedicated-server/ Update: this works

Won't you get an (mac address) abuse from Hetzner with this setup?

When you order a additional single IP address on Hetzner, you get also a MAC address for it?

I have a dedicated Proxmox server on Hetzner with a single IP address, Is it possible with this configuration to add an extra single (public) IP address which a VM directly can use (without NAT rules)? iface enp0s31f6 inet static address 138.x.x.18/26 gateway 138.x.x.1 iface...

Still no user authenticated SMTP for sending mail?

I had the same after updating today. This was on a Hetzner server.

Update: Installing kernel 5.4 on Ubuntu 18.04 makes fstrim working https://ubuntuhandbook.org/index.php/2020/08/ubuntu-18-04-5-released-5-4-kernel/ :)

Ubuntu 18.04 with kernel 4.15 Ubuntu 18.04 with kernel 4.15, discard is enabled

I have migrated older VM Ubuntu machines to a thin-LVM storage. To make fstrim work (enabling SSD emulation), the virtio0 disk must changed to scsi0. I editted the VM conf file, but the VM will not start because the disk is not found.

I'm trying to create a VXLAN between nodes with a IPv6 only address. Proxmox cluster runs fine over IPv6. After SDN apply I get this error: vxlan_vnet1 : error: vxlan_vnet1: vxlan-remoteip: Expected 4 octets in '2a01:x:x:x::2' TASK ERROR: command 'ifreload -a' failed: exit code 1

Using LVM-Thin on iSCSI (use LUN directly=disabled) works with LXC snapshots. What I did first create iSCSI (no LUN directly), so we have a block device (check it with lsblk). Then create LVM-Thin from console