Proxmox не работает веб интерфейс

Содержание

PROXMOX не корректно отрабатывает web-интерфейс
[Решено] не открывается web интерфейс
ProxMox web interface not running
Steijn van Essen
Steijn van Essen
Steijn van Essen
Steijn van Essen
Steijn van Essen

PROXMOX не корректно отрабатывает web-интерфейс

Доброго времени суток.

Не корректно отрабатывает web-интерфейс PROXMOX. Скриншот по ссылке. К сожалению, из-за показанной ошибки нельзя увидеть статус запуска виртуалки, подключиться к Консоли PROXMOX. Хотя виртуалки работают, к Линуксячим подключиться можно по SSH, к Виндузячным по RDP. Но такая ситуация не правильная.

Как исправить сложившуюся ошибку не перезагружая сервер и виртуальные машины.

Заранее спасибо всем ответившим.

Кластер или отдельный хост ?

/root/.ssh/known_hosts — попробуй переименовать

Попробовал, не помогло — теперь еще хуже (скриншот). Пишет: «Login failed. Please try again».

Все началось с того, что возникла необходимость перезагрузить одну из виртуалок. Виртуалка после этого не запустилась. При попытке посмотреть статус виртуалки через web-интерфейс столкнулся с проблемой что посмотреть ничего нельзя. Остальные виртуалки работают. Перезагружать весь хост бояздно — боюсь столкнуться с ситуацией неработающего сервера посередине рабочей недели.

Так же не помогло.

В режиме инкогнито попробуй открыть. Кэш браузера порой мешает нормально в проксе работать.

То же самое, и из других браузеров такая же картина.

бывает такая фигня. pct list не отрабатывает. надо покилять все, что связано с зависшим контейнером. иначе только ребут.

Без ребута всего хоста, перезагрузить только сервис нельзя?

можешь перезапустить все pve сервисы — не поможет. как-то удавалось покилять остатки зависшего контейнера и отпустило.

проблема даже проявляется иногда в последнем pve 5.4-11. Но ребята ушли пилить 6.0. Энтерпрайзненько чо

На моей практике такая проблема проявляется если ты перезапускаешь контейнер после обновления ядра без перезагрузки, дико бесит.

Починить интерфейс помогает ps aux | grep lxc и прибить lxc monitor для зависшего контейнера, но сам контейнер это не починит, только перезагрузка

Место на диске не закончилось?

А kworker случаем не грузит одно ядро на 100%. Если это так то, а оно очень похоже по симптомам, это достаточно неуловимый баг в proxmox 5.

Источник

[Решено] не открывается web интерфейс

Всем добрый день

Не открывается web интерфейс, белая страница.

proxmox-ve: 5.2-2 (running kernel: 4.15.17-1-pve)
pve-manager: 5.2-1 (running version: 5.2-1/0fcd7879)

очистка кэша браузера, другие браузеры та же картина

systemctl restart pveproxy — без результата

# netstat -an | grep 8006
tcp 0 0 0.0.0.0:8006 0.0.0.0:* LISTEN

ssh работает, виртуальные машины работают, мобильная версия открывается

Для начала попробуйте в браузере ввести IP-адрес Вашего proxmox вместо DNS-имени, чтобы получилось так ( 192.168.10.152 замените на свой IP-адрес):

https:// 192.168.10.152 :8006

Если Вы не установили на свой proxmox сертификат — купленный или выпущенный своими силами и добавлен на Ваш компьютер в корневые сертификаты, то в браузере «Opera» появится сообщение : «В аше подключение не является приватным. Не удалось подтвердить, что это сервер. Операционная система компьютера не доверяет его сертификату безопасности. Возможно, сервер настроен неправильно или кто-то пытается перехватить ваши данные. NET:ERR_CERT_AUTHORITY_INVALID».

Дальше у Вас будет две кнопки «Не продолжать» и «Помогите мне разобраться» — нажимаем вторую ., а потом — «Перейти к 192.168.10.152 (небезопасно)»

Ну, а дальше уже Вас встретить знакомый Вам веб-интерфейс proxmox, где нужно вводить свои данные для авторизации — логин и пароль.

Если Вы используете иной браузер, то текст приведённого выше сообщения может быть другим, но суть и действия будут такими же.

это все мне известно, инсталляция не новая уже работала около года

1. Тогда показывайте логи Вашего proxmox

2. С других компьютеров сети такая же ситуация?

3. Какие у Вас правила в файерволе — доступ к proxmox через браузер только с определённого IP или что-то иное?!

вот например access.log

[21/08/201943 +0300] «GET / HTTP/1.1» 200 754
[21/08/201943 +0300] «GET /pve2/ext6/crisp/resources/charts-all.css HTTP/1.1» 200 995
[21/08/201943 +0300] «GET /pve2/ext6/theme-crisp/resources/theme-crisp-all.css HTTP/1.1» 200 68
[21/08/201943 +0300] «GET /pve2/js/pvemanagerlib.js?ver=5.2-1 HTTP/1.1» 304 —
[21/08/201943 +0300] «GET /pve2/ext6/locale/locale-en.js HTTP/1.1» 304 —
[21/08/201943 +0300] «GET /pve2/ext6/ext-all.js HTTP/1.1» 304 —
[21/08/201943 +0300] «GET /pve2/css/ext6-pve.css?ver=5.2-1 HTTP/1.1» 200 2814
[21/08/201943 +0300] «GET /pve2/fa/css/font-awesome.css HTTP/1.1» 200 7289
[21/08/201943 +0300] «GET /pve2/ext6/charts.js HTTP/1.1» 304 —
[21/08/201943 +0300] «GET /proxmoxlib.js?ver=1.0-18 HTTP/1.1» 304 —
[21/08/201944 +0300] «GET /pve2/ext6/theme-crisp/resources/theme-crisp-all_1.css HTTP/1.1» 200 33744
[21/08/201944 +0300] «GET /pve2/ext6/theme-crisp/resources/theme-crisp-all_2.css HTTP/1.1» 200 5208
[21/08/201944 +0300] «GET /pve2/images/logo-128.png HTTP/1.1» 200 4977
[21/08/201944 +0300] «GET /pve2/images/logo-128.png HTTP/1.1» 200 4977
[21/08/201944 +0300] «GET /PVE/StdWorkspace.js?_dc=1566371245735 HTTP/1.1» 501 —
[21/08/201955 +0300] «GET / HTTP/1.1» 200 754
[21/08/201955 +0300] «GET /pve2/ext6/theme-crisp/resources/theme-crisp-all.css HTTP/1.1» 200 68
[21/08/201955 +0300] «GET /pve2/ext6/theme-crisp/resources/theme-crisp-all_1.css HTTP/1.1» 200 33744
[21/08/201955 +0300] «GET /pve2/ext6/crisp/resources/charts-all.css HTTP/1.1» 200 995
[21/08/201955 +0300] «GET /pve2/fa/css/font-awesome.css HTTP/1.1» 200 7289
[21/08/201955 +0300] «GET /pve2/css/ext6-pve.css?ver=5.2-1 HTTP/1.1» 200 2814
[21/08/201955 +0300] «GET /pve2/ext6/locale/locale-en.js HTTP/1.1» 200 2569
[21/08/201955 +0300] «GET /pve2/ext6/theme-crisp/resources/theme-crisp-all_2.css HTTP/1.1» 200 5208
[21/08/201955 +0300] «GET /pve2/js/pvemanagerlib.js?ver=5.2-1 HTTP/1.1» 200 152085
[21/08/201955 +0300] «GET /pve2/ext6/ext-all.js HTTP/1.1» 200 609692
[21/08/201955 +0300] «GET /pve2/ext6/charts.js HTTP/1.1» 200 100383
[21/08/201955 +0300] «GET /proxmoxlib.js?ver=1.0-18 HTTP/1.1» 200 41451
[21/08/201956 +0300] «GET /pve2/images/logo-128.png HTTP/1.1» 200 4977
[21/08/201956 +0300] «GET /PVE/StdWorkspace.js?_dc=1566371257492 HTTP/1.1» 501 —
[21/08/201928 +0300] «GET / HTTP/1.1» 200 754
[21/08/201929 +0300] «GET /pve2/ext6/theme-crisp/resources/theme-crisp-all.css HTTP/1.1» 200 68
[21/08/201930 +0300] «GET /PVE/StdWorkspace.js?_dc=1566372550774 HTTP/1.1» 501 —

в принципе я это и так вижу в developers tools браузера, всё заканчивается так:

Источник

ProxMox web interface not running

Steijn van Essen

New Member

Here’s my 2nd post on this forum. Referring to my 1st post ‘Installation aborted’ dated June 21, 2011, I made quite some progress in getting ProxMox up and running, considering the fact that I was a rather newbie on Linux and totally unfamiliar with ProxMox.
Just for the record and maybe to help out other newbies I will add a summary of my findings for the last month to my 1st post, but for now I need some help with the following:

Following the suggestion from Tom on my 1st post I installed Debian Lenny 5.0.8, running the vmlinuz-2.6.26-2-amd64 kernel. Then following the instructions at

I came up to, but not including, the final step: connecting to the ProxMox web interface.

When I try to connect to https:// with my (Win XP) workstation’s web browser I get nothing and running ‘telnet 443’ returns ‘Cannot make connection with host on port 443: connection failed’.
When I ping I get replies and when I telnet to on port 44077 (see output below) I get some sort of black Telnet screen (normally indicating a running listener/deamon).

Having learned quite a lot about Linux by now I turn to my server console and enter ‘uname -a’ just to make sure. It returns

Concentrating on the TCP and UDP listeners for now I don’t include the list of domain sockets that follows.

Now, why don’t I see a TCP listener running on port 443?
Could it be the fact that the above weblink does not detail on what kind of services need to be included in the Debian install?
=> I only did a bare bones install (just the base system w/o any additional packages like graphical user desktop or web server)
=> oh, by the way, I don’t recall selecting LVM based partitioning, but is it necessary to run the
web interface?!
Could it be because I haven’t configured the FQDN for ‘My_ProxMox’ server in my DNS?
Or could it be because I skipped the optional step of installing ProxMox kernel headers (‘aptitude
install pve-headers-2.6.32-4-pve’)?

Could anybody perhaps help me find out why I don’t see the ProxMox web interface?

Awaiting your most appreciated reaction(s),

Famous Member

Following the suggestion from Tom on my 1st post I installed Debian Lenny 5.0.8, running the vmlinuz-2.6.26-2-amd64 kernel. Then following the instructions at

I came up to, but not including, the final step: connecting to the ProxMox web interface.

Having learned quite a lot about Linux by now I turn to my server console and enter ‘uname -a’ just to make sure. It returns

Concentrating on the TCP and UDP listeners for now I don’t include the list of domain sockets that follows.

Could anybody perhaps help me find out why I don’t see the ProxMox web interface?

Awaiting your most appreciated reaction(s),

For an newbie i’m recommend a original pve-installation (perhaps on a simple box — e.g. cheap amd-phenom).

Steijn van Essen

New Member

Thank you, Udo, for your reaction. So it seems that web support doesn’t automatically come with the ProxMox install on top of Debian and that Debian should have Apache running before I install ProxMox on top of it?!

With respect to your suggestion to try it on simpler hardware: I have two candidate old servers, one AMD K7-1200MHz based w Debian 32 bit already installed and one Intel P4-2000Mhz w Windows XP on it. But since the ProxMox Bare-metal ISO Installer only supports 64 bit CPUs (according to this thread: [thread=990]Proxmox-32-bit-OS[/thread]) this is not going to be of much help.
There is also the option of installing an unofficial 32 bit version of ProxMox on top of Debian Lenny 32 bit, but that that doesn’t brings me in a better position compared to where I am now. And given the spendings and efforts to build my current i7 6 core machine I consider buying another, albeit much cheaper, amd64 based system as an option of last resort.

So for now, I’ll try to get ProxMox reinstalled on Debian w Apache already installed and running.

Or would it be possible to add Apache (or any other additional service) to the current ProxMox install?

To be continued,

Famous Member

So for now, I’ll try to get ProxMox reinstalled on Debian w Apache already installed and running.

Or would it be possible to add Apache (or any other additional service) to the current ProxMox install?

To be continued,

install with «apt-get install apache2-mpm-prefork» and so on (do an «apt-get upgrade» before).

Steijn van Essen

New Member

Dear Udo (and other forum readers),

I was quite busy at the office and with other private matters, so it took some time for me to follow up your suggestions. Here’s my results:

I don’t remember actually trying «/etc/init.d/apache2 start». But I did install Apache2 on top of ProxMox. As a newbie it took me a couple of evenings to make it work for me. First only with HTTP, later on also with HTTPS. Learned a number of things about creating and self signing SSL certificates. When I connected to my server with my workstation’s browser, however, I got the default «It works!» page rather than the ProxMox configuration screen.

Then I created a new Debian installation (with a different host name to prevent from mixups between the two images) on another disk partition, arranged for some relevant contents in the /etc/hosts file (to make sure that this wouldn’t be part of the problem) and after that I first installed Apache2 with SSL certificates before I installed ProxMox on top of that. Unfortunately I saw no difference. That is, I run the ProxMox kernel but still get «It works!» when I «https://» from my workstation.
I mounted the original partition to my new partition to look for clues, but didn’t find much, really. I also used «find» to look for everything I could think of. One thing that puzzles me is that I don’t see any HTML pages (apart from documentation pages) that I could possible relate to the ProxMox web interface. So here’s my questions:

Does the ProxMox web interface really utilize Apache or does it come with a self contained web service?
And if it uses Apache, could anybody perhaps tell me what content Apache will present to anyone surfing to «https://IP_address_of_my_ProxMox_server»?! Where does Apache get its contents from? How does Apache come up with the ProxMox mangement interface?
And sorry I forgot about checking this before I started: is it likely/possible that Apache comes with the ProxMox-on-top-of-Lenny install if I don’t install it on Debian on beforehand?

Is there anyone who wants to just take a short look at his or her running ProxMox to find me some answers?

Famous Member

.
Does the ProxMox web interface really utilize Apache or does it come with a self contained web service?
And if it uses Apache, could anybody perhaps tell me what content Apache will present to anyone surfing to «https://IP_address_of_my_ProxMox_server»?! Where does Apache get its contents from? How does Apache come up with the ProxMox mangement interface?
And sorry I forgot about checking this before I started: is it likely/possible that Apache comes with the ProxMox-on-top-of-Lenny install if I don’t install it on Debian on beforehand?

Is there anyone who wants to just take a short look at his or her running ProxMox to find me some answers?

The website-content is below /usr/share/pve-manager/root

This is all in the package pve-manager — see «dpkg -L pve-manager»

Hope this helps.

Steijn van Essen

New Member

for giving me one more clue. The ‘pve-manager’ thing sure looks seriously helpfull. Hope to get back to you with some news soon.

Good night for now.

Steijn van Essen

New Member

Dear Udo (and other forum readers),

Just want you to know that I finally got PVE Manager running after two more weeks of trial and error. Never having seen a ‘live’ ProxMox environment I didn’t know where to look for, but the instructions and examples on Internet and the clues given by Udo helped me a lot.

Just FYI the prologue to this post:
— I originally tried to use the ProxMox install ISO booting from a USB key. Didn’t work.
— Then I changed to booting from an USB attached CD drive. Didn’t work.
— Then I ‘borrowed’ a SATA CD drive from my workstation and hooked it up to my server. This helped, but still I got “Installation aborted”.
— Then I followed the advice of forum member Tom to take a two step approach: install ProxMox on top of Debian Lenny (see my 1st post [thread=6553]Installation aborted[/thread]). I was able to install Debian and the ProxMox kernel on top of it, but didn’t get the management tools. This was the reason for my second (this) post.[/list]

So here’s my round up of what I did with Udo’s last clues:

Started reading about Apache and after feeling comfortable with that I installed the ‘ apache2-mpm-prefork ’ package. I rejected the default of ‘apache2-mpm-worker’ for I think this is overkill for just management of ProxMox. Prefork gave me at least TCP port 80 listening, but this is not a port used for web based manage¬ment of ProxMox. So I somehow needed to add at least port 443.
Started reading about Apache and SSL certificates, ‘ mod-ssl ’ and ‘ open-ssl ’. After feeling comfortable with that I issued the ‘ aptitude install openssl ssl-cert ’ command. Then I played with creating and storing keys and certificates (and self-signing them) and finally was able to get port 443 up and running and Apache’s default “It Works!” web page. Wow! But unfortunately, no PVE Manager interface.
I copied the ‘../proxmox/packages’ directory I found on the ProxMox installer CD to my hard disk. Then tried to get all kinds of packages installed (amongst them ‘ pve-manager ’). Then, after further investigation, I came to the conclusion that the ‘ proxmox-ve-2.6.32 ’ package contained all I needed (‘ aptitude -s install proxmox-ve-2.6.32 ’ enables you to learn about all the prompts you get and replies you should give during installing without actually doing the installation, thanks to the ‘-s’ option). After this you can run ‘aptitude -s install proxmox-ve-2.6.32 > apt_install_proxmox-ve’ and ‘more apt_install_proxmox-ve’ to learn at your own pace about all installation details (requirements, conflicts, suggestions, updates, removals, resulting actions). So, Udo, indeed: the ProxMox-on-top-of-Lenny install comes with everything you need and the Debian system underneath can be bare bones.
Having learned a lot about Aptitude and installing Debian and ProxMox by now, I copied a ‘fresh’ bare bones Debian install (I have four partitions on my SSD to make sure I always have one left for booting) to my ProxMox partition and then put all my efforts in getting the ‘ proxmox-ve-2.6.32 ’ package installed. After another week of struggling I desperately tried one more thing: comment out the following ‘deb’ lines in ‘ /etc/apt/sources.list ’:

This did the trick: all kinds of messages of unresolvable dependencies and virtual packages disappeared and ‘ aptitude install proxmox-ve-2.6.32 ntp ssh lvm2 ’ was now able to complete with far less disturbing messages.

So, where am I now?
Netstat shows a number of extra TCP listeners, like ‘www’, ‘ssh’ and ‘https’ and they all work as expected: I can do a Secure Telnet (using PuTTY from my Windows workstation) and also get the PVE Manager graphical interface when I surf to https:// .

My next moves will be:
— familiarize myself with PVE Manager and configuring and starting VM’s;
— get my 36 GB swap partition at the end of my SSD ‘swapped on’ to ProxMox to replace the current default swap file. 36 GB of swap should fit well with 24 GB of RAM;
— getting write permission from my ProxMox server on my NAS shares that currently tell me writing is not permitted;
— order some additional hardware, like an internal SATA CD drive and a second SSD. I want the second SSD for three reasons, noting that I want to support quite a number of VMs and projects on top of ProxMox: (1) for flexibility in ProxMox maintenance and minimizing downtime, (2) as a backup in case of SSD hardware failure and (3) to be able to change ProxMox boot and swap partitions on a regular bases to increase SSD lifetime (SSDs can only handle 1M I/Os or so to the same memory cells). And have a look at file systems that optimize SSD lifetime and performance;
— further familiarize myself with Debian, OpenSuse and Windows running in VM’s;
— a virtualized IPv6 network between the VMs, to be extended into Internet (I’m changing to an IPv6 provider in a couple of weeks);
— getting hands-on experience with all kinds of IPv6 networking matters (DNS, hosting, etc).

Thanx again, all of you and no doubt we’ll meet again on this forum.

Источник