[SOLVED] error 1006

Arthur Ferraz

Member
Aug 4, 2022
35
0
6
im getting this error while trying to access node console vm working fine

client connection: [::1]:37744
[7] Couldn't connect to server (Failed to connect to localhost port 85: Connection refused)
TASK ERROR: command '/usr/bin/termproxy 5900 --path /nodes/alvesfnds --perm Sys.Console -- /bin/login -f root' failed: exit code 1
 
hi,

do you have multiple nodes in a cluster?

please check the /etc/hosts file and make sure that all your nodes IPs are in there correctly
 
hi,

do you have multiple nodes in a cluster?

please check the /etc/hosts file and make sure that all your nodes IPs are in there correctly
this happened after i tried to change the node name if it helps
 

Attachments

  • Capturar.PNG
    Capturar.PNG
    5.6 KB · Views: 219
did you follow [0] ?

also on your screenshot i see a "t" before the IP address 127.0.0.1 which seems wrong and could be problematic too

ok i fixed that, now there is one more thing, how can i back to acces my vm via remote desktop ?
 
ok i fixed that, now there is one more thing, how can i back to acces my vm via remote desktop ?

if the issue is fixed please mark the thread as [SOLVED] :)

for accessing your VM via remote desktop you'd have to check a couple of things:
* network topology
* firewall settings
* if RDP service is running on the VM *and that your credentials are working

but i'd suggest to open a new thread and explain where you're getting stuck :)
 
if the issue is fixed please mark the thread as [SOLVED] :)

for accessing your VM via remote desktop you'd have to check a couple of things:
* network topology
* firewall settings
* if RDP service is running on the VM *and that your credentials are working

but i'd suggest to open a new thread and explain where you're getting stuck :)
ty for the help
 
When you browse shell/console/vnc etc from your browser, it use websocket (wss) connection. So when you configure a reverse proxy to access your proxmox server then you must enable websocket support in your proxy server settings.

In my case I used apache reverse proxy.

First enable mod_proxy_wstunnel by command:

Bash:
sudo a2enmod proxy_wstunnel
sudo systemctl restart apache2


Apache ssl config:


ServerName ****.com
ServerAlias www.****.com
DirectoryIndex index.php index.htm index.html
<Directory /home/******/public_html>
Options -Indexes +IncludesNOEXEC +SymLinksIfOwnerMatch
Require all granted
AllowOverride All Options=ExecCGI,Includes,IncludesNOEXEC,Indexes,MultiViews,SymLinksIfOwnerMatch
AddType text/plain .php
</Directory>
<Directory /home/****/cgi-bin>
Require all granted
AllowOverride All Options=ExecCGI,Includes,IncludesNOEXEC,Indexes,MultiViews,SymLinksIfOwnerMatch
</Directory>
ProxyPass /.well-known !
RewriteEngine on
SSLProxyVerify none
SSLProxyCheckPeerCN off
SSLProxyCheckPeerName off
SSLProxyCheckPeerExpire off
ProxyPass / https://192.168.10.80:8006/
ProxyPassReverse / https://192.168.10.80:8006/

SSLProxyEngine on
SSLEngine on
SSLCertificateFile /home/*********/ssl.combined
SSLCertificateKeyFile /home/********/ssl.key
SSLCACertificateFile /home/*******/ssl.ca
SSLProtocol all -SSLv2 -SSLv3 -TLSv1 -TLSv1.1

RewriteCond %{HTTP:Upgrade} websocket [NC]
RewriteRule /(.*) wss://192.168.10.80:8006/$1 [P]
 
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!