Connect failed: connect: Connection refused; Connection refused (500)

bread-baker

Member
Mar 6, 2010
432
0
16
Connect failed: connect: Connection refused; Connection refused (500) *SOLVED*

this issue was solved by running
Code:
pvecm updatecerts

see 2-nd post.
---
Hello
I have a server which had been running Proxmox 2.0 since December. according to aptitude logs it originally had proxmox-ve-2.6.32 2.0-53 . the node name is fbc241 .

Today I backed up and removed the vm's and added fbc241 to the cluster. here is pvecm status and nodes:

Code:
fbc241 s012 /var/log # pvecm nodes
Node  Sts   Inc   Joined               Name
   1   M    196   2012-04-16 06:38:08  s009
   2   M    196   2012-04-16 06:38:08  fbc246
   3   M    196   2012-04-16 06:38:08  s002
   4   M    188   2012-04-16 06:37:42  fbc241

fbc241 s012 /var/log # pvecm status
Version: 6.2.0
Config Version: 19
Cluster Name: fbcluster
Cluster Id: 52020
Cluster Member: Yes
Cluster Generation: 196
Membership state: Cluster-Member
Nodes: 4
Expected votes: 4
Total votes: 4
Node votes: 1
Quorum: 3  
Active subsystems: 5
Flags: 
Ports Bound: 0  
Node name: fbc241
Node ID: 4
Multicast addresses: 239.192.203.0 
Node addresses: 10.100.100.241

The problem is on the pve screen, when I try to click on fbc241 this error displays:
"Connect failed: connect: Connection refused; Connection refused (500) "

Other issues:
from other nodes ' ssh fbc241 ' requires a password, even when trying 'ssh-copy-id ' .

/root/.ssh/ :has
authorized_keys -> /etc/pve/priv/authorized_keys

but if I copy the original authorized_keys back ssh login does not need a password.

In the past when I ran into this problem a reinstall is the only solution I could find.

But it would be good to try to fix this issue incase anyone else runs in to the problem.


Any suggestions?


ps: thank you for the great Proxmox PVE system.
 
Last edited:
after checking other threads :

Code:
ls -l /etc/pve/local/pve-ssl.pem
ls: cannot access /etc/pve/local/pve-ssl.pem: No such file or directory

pvecm updatecerts
fbc241 s012 ~ # ls -l /etc/pve/local/pve-ssl.pem                                                                                      
-rw-r----- 1 root www-data 1363 Apr 16 08:36 /etc/pve/local/pve-ssl.pem

still get the error. try rebooting node fbc241

that fixed pve access. the connection error is gone.

but ssh logins are not ok:
Code:
root@fbc1 /home/rob/Downloads # ssh-copy-id fbc241
root@fbc241's password: 
Now try logging into the machine, with "ssh 'fbc241'", and check in:

  .ssh/authorized_keys

to make sure we haven't added extra keys that you weren't expecting.
# 
# then try to log in, but password is still needed:
ssh fbc241
root@fbc241's password:
 
the ssh issue had something to do with the old server running one of our cronscripts which was ok for non cluster setup.
 
Last edited:

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!