Search results

  1. backup failed: connection error: Connection timed out (os error 110)

    Thank you, glad to know that I'm not he only one. Will put this fix in and report back.
  2. backup failed: connection error: Connection timed out (os error 110)

    I tried that and still see the issue occasionally. I think the issue might be unrelated to PBS.
  3. backup failed: connection error: Connection timed out (os error 110)

    You mean use api authentication instead of username/pass?
  4. backup failed: connection error: Connection timed out (os error 110)

    Nevermind, it was a network issue. Firewall was blocking incoming requests from this server. Not sure why smaller VMs were still able to be backed up. It wasn't the firewall. I'm still experiencing this issue.
  5. backup failed: connection error: Connection timed out (os error 110)

    I recently setup PBS on a public cloud and have been getting these errors when trying to backup "larger" VMs(over 50GB). VMs less than this size have been backing up without issues but I keep getting issues with larger ones. I finally was able to backup a 64gb VM after a few tries but haven't...
  6. a simple way to passthrough an internal SATA DVD burner [solved]

    For anyone who's looking for a working solution, this tutorial is still working perfectly. Do remember to change the initiator-name to initiator-address
  7. [SOLVED] [Warning] Latest Patch just broke all my WINDOWS vms. (6.3-4) [Patch Inside] (See #53)

    Windows Server 2019 Here's the conf agent: 1 balloon: 2048 bios: ovmf bootdisk: scsi0 cores: 4 cpu: host efidisk0: SSD1:vm-101-disk-1,size=4M machine: q35 memory: 4096 name: DC net0: virtio=4A:A6:28:0B:4A:A9,bridge=vmbr0 numa: 0 onboot: 1 ostype: win10 scsi0...
  8. [SOLVED] [Warning] Latest Patch just broke all my WINDOWS vms. (6.3-4) [Patch Inside] (See #53)

    This not true in my case. I have 3 windows VMs created on PVE 6.2 and they too had the issue.
  9. [SOLVED] [Warning] Latest Patch just broke all my WINDOWS vms. (6.3-4) [Patch Inside] (See #53)

    Same issue for me too. One of them was an AD server so all my web apps and VPNs were hosed. I had to drive back home to fix it locally. I dont know why but PVE updates seems to be a lot less stable than before. Even for home use.
  10. e1000 breaks after upgrade

    The same issue happened with VirtIO Nic too. Old network adapter got removed and a new one replaced it. Had to set static ips again.
  11. LXC update breaking up write permission

    I have it enabled on my container but /sys is still being mounted at read only. I am able to get docker to work by remounting it as rw inside the container, but I couldnt do that for all containers so I ended up downgrading.
  12. LXC update breaking up write permission

    Same issue. Downgrading fixed it. This is pretty major as it broke all my containers running docker.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!