Proxmox ошибка входа попробуйте еще раз

[SOLVED] Proxmox VE — Login failed. Please try again.

Punkjob

New Member

Proxmox Staff Member

Best regards,
Mira

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

Punkjob

New Member

john2151

New Member

Hi,
fairly new user of Proxmox here, but already love it!

I’m having the same issue, but i’m not exactly sure since when, because the cluster is fairly new.
First node is down at the moment (creator of the cluster) and on node 2 i can’t log in anymore.
It definitely worked in the beginning.

/var/log/auth.log only has entries if the password is wrong:
Dec 8 21:09:26 dl380 IPCC.xs[2015]: pam_unix(proxmox-ve-auth:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=root

root@pam also doesn’t work, but doesn’t create an auth.log entry either.

There were no authentication methods added, so just PAM and PVE-Authentication-Server, but neither of them work.

All Proxmox packages are the latest non-subscription version and the server was installed from the latest Proxmox ISO.

cat /etc/pve/user.cfg
user:root@pam:1:0. it@mail.

If additional files or info is required, i’d be glad to provide it.

Thanks in advance!

john2151

New Member

Just figured out my problem.

The node that was shut down, caused the Cluster to drop below the quorum limit.
Such that the node entered a read-only mode and no VMs or CTs were started and the Web GUI was inaccessible.
pvecm expected 1 fixed that and the GUI became accessible again.

Question: Is that an expected reaction on losing a cluster node?
If yes, i don’t really understand why and how high availability can be achieved if the remaining cluster node is made useless by losing another node?

Edit: Also the VMs and CTs couldn’t be started via CLI. That’s how i stumbled upon the loss of quorum.

Proxmox Staff Member

Best regards,
Mira

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

uiffiu

Member

I can confirm, login failed to webgui on the remaining node. have a cluster of 2 nodes.
I can not say since when the problem persist, I just discovered it like 10 minutes ago. Usually I stay logged in when one node reboots.

proxmox-ve: 7.1-1 (running kernel: 5.13.19-2-pve) pve-manager: 7.1-8 (running version: 7.1-8/5b267f33) pve-kernel-helper: 7.1-6 pve-kernel-5.13: 7.1-5 pve-kernel-5.11: 7.0-10 pve-kernel-5.13.19-2-pve: 5.13.19-4 pve-kernel-5.13.19-1-pve: 5.13.19-3 pve-kernel-5.11.22-7-pve: 5.11.22-12 pve-kernel-5.11.22-5-pve: 5.11.22-10 pve-kernel-5.11.22-4-pve: 5.11.22-9 ceph-fuse: 15.2.14-pve1 corosync: 3.1.5-pve2 criu: 3.15-1+pve-1 glusterfs-client: 9.2-1 ifupdown2: 3.1.0-1+pmx3 ksm-control-daemon: 1.4-1 libjs-extjs: 7.0.0-1 libknet1: 1.22-pve2 libproxmox-acme-perl: 1.4.0 libproxmox-backup-qemu0: 1.2.0-1 libpve-access-control: 7.1-5 libpve-apiclient-perl: 3.2-1 libpve-common-perl: 7.0-14 libpve-guest-common-perl: 4.0-3 libpve-http-server-perl: 4.0-4 libpve-storage-perl: 7.0-15 libspice-server1: 0.14.3-2.1 lvm2: 2.03.11-2.1 lxc-pve: 4.0.11-1 lxcfs: 4.0.11-pve1 novnc-pve: 1.2.0-3 proxmox-backup-client: 2.1.2-1 proxmox-backup-file-restore: 2.1.2-1 proxmox-mini-journalreader: 1.3-1 proxmox-widget-toolkit: 3.4-4 pve-cluster: 7.1-2 pve-container: 4.1-3 pve-docs: 7.1-2 pve-edk2-firmware: 3.20210831-2 pve-firewall: 4.2-5 pve-firmware: 3.3-3 pve-ha-manager: 3.3-1 pve-i18n: 2.6-2 pve-qemu-kvm: 6.1.0-3 pve-xtermjs: 4.12.0-1 qemu-server: 7.1-4 smartmontools: 7.2-1 spiceterm: 3.2-2 swtpm: 0.7.0

rc1+2 vncterm: 1.7-1 zfsutils-linux: 2.1.1-pve3

Источник

«Login Failed»

sigma

New Member

Hi ! I need help. My Proxmox web interface stopped recognizing me with a «LOGIN FAILED» message.

I have a single computer, running proxmox latest version pre 4.0 with only two virtual machines inside.

It began with the following symptom: Some hours ago my two virtual machines started appearing «off» (monitors in black) on the web interface (but they were working just fine). All performance graphs had nothing being graphed on them.

Some minutes later, the whole web interface refreshed into the PROXMOX VE LOGIN window.

From that moment on, my password did not log me into Proxmox web interface anymore. But I can log as root with no problems at all on SSH shell.

I had no firewall ON, did not install anything prior to this behavior, nothing it has been working fine for years, and suddenly this problem. I am totally baffled about this.

Any suggestion or idea is very much welcome. This is a production server, and since the virtual machines are working just fine, I had no chance yet to perform a reset on the barebone server that runs proxmox.

pveversion -v returns the following:

proxmox-ve-2.6.32: 3.4-165 (running kernel: 2.6.32-42-pve)
pve-manager: 3.4-11 (running version: 3.4-11/6502936f)
pve-kernel-2.6.32-40-pve: 2.6.32-160
pve-kernel-2.6.32-39-pve: 2.6.32-157
pve-kernel-2.6.32-41-pve: 2.6.32-164
pve-kernel-2.6.32-42-pve: 2.6.32-165
pve-kernel-2.6.32-38-pve: 2.6.32-155
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-3
pve-cluster: 3.0-19
qemu-server: 3.4-6
pve-firmware: 1.1-4
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-33
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.2-11
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1

wolfgang

Proxmox Retired Staff

Hi,
I’m a little confused about your settings you wrote you have PVE4.0 but your pveversion -v tell us you run 3.4?

try to flush the browser cache.
restart pveproxy

Best regards,
Wolfgang

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

sigma

New Member

I am sorry I was not clear enough: As I stated, I have the latest proxmox version PRE 4.0 (before 4.0). The first thing I did when this started happening to me was getting into this forum and searching for similar cases (before posting anything). So I already did a flush of the browser cache, and even tried different browsers. Also tried to restart pveproxy.

The behavior is still the same: I am left out of the web interface! I am mildly panicking, since I am not that proficient on linux administration, as to manage (backup, check usage, etc.) my proxmox through command line.

wolfgang

Proxmox Retired Staff

Do you have OpenVz container to?

What output you get from

cat /etc/hosts
cat /etc/network/interfaces ifconfig
service pveproxy status

Best regards,
Wolfgang

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

sigma

New Member

I am not using OpenVz as VM engine.

# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
X.X.X.194 proxmox.avalle.net proxmox pvelocalhost

# The following lines are desirable for IPv6 capable hosts

ip6-localhost ip6-loopback
ip6-localnet
ip6-mcastprefix
ip6-allnodes
ip6-allrouters
ip6-allhosts

# cat /etc/network/interfaces ifconfig
auto lo
iface lo inet loopback

auto vmbr0
iface vmbr0 inet static
address X.X.X.194
netmask 255.255.255.224
gateway X.X.X.193
bridge_ports eth0
bridge_stp off
bridge_fd 0
cat: ifconfig: No such file or directory

# service pveproxy status
Usage: /etc/init.d/pveproxy

Since that last command had no status parameter, but I could see the available parameters, I did just try the following:

# /etc/init.d/pveproxy force-reload
Restarting PVE API Proxy Server: pveproxy.

And tried again to log into the administrator web interface, but I keep getting the same: Login Failed. Please try again.

Thanks very much Wolfgang for your help. Hopefully this walk-through looking for a solution can be useful for other persons.

wolfgang

Proxmox Retired Staff

Best regards,
Wolfgang

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

sigma

New Member

Yes, I supposed too it would look ok, as I never changed anything. This happened with no apparent reason. It worked fine for years, until now.

I am using, yes Linux PAM (although I did try PVE Authentication, just in case) as log in realm.

I just paid an anual subscription for Proxmox (I could afford only the community subscription). I know it is a minimal gesture, and it was long due for me to at least jump into it.

I understand that the community subscription does not entitle me for real ticket support, or anything like that.

Anyway, if there is any other suggestion or test for me to try, I am closely reading this thread, for the next hours.

wolfgang

Proxmox Retired Staff

try to reinstall the manager and change the password

apt-get update && apt-get install pve-manager

Best regards,
Wolfgang

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

sigma

New Member

I have a (great) partial success:

I had to issue the following commands:

apt-get update
apt-get remove pve-manager
apt-get install pve-manager

I regained access to web interface. But, virtual machines appear just as right before loosing access yesterday: «Powered off». Also all server graphs have nothing plotted on them (but VM are working fine).

. At this time I am kind of tempted of backing up my two VM and try to do Proxmox 4 upgrade.

wolfgang

Proxmox Retired Staff

Best regards,
Wolfgang

Do you already have a Commercial Support Subscription? — If not, Buy now and read the documentation

sigma

New Member

I have everything working now. I stopped my two virtual machines and issued a reboot command on the proxmox ssh linux shell.

Thank you very much for your directions, Wolfgang!

Right now I am backing up both VM, just in case, and tomorrow I will try to upgrade proxmox into version 4.0

sigma

New Member

Sorry to «reopoen» this thread: The problem depicted in here kept happening to me. Now I am up to date with Proxmox version 4. Always the same:

After rebooting proxmox server and everything working ok for several days, first I wake up into a web interface depicting my virtual machines powered off, no cpu / bandwitdth graphs active, but the «Status» panel (the upper panel showing the Uptime, load, cpu,io, ram, swap usage, etc. in text mode) is still being refreshed and showing what seems to be the correct values.

If at this time, I logoff from the web interface, then there is no way to log in again, as stated on my first post.

This is haunting me big time, and I would rather NOT reset my server only to regain proper web interface usage!!

perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_CTYPE = «UTF-8»,
LANG = «es_UY.UTF-8»
are supported and installed on your system.
perl: warning: Falling back to a fallback locale («es_UY.UTF-8»).

proxmox-ve: not correctly installed (running kernel: 4.2.3-2-pve)
pve-manager: 4.1-5 (running version: 4.1-5/f910ef5c)
pve-kernel-2.6.32-43-pve: 2.6.32-166
pve-kernel-4.2.2-1-pve: 4.2.2-16
pve-kernel-4.2.3-2-pve: 4.2.3-22
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 0.17.2-1
pve-cluster: 4.0-30
qemu-server: 4.0-46
pve-firmware: 1.1-7
libpve-common-perl: 4.0-43
libpve-access-control: 4.0-11
libpve-storage-perl: 4.0-38
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.4-21
pve-container: 1.0-37
pve-firewall: 2.0-15
pve-ha-manager: 1.0-18
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-5
lxcfs: 0.13-pve3
cgmanager: 0.39-pve1
criu: 1.6.0-1

I don’t know if it is related, but when inspecting the Syslog, around the time I suspect everything goes berzerk, I find a flood of lines like these:

Источник

proxmox 4.1-22 не могу авторизоваться через WEB, по ssh пускает

на сервере ничего не делал
пользователем root по ssh пускает через web не пускает.
ребут сервера не помог
что делать?

Вы не можете попасть на страницу авторизации или не можете на ней залогиниться?

конечно по этому адресу лежит. не могу залогиниться/авторизоваться через web

залогиниться не могу

При попытке авторизоваться что происходит? Пишет неверный пароль, кидает на белый экран. В логах pve что пишет?

Окошко с «Login failed. Please try again»
логи pve — сорри а это где посмотреть?

Тип авторизации выбран PAM?

да PAM
в этом файле только строчки от CRON и sshd
при попытке залогиниться в этот файл ничего не попадает

Охренеть.
попробовал из firefox залогиниться — залогинился )).
но как это объяснить — ХЗ.
у меня есть второй сервер с точно таким же proxmox и на него логинился нормально из хрома, а на первый не могу логиниться из хрома.

С кэшем траблы возникать могут не только при логине.

как почистить кэш?

ну, если хром, ctrl+h, и там Clear browsing data

Источник

Today we have a quick fix to a Proxmox VE cluster login issue. When you try logging into a Proxmox VE node, it can give you a “Login failed. Please try again” message even if you are using the correct credentials. This can happen when a cluster’s health is less than 100%, so we wanted to show what causes it and the quick fix to let you log in.

Here is the Error Login failed. Please try again screen that you see on a node that is running, but within the context of a failed cluster. This Error was generated even when supplying the correct user name, password, and ream. VMs on the node were operating normally as well.

The reason for this is that the cluster is in a degraded state. We created this state while decomissioning a 7-node PVE cluster. With only 3 of 7 nodes online, we did not have a quorum and so even local node authentication was failing.

If you search online, you will find “pvecm expected 1” as the fix, fooling the Proxmox VE cluster into thinking you have quorum. This typically works on 3-node clusters, but as the cluster size increases, it does not work.

Here is the cluster where we can see that we have a 7-node cluster meaning to get a majority of nodes, or a quorum, we need four nodes. As we were taking down the nodes, we had four offline already, and not removed from the cluster. That meant that only 3 of 7 nodes were online and that is not enough for a quorum.

Instead of pvecm expected 1, we can use “pvecm expected 3” to match the three nodes online here, and that again gives us quorum. The expected votes/ highest expected are then 3, and the quorum is then two. With three nodes online, and an exptected value of three, we are able to quorate.

Once this is done, we are able to login to Proxmox VE normally.

Final Words

This is not going to be the most common issue, but is one where the current online guides lead you only to the small cluster answer, rather than one that can work for larger clusters. Ideally, our readers only run into this when taking down a cluster. As a result, we wanted to document the fix for those who run into it in the future. It can be a strange feeling to get an error that the login has failed even when using the correct username/ password. Hopefully this helps.

The error ‘Login to Proxmox host failed’ can happen in different scenarios:

1. When you try to access the Proxmox VE management console directly
2. While integrating a third party module such as WHMCS into your Proxmox server
3. During the management of a cluster of Proxmox nodes

Proxmox would just say “Login failed, please try again” and you may have no idea what went wrong.

Today we’ll see the 4 main reasons why we come across ‘login to Proxmox host failed’ error during our Outsourced Web Hosting Support services and how we fix each of them.

1. Login failed due to SSL problems

The default URL to access the Proxmox VE management console is https://IPaddress:8006/ . If you try to access it without secure protocol, the console will not load.

At times, when the SSL certificate has expired, there maybe issues accessing the Proxmox node. In some cases, a bug with Proxmox cause it not to detect the SSL settings.

To fix SSL issues, first confirm that the certificate has not expired and is working fine. If all fine, execute this command in the Proxmox machine:

pvecm updatecerts --force

This command will update and fix the issues related to Proxmox SSL certificate and you’d be able to access the node fine.

2. Firewall rules causing login failures

Firewall rules in the Proxmox node can cause login failures. While firewalls are important to secure a server, configuring the rules correctly is vital for proper server functioning.

Proxmox VE 4.x and later uses the following ports:

• Web interface at port 8006
• pvedaemon (listens only on 127.0.0.1) at port 85
• SPICE proxy at port 3128
• sshd at port 22
• rpcbind at port 111

In Proxmox servers where firewalls such as iptables is used, specifically allow these ports for proper functioning of the Proxmox server.

To allow the Proxmox ports, firewall rules have to be added in the Proxmox server for the corresponding ports:

For proper internal communication in the Proxmox server, a rule to accept loop-back interface connection should also be added.

In the case of third party modules such as WHMCS, Modulegarden, etc., it is important to ensure that the connectivity is proper between the two servers.

Use telnet command to check the connectivity to Proxmox node from the module server. This helps to know if the login failure is due to any connectivity problems.

Flushing the firewalls fully may resolve connectivity problems, but its not advisable for server security. That makes it important to allow the required connections while denying everything else.

3. Login errors due to incorrect server time

Most servers rely on NTP service to update their server time zone. At times, the NTP server can fail to sync the server time due to connectivity issues or other service related errors.

It can also happen that the server time gets changed to a different time zone, especially in cases when the Proxmox machine is migrated to a different one.

In such cases, the lack of clock synchronization can lead to incorrect server time for the Proxmox installation and login failures.

Proper clock synchronization in the Proxmox server is crucial for its smooth functioning. Fixing the NTP server and keeping the server time updated, would help fix the login errors.

4. Failed to login due to password issues

To access the Proxmox VE management console, use the same login / password of your proxmox shell defined during your proxmox installation.

While it is advisable to use strong passwords for security, it is also noticed at times that too complicated passwords with a lot of special characters can cause login issues.

Password issues can happen be due to some bug with the Proxmox authentication module used to validate the login details.

So if none of the above mentioned fixes work, then its a good move to try resetting the node passwords to simpler ones and try to login.

Read: Proxmox change IP address in 3 simple steps

In short..

Here we saw the main four reasons why login to Proxmox node fails and how to fix them. Performing each fix should be done with caution to avoid any mess up.

Login to Proxmox host failed errors can also happen due to various other reasons, ranging from browser cookies to issues with the storage devices.

We also give recommendations to server owners on how to manage their server resources effectively. If you’d like to know how to do it for your servers, we’d be happy to talk to you.

Read: How to add multiple IP addresses in Proxmox LXC containers

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

Bobcares provides Outsourced Hosting Support for online businesses. Our services include Outsourced Web Hosting Support, Outsourced Server Support, Outsourced Help Desk Support, Outsource Live Chat Support and Phone Support Services.