[{"data":1,"prerenderedAt":48},["ShallowReactive",2],{"articles-page-5":3},{"articles":4,"total":47},[5],{"path":6,"title":7,"description":8,"image":9,"createdAt":10,"authorKey":11,"tags":12,"codeLinks":17,"readingTime":18,"excerpt":19},"\u002Farticles\u002F20130918-pve-restrict-webui-access","Proxmox VE Restricting Web UI access","How to password protect the web UI of Proxmox VE.","\u002Fimages\u002Fcovers\u002Fproxmoxve-webui.png","2013-09-18","philip",[13,14,15,16],"sysadmin","linux","proxmoxve","security",null,3,{"type":20,"value":21},"minimark",[22,44],[23,24,25,26,36,37,40,41],"p",{},"With the release of ",[27,28,29],"strong",{},[30,31,35],"a",{"href":32,"rel":33},"https:\u002F\u002Fwww.proxmox.com\u002Fde\u002Fnews\u002Fpressemitteilungen\u002Fproxmox-ve-3-0-veroeffentlicht",[34],"nofollow","Proxmox VE 3.0"," back in May 2013, the Proxmox VE web interface does no longer require Apache. Instead, they're using now a new event driven API server called ",[27,38,39],{},"pveproxy",". That was actually a great step ahead, as we all know Apache get's bulkier every day and the new pveproxy is a much more lightweight solution. But the question arose: ",[27,42,43],{},"How do I protect my Proxmox VE WebUI with basic user authentication?",[23,45,46],{},"Basically, we do not trust any web application out there so we better double protect the whole WebUI with plain old basic auth - previously done in Apache by .htaccess.",29,1794961390517]