Recent content by MicJB

I see, I'm using 3.3-1, I guess it's been disabled only in 3.4, however it would be nice to not having to reinstall all proxmox installations just to disable SSL 3.0. Thank you, Mic

I've succesfully installed my SSL certificates from StartCom following http://pve.proxmox.com/wiki/HTTPSCertificateConfiguration everything works flawlessly and I'm very happy :D However testing with https://www.digicert.com/help/ tells me that: Protocol Supported: TLS 1.2, TLS 1.1, TLS 1.0...

I see, that good actually, thanks for the reply ;)

I was wondering whether there is any security or performance reason for which I shouldn't enable TUN/TAP by default on my VPS, any idea? The same goes for the FUSE setting (vzctl set $VMID --devnodes fuse:rw --save), are there any negative side effects if one enables it by default? Thank you, Mic

Interesting, however this does not seem to be an option for us as we'd like console access to VMs regardless of what user might have installed on uninstalled in their VMs.

Thanks dietmar, I agree that API calls work just fine. Unfortunately that's not the issue here. The issue is opening the VM console URL using a standard link like <a href="https://<proxmox-server-port>/?console=openvz&novnc=1&vmid=123&vmname=hostname&node=proxmox">open vm console</a> which will...

I just wanted to point out that the link in question ISN'T working for anyone else because this runs on the same server as proxmox and thus setting cookies works perfectly - however as state elsewhere multiple times if you have your own web app/site/service you're screwed because cookies cannot...

Anyone found a solution to this? I've the same problem as timur, needing to log in user programmatically without exposing the proxmox GUI to the user.

Phinitirs, please send me your Skype nick, thanks for your help, so far looks like the only three options available are 1) to modify proxmox api to programmatically log in the user which automatically sets the authorization cookie, or 2) modify proxmox api to POST the authorization cookie and...

This is the exact same issue I'm describing here: http://forum.proxmox.com/threads/21200-Accessing-VM-s-NoVNC-from-another-website Anyone found any solution to this?

Hi Phinitris, thanks for your reply. I do know that I can get a ticket from the API and that's what I do actually. The problem is that I cannot use the ticket because it needs to be passed as a cookie to the proxmox server and there is no way I (or anyone) can set a cookie to the proxmox server...

Hi all, I'm working on a minimalistic service to let users create and manage their own OpenVZ VMs and access their VM terminal through my website. My original plan was to simply embed in an iframe (in my website) the VM's NoVNC console url, ex: <iframe...