can't access Proxmox Backup Server on Proxmox VE

PaulVM

Renowned Member
May 24, 2011
102
3
83
I have a test PVE box That I use as backup/spare.
Reading of the new PBS since some month ago I decided to try an install following the
instructions for "Proxmox Backup Server on Proxmox VE" (https://pbs.proxmox.com/docs/installation.html#install-proxmox-backup-server-on-proxmox-ve).
Update PVE and Installed PBS without problems (seems), but when I try to login to the PBS GUI ( host:8007 ) I cant' authenticate.
I still can authentivate without problems to the PVE GUI (host:8006).
I am using the same credentials (root / pwd).
Am I missing something?

Thanks, P.

 
I think it is a little different situation. I can't neither log in to :8007
Anyway, tried to replace "localhost" with "127.0.0.1" in /etc/pve/storage.cfg (odd bug if present), but the situation is unchanged.

Thanks, P.
Hi,
the bug regarding PVE storage authentication has been fixed with libpve-storage-perl 6.3-3.
Check if you are using the correct realm for login (Linux PAM in your case).
If that's not it, can you connect to your host using ssh and check for errors with journalctl -f while trying to log in via the WebUI?
 
Hi,
the bug regarding PVE storage authentication has been fixed with libpve-storage-perl 6.3-3.
Check if you are using the correct realm for login (Linux PAM in your case).

# apt info libpve-storage-perl
Package: libpve-storage-perl
Version: 6.3-3
Priority: optional
Section: perl
Maintainer: Proxmox Support Team <support@proxmox.com>
Installed-Size: 498 kB
. . .

I usually authenticate using Linux PAM as realm.
Tried also P. B. Authentication server just in case ... ;-)

If that's not it, can you connect to your host using ssh and check for errors with journalctl -f while trying to log in via the WebUI?

A few rows (including some "hack" attempts"):

Dec 08 16:51:00 pm005 systemd[1]: Starting Proxmox VE replication runner...
Dec 08 16:51:01 pm005 systemd[1]: pvesr.service: Succeeded.
Dec 08 16:51:01 pm005 systemd[1]: Started Proxmox VE replication runner.
Dec 08 16:51:01 pm005 sshd[15142]: Bad protocol version identification 'POST /api2/extjs/access/ticket HTTP/1.1' from 127.0.0.1 port 60080
Dec 08 16:51:03 pm005 sshd[15166]: Bad protocol version identification 'POST /api2/extjs/access/ticket HTTP/1.1' from 127.0.0.1 port 60082
Dec 08 16:51:06 pm005 sshd[15167]: Bad protocol version identification 'POST /api2/extjs/access/ticket HTTP/1.1' from 127.0.0.1 port 60084
Dec 08 16:51:08 pm005 sshd[15169]: Bad protocol version identification 'POST /api2/extjs/access/ticket HTTP/1.1' from 127.0.0.1 port 60086
Dec 08 16:51:42 pm005 sshd[15241]: Invalid user jenkins from 119.29.177.222 port 44450
Dec 08 16:51:42 pm005 sshd[15241]: pam_unix(sshd:auth): check pass; user unknown
Dec 08 16:51:42 pm005 sshd[15241]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.177.222
Dec 08 16:51:43 pm005 sshd[15266]: Bad protocol version identification 'POST /api2/extjs/access/ticket HTTP/1.1' from 127.0.0.1 port 60088
Dec 08 16:51:43 pm005 sshd[15241]: Failed password for invalid user jenkins from 119.29.177.222 port 44450 ssh2
Dec 08 16:51:44 pm005 sshd[15241]: Received disconnect from 119.29.177.222 port 44450:11: Bye Bye [preauth]
Dec 08 16:51:44 pm005 sshd[15241]: Disconnected from invalid user jenkins 119.29.177.222 port 44450 [preauth]
Dec 08 16:51:46 pm005 sshd[15273]: Invalid user subir from 162.243.91.84 port 53086
Dec 08 16:51:46 pm005 sshd[15273]: pam_unix(sshd:auth): check pass; user unknown
Dec 08 16:51:46 pm005 sshd[15273]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.243.91.84
Dec 08 16:51:46 pm005 sshd[15275]: Bad protocol version identification 'POST /api2/extjs/access/ticket HTTP/1.1' from 127.0.0.1 port 60090
Dec 08 16:51:47 pm005 sshd[15273]: Failed password for invalid user subir from 162.243.91.84 port 53086 ssh2
Dec 08 16:51:49 pm005 sshd[15273]: Received disconnect from 162.243.91.84 port 53086:11: Bye Bye [preauth]
Dec 08 16:51:49 pm005 sshd[15273]: Disconnected from invalid user subir 162.243.91.84 port 53086 [preauth]
Dec 08 16:51:50 pm005 sshd[15277]: Bad protocol version identification 'POST /api2/extjs/access/ticket HTTP/1.1' from 127.0.0.1 port 60092
Dec 08 16:52:00 pm005 systemd[1]: Starting Proxmox VE replication runner...
Dec 08 16:52:01 pm005 systemd[1]: pvesr.service: Succeeded.
Dec 08 16:52:01 pm005 systemd[1]: Started Proxmox VE replication runner.

I think the only relevants rows are those that seems generated at every my auth attempt:

Dec 08 16:56:13 pm005 sshd[15985]: Bad protocol version identification 'POST /api2/extjs/access/ticket HTTP/1.1' from 127.0.0.1 port 60096
Dec 08 16:56:16 pm005 sshd[15992]: Bad protocol version identification 'POST /api2/extjs/access/ticket HTTP/1.1' from 127.0.0.1 port 60098
Dec 08 16:56:19 pm005 sshd[15994]: Bad protocol version identification 'POST /api2/extjs/access/ticket HTTP/1.1' from 127.0.0.1 port 60100
Dec 08 16:56:24 pm005 sshd[16018]: Bad protocol version identification 'POST /api2/extjs/access/ticket HTTP/1.1' from 127.0.0.1 port 60102

If I revert 127.0.0.1 to localhost in /etc/pve/storage.cfg and reboot nothing change:

Dec 08 17:07:00 pm005 systemd[1]: Starting Proxmox VE replication runner...
Dec 08 17:07:01 pm005 systemd[1]: pvesr.service: Succeeded.
Dec 08 17:07:01 pm005 systemd[1]: Started Proxmox VE replication runner.
Dec 08 17:07:01 pm005 sshd[2106]: Did not receive identification string from 127.0.0.1 port 45916
Dec 08 17:07:17 pm005 sshd[2160]: Bad protocol version identification 'POST /api2/extjs/access/ticket HTTP/1.1' from 127.0.0.1 port 45918
Dec 08 17:07:23 pm005 sshd[2184]: Bad protocol version identification 'POST /api2/extjs/access/ticket HTTP/1.1' from 127.0.0.1 port 45920
Dec 08 17:07:26 pm005 sshd[2185]: Bad protocol version identification 'POST /api2/extjs/access/ticket HTTP/1.1' from 127.0.0.1 port 45922
Dec 08 17:07:34 pm005 sshd[2210]: Bad protocol version identification 'POST /api2/extjs/access/ticket HTTP/1.1' from 127.0.0.1 port 45924
Dec 08 17:07:47 pm005 sshd[2235]: Bad protocol version identification 'POST /api2/extjs/access/ticket HTTP/1.1' from 127.0.0.1 port 45926
Dec 08 17:07:50 pm005 sshd[2236]: Bad protocol version identification 'POST /api2/extjs/access/ticket HTTP/1.1' from 127.0.0.1 port 45928

Thanks, P.
 
??? Seems that your sshd is receiving HTTP traffic from an API client? What port is your sshd listening on, what port PBS? ss -tulpen | grep -E "proxmox|sshd"
Also it is not recomeded to post public IPs contained in log files (please retract them).
I was expecting log outputs of failed auth from proxmox-backup-proxy, please check that it is up and running with systemctl status proxmox-backup proxmox-backup-proxy.
 
  • Like
Reactions: PaulVM
??? Seems that your sshd is receiving HTTP traffic from an API client? What port is your sshd listening on, what port PBS? ss -tulpen | grep -E "proxmox|sshd"
Also it is not recomeded to post public IPs contained in log files (please retract them).
I was expecting log outputs of failed auth from proxmox-backup-proxy, please check that it is up and running with systemctl status proxmox-backup proxmox-backup-proxy.

I had sshd listening on port 82.
Changed the port and now I can log into PBS
Seems this solve my first PBS problem and now I can start play ... ;-)

Thanks, P.
 
I had sshd listening on port 82.
Changed the port and now I can log into PBS
Seems this solve my first PBS problem and now I can start play ... ;-)

Thanks, P.
Yep, that was your problem proxmox-backup-api is listening on port 82...
 
;-)
Now I also know this ;-)

20 years ago sshd on port 82 was fine. recently not so much ;-)

Thanks, P.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!