Search results

i updated the certs to my purchased ssl, while the interface now works with no self-signed errors, the java applet doesnt work also tried the instructions at http://pve.proxmox.com/wiki/HTTPSCertificateConfiguration for the /etc/pve certs not just /etc/pve/local i'm getting the following error...

from my experience you dont need to restart the host unless there is a kernel update as well, only vm's if there affected (eg qemu updates for kvm vm's) however a reboot is generally safer and faster than rebooting all your VM's manually

theres a few threads about testing wheezy and proxmox 3.0 which is not yet stable i come to ask the question has upgrading a proxmox 2.3 install from squeeze to wheezy been tested and does anyone know if it works or is supported? I've set all my PVE boxes up by starting with blank squeeze...

can i ask why not? i'm pretty certain a virtual package is what only a few lines in the repo packages list? it appears that you have it for the kernel itself or at least it updates safely with apt-get dist-upgrade or apt-get upgrade the pve-headers packages do not update in the same way and...

is there any update to this thread - this creates a lot of frustrations every time you update the kernel and we forget to manually find and update the headers package

I too have the same question, we have no need for the live migration at this time or HA support (although offline migration would be nice) - is this possible?

i run r1soft/idera on my proxmox boxes to backup the settings of the HV and openvz vm's where and if i run them (KVM vm's are excluded from HV backup and done within the vm itself) now on initial setup i have to install the pve-headers package that matches the version of the running kernel for...

Hi There I'm using ezeelogin to manage a load of servers, of which around 10 are within my proxmox cluster i'm trying to setup the ezeelogin Datacenter section up to allow my ezeelogin users to login to the proxmox interface from ezeelogin in 1 click and not need to be provided with the...

well theres no central management as you have to put software firewalls on every VM as well, also using openvz containers further complexifies the firewall setup (you either have to explicitly pass off VZ container traffic by IP to the container or manage the VZ container network access from the...

sorry to resurrect an old thread, i'd love to mirror the proxmox repo to help provide geo-redundancy and help the effort in that way if i can

Its generally simpler to manage to get a Hardware firewall to put your servers behind. Proxmox runs no iptables firewalls on the hosts and it would get pretty complex and messy to do this yourself and you would then also have to run software firewalls on all your VM's as well Most providers...

aware of that thanks - is there anyway to set the default for new users that wont have been on before?

How can i set the default realm to PVE instead of PAM so that users dont trip up when they login for the first time, as having a few issues with users forgetting to set the realm correctly

Thanks Dietmar - i ended up trying the edits in my first post and they worked - good job i left 8006 working internally - its not seeming to affect anything on the web frontend for users - console works etc

Hi - I Tried searching for this but either i failed or i couldnt find the info here or on the Wiki Problem: Current web gui port is 8006 over HTTPS - We'd Like to change this to standard port 443 Question(s): Can i just move the ports in apache config? Do I need to keep the service also...

thanks for the info, i thought as much but still not sure how i would implement it i see how i could setup ordered failovers that would make the vm prefer a specific host and failover to specific HV's in a controlled manner and just use different hosts for the different VM's however i dont see...

Hi I setup a 2 node HA cluster with a shared quorum disk on the SAN thats backing the storage for the HV's (LVM over iSCSI) and its working well! what i'd like to setup if possible is some rules that: assuming the cluster is healthy (all host servers online) to make sure specific VM's always...

use Venet unless you have a specific need for veth, it will be much simpler to manage for your VM's and provide less headaches you do not need multiple ethernet cards for more than 1 VM although it is reccomended you have more than one particularly if some of your VM's are network intensive...

i am loading ipt_recent because its a required module for CSF to work, and it does work my line is this IPTABLES="ipt_REJECT ipt_tos ipt_recent ipt_owner iptable_nat ipt_REDIRECT ipt_TOS ipt_LOG ip_conntrack ipt_limit ipt_multiport iptable_filter iptable_mangle ipt_TCPMSS ipt_tcpmss ipt_ttl...

i was meaning as an iptables module like you have loaded the others....