Search results

Without "secure 1" it would be clear text. The auto-TLS would just be set to off

I see. Is there a documented method for reinstalling grub for Proxmox? What do we need to do with the BIOS boot and EFI System partitions? root@world:~# fdisk -l /dev/sdo Disk /dev/sdo: 37.3 GiB, 40020664320 bytes, 78165360 sectors Units: sectors of 1 * 512 = 512 bytes Sector size...

The scenario is that Proxmox is not able to boot. Proxmox had been installed and working prior to it no longer working. And upon following https://pve.proxmox.com/wiki/Recover_From_Grub_Failure You get the following issues: - unable to mount /dev/sdX1, because it is unable to determine the...

If you test it and run "grub-install /dev/sda" you'll see that it'll result in taking up 9.3MB Unless there are other grub-install options or pre-requisites that are required. So far, the issues are: - unable to mount /dev/sdX1, because it is unable to determine the fs/magicblock/etc. - you...

I don't have the error output with me, but when following the grub recovery page: https://pve.proxmox.com/wiki/Recover_From_Grub_Failure I get an error that it is not able to mount /dev/<proxmox>1 because it "can't find the magic block" or "doesn't know what fs it is"

This happens because Proxmox creates three partitions on a drive: 1. a 1MB BIOS boot partition 2. a 256MB EFI partition 3. the rest The BIOS boot partition is too small for grub to be installed into, which is why it complains there is no space left Grub needs at least 9.3MB to install

Does anyone else use OpenLDAP with proxmox?

I followed the steps enabling SSL for LDAP with a self-signed certificate, but get the error: Aug 10 05:15:56 world pvedaemon[515]: authentication failure; rhost=10.10.10.225 user=test2@ldap msg=SSL connect attempt failed https://help.ubuntu.com/lts/serverguide/openldap-server.html#openldap-tls...

Uploading a 3.2GB ISO times out and gives and error Similar to this post, https://forum.proxmox.com/threads/timeout-error-at-iso-upload.8848/

What are all of Proxmox's required directories? I'm looking to be able to put in a fresh install of Proxmox, and have Proxmox running by having all of its required settings, configurations, logons, and certificates stored in the ZFS pool I have "images", "templates", "containers", and...

Unless it changed when the server was turned off for maintenance and back on again. I don't know what changed. Everything is vanilla on the server with zero system-wide changes, except for the container config in /etc/pve/lxc/<container>.conf Where can you find the global LXC policies?

Upon 2 nights and 14 hours of troubleshooting later, it turns out Proxmox 4.4-1/eb2d6f1e no longer needs the following lines of code inside /etc/pve/lxc/<container>.conf lxc.cgroup.devices.allow = c 10:200 rwm lxc.hook.autodev = sh -c "modprobe tun; cd ${LXC_ROOTFS_MOUNT}/dev; mkdir net; mknod...

Did you add the lines to /etc/pve/lxc/<container>.conf? Did you create it as a Privileged Container? I think you can add it to the container.conf in either of the ways below (either with a "=" or a ":") and both ways still creates a /var/lib/lxc/container/config that works...

The apparmor error does not seem to affect running OpenVPN. the service is able to run and create a listening socket

PVE: 4.4 Image: Ubuntu 16.10 I'm following the tutorial for setting up OpenVPN, here: https://hungred.com/how-to/setup-openvpn-on-proxmox-lxc/. This worked just fine in PVE 4.2, and have set up 3 OpenVPN servers this way, but it no loger seems to work in PVE 4.4 I've added to...

If a linux bridge isn't created, will proxmox have one to use by default? Also, if you have multiple linux bridges, how will proxmox decide which one to nat it to? As of v4.4 there isn't an option to select which bridge to use; it just has an "enable NAT mode" radio button to select

Creating a new container with the Ubuntu 16.10 image produces this error when executing `tmux` This is a possible regression from the Ubuntu 16.04 image, which did not have this issue tmux: need UTF-8 locale (LC_CTYPE) but have ANSI_X3.4-1968 This can be remedied by uncommenting # en_US.UTF-8...

Upgraded the packages to 4.4, and confirm it works now

The new Ubuntu 16.10 lxc image is unable to be used when creating a new container. Did anyone else run into this issue? And also in the error message there's a typo (it says "ubunt" instead of "ubuntu") extracting archive...

I just have a while loop running when the container restarts, it seems to work pretty well for me right now #!/bin/bash # Restart openvpn on reboot while true; do ps -ef| grep -v grep | grep /etc/openvpn/server.conf 2>/dev/null >/dev/null if [ ! "$?" == 0 ]; then...