Search results

Bad gateway with default config but it's not secure. Same result.

Here is my nginx configuration: upstream proxmox { server "proxmox.mydomain.com"; } server { listen 80 default_server; rewrite ^(.*) https://$host$1 permanent; } server { listen 443; server_name _; ssl on; ssl_certificate...

I followed the directions exactly as stated here: https://pve.proxmox.com/wiki/Web_Interface_Via_Nginx_Proxy I doubled checked to make sure nginx had no errors running or in the configuration and it does not. I'm currently getting a bad gateway error when I visit the domain. I can also verify...

I just upgraded to the latest version of proxmox 6 (6.4-13) and my SSL domain is no longer working on nginx. I've double checked everything included the A record propagation and let's encrypt certs all valid. I can't seem to find the issue after the upgrade. Is there something that changed with...

I found this solution for setting the default kernel with grub: https://forum.proxmox.com/threads/select-default-boot-kernel.79582/ These are my kernel options: submenu 'Advanced options for Proxmox Virtual Environment GNU/Linux' $menuentry_id_option 'gnulinux-advanced-cudgf983475gfhdjk' {...

@proxmox:~# qm config 110 balloon: 8192 bootdisk: scsi0 cores: 8 description: ide2: none,media=cdrom memory: 65536 name: srv1 net0: virtio=56:AF:E8:AA:CB:0C,bridge=vmbr0 numa: 0 onboot: 1 ostype: l26 scsi0: local-zfs:vm-110-disk-1,size=400G scsihw: virtio-scsi-pci smbios1...

Yeah it is old but really running perfectly before the upgrade. @proxmox:~# top -b -c -n 1 -o TIME -w200 | head -15 top - 23:14:00 up 7:35, 1 user, load average: 20.02, 18.97, 18.75 Tasks: 707 total, 2 running, 697 sleeping, 8 stopped, 0 zombie %Cpu(s): 55.0 us, 8.4 sy, 0.0 ni, 36.2...

lscpu: @proxmox:~# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 46 bits physical, 48 bits virtual CPU(s): 24 On-line CPU(s) list: 0-23 Thread(s) per core: 2 Core(s) per socket: 6 Socket(s)...

I've spent a couple hours looking at all the threads complaining of CPU load after an upgrade but haven't found a solution. Here are my servers stats after the upgrade: proxmox-ve: 6.4-1 (running kernel: 5.4.140-1-pve) pve-manager: 6.4-13 (running version: 6.4-13/9f411e79) pve-kernel-5.4: 6.4-6...

I'm having the exact issue upon upgrading from 6.2 to the latest version just now: proxmox-ve: 6.4-1 (running kernel: 5.4.140-1-pve) pve-manager: 6.4-13 (running version: 6.4-13/9f411e79) Is there another patch now I have to install? Or is this a different issue? pct cpuset returns: no...

It worked, here is what I did in case anyone else is interested: Create /etc/wasabi-backup.sh script: #!/bin/bash if [ "$1" == "backup-end" ]; then sleep 1m rm -rf /var/lib/vz/dump/*.tmp sleep 20 mv /var/lib/vz/dump/* /mnt/wasabi-bucket/dump/ sleep 3m mv /var/lib/vz/dump/*.log...

I edited the vzdump.conf and added a script: param. Backup is running right now, fingers crossed!

Would something like this work?: #!/bin/bash if [ "$1" == "backup-end" ]; then mv /var/lib/vz/dump/* /mnt/wasabi-bucket/ fi Where would I put this script to get it to fire after the backup is finished. You stated: but I don't exactly know what that means, can you be more detailed please?

I just checked and I can't. Do you have any idea why?

I have successfully added a wasabi bucket to my proxmox server via s3sf and backups to it work with some VMs but with others I get the error: ERROR: Backup of VM 118 failed - unable to rename '/mnt/wasabi-bucket/dump/vzdump-qemu-118-2020_04_26-17_23_49.vma.dat' to...

There's no reason why this shouldn't be in the upgrade manual! It happened to me too. Thank you so much for writing it out clearly.

Thanks @Vasu Sreekumar that's probably the best way to do it, but I still think this should be in the GUI, not gonna change my mind about that because you actually can add multiple IPs to the same interface with linux.

Exaclty, hopefully others will respond the same way so they'll add it to the GUI. This a very normal thing to need. All the other complicated networking is for maybe 1% of users. You need to add an ignore file for the interface file so proxmox won't override it. At least that's what I...

Understood you can do a lot with the network setup, but I would say that multiple IPs for one container on one nic is common enough to have it in the GUI. Or, a checkbox in the GUI network config for a self-managed network.

That's fine, thanks for the info but I still don't think there is any reason at all that proxmox should not have multiple IP address additions in the GUI. Proxmox already has the nic mappings setup, it wouldn't be hard to map an additional IP from the GUI to IPADDR1, IPADDR2, etc.