undefined (Code: 1006) when using GUI Node console in domains (Using GUI IP works fine)

S

Skyrider

Active Member
May 11, 2020
55
1
28
38
So I've created a subdomain for my Proxmox GUI, and it's working nicely. I did however notice that every time I attempt to use the console within the proxmox gui (either the main server console or node consoles), I get the message "undefined (Code: 1006)" on the console screen. But when I use the console through the Gui IP address (rather than the sub-domain), the console is working as it should.

Any idea as to why this is?

Regards,
Skyrider
 
hi,

you should adapt the /etc/hosts file to reflect the subdomain
 
Thanks for the reply! And sorry for the delay.

The hosts file is actually reflecting my servers ip / subdomain.

IP subdomain hostname

Still having the same issue (even after a server restart)
 
check /etc/hostname file as well.

is this PVE part of a cluster or standalone node?
 
Thanks for replying!

1660127327333.png
And hostname --fqdn confirms it as well that it's set right.

And it's a standalone node.
 
Last edited:
Skyrider said:
Thanks for replying!

View attachment 39852
And hostname --fqdn confirms it as well that it's set right.

And it's a standalone node.
Click to expand...
are you using maybe reverse proxy such as nginx proxy manager? Also, are you using SSL for internal domains? Note, not external SSL such as from Let's Encrypt etc. I mean that you are the CA of the SSL in order to access the Web GUI through the domain name?
 
stanikz said:
are you using maybe reverse proxy such as nginx proxy manager? Also, are you using SSL for internal domains? Note, not external SSL such as from Let's Encrypt etc. I mean that you are the CA of the SSL in order to access the Web GUI through the domain name?
Click to expand...
Yes I am actually, to both. (Reverse Proxy & Lets Encrypt SSL). That does really matter that much that I'm not using an internal SSL?
 
Skyrider said:
Yes I am actually, to both. (Reverse Proxy & Lets Encrypt SSL). That does really matter that much that I'm not using an internal SSL?
Click to expand...
I guess you didn't get my question, sorry for not being so clear. If you are using nginx proxy manager (npm), in case you're using external domain and SSL from Let's Encrypt that shouldn't be that hard at all. In case you're using it with your own created certificate and you are the CA and hold a wildcard cert. Then its important that websockets support is checked as in two lowest figures (section -> For internal domain).

Here I have two npm instances, one for internal domain names and one for external. I can choose to use either the internal domain name to access the webui with my own wildcard SSL cert as well as external with my wildcard SSL from Cloudflare. Hope this can solve your problem.

For external domain
SSL-with-LetsEncrypt1.pngSSL-with-LetsEncrypt2.png

For internal domain name (LAN)
SSL-without-LE-for-internaldomain1.pngSSL-without-LE-for-internaldomain2.png

Don't forgot to import you CA cert into Chrome/Firefox in case you want to skip the warning message.
 
Last edited:
  • Like
Reactions: PrivateAye, invaderjim1, jvmaragui and 6 others
I'm using a reverse proxy without the manager. Found it easier to deal with the access/error logs with crowdsec installed.
 
Hi,

While this is an old thread, I was having exactly the same problem, and this answer is exactly what I needed.

Thank you!
 
  • Like
Reactions: stanikz
Console/Shell/VNC uses websocket connection. If you set a reverse proxy to access your proxmox server then you must enable websocket (wss) support in your proxy configuration.

I my case I used apache as reverse proxy server.

I enabled mod_proxy_wstunnel module by
Bash: 
sudo a2enmod proxy_wstunnel
sudo systemctl restart apache2

& my apache ssl site config is following:


ServerName ***.com
ServerAlias www.***.com

ProxyPass /.well-known !
ProxyPass / https://192.168.10.80:8006/
ProxyPassReverse / https://192.168.10.80:8006/

SSLEngine on
SSLProxyEngine on
SSLProxyVerify none
SSLProxyCheckPeerCN off
SSLProxyCheckPeerName off
SSLProxyCheckPeerExpire off
SSLCertificateFile /home/***/ssl.combined
SSLCertificateKeyFile /home/***/ssl.key
SSLCACertificateFile /home/***/ssl.ca
SSLProtocol all -SSLv2 -SSLv3 -TLSv1 -TLSv1.1

RewriteEngine on
RewriteCond %{HTTP:Upgrade} websocket [NC]
RewriteRule /(.*) wss://192.168.10.80:8006/$1 [P]
 
stanikz said:
I guess you didn't get my question, sorry for not being so clear. If you are using nginx proxy manager (npm), in case you're using external domain and SSL from Let's Encrypt that shouldn't be that hard at all. In case you're using it with your own created certificate and you are the CA and hold a wildcard cert. Then its important that websockets support is checked as in two lowest figures (section -> For internal domain).

Here I have two npm instances, one for internal domain names and one for external. I can choose to use either the internal domain name to access the webui with my own wildcard SSL cert as well as external with my wildcard SSL from Cloudflare. Hope this can solve your problem.

For external domain
View attachment 41948View attachment 41949

For internal domain name (LAN)
View attachment 41950View attachment 41951

Don't forgot to import you CA cert into Chrome/Firefox in case you want to skip the warning message.
Click to expand...
Thanks for this, solved my issue (that I created for myself). Forgot to enable websocket support when I put it on a new subdomain...
 
I just wanted to chime in and say THANK YOU for this. I have been fighting with this for hours and could not find out an answer.
 
You must log in or register to reply here.
Top Bottom