Yes, this happens to different users on different systems so I don’t think related to user details or browser cache.
This is copy of the nginx config we are currently testing, do you see any issues with this or know of a better working config for the OpenNebula version we are using? We also need to allow noVNC as well.
No squealing.
server_tokens off;
OpenNebula Sunstone upstream
upstream sunstone {
server 127.0.0.1:9869;
}
Added 02/08/2021
upstream websocketproxy {
server 127.0.0.1:29876;
}
XXXXXX HTTP virtual host
server {
listen 80;
server_name XXXXXX;
### Permanent redirect to HTTPS (optional)
return 301 https://$server_name:443;
}
XXXXXX HTTPS virtual host
server {
listen 443 ssl;
server_name XXXXXX;
root /usr/share/nginx/html;
ii opennebula-common 6.0.0.2-1.ce all Common OpenNebula package shared by various components (Community Edition)
ii opennebula-common-onecfg 6.0.0.2-1.ce all Helpers for OpenNebula onecfg (Community Edition)
ii opennebula-fireedge 6.0.0.2-1.ce amd64 OpenNebula web interface FireEdge (Community Edition)
ii opennebula-flow 6.0.0.2-1.ce all OpenNebula Flow server (Community Edition)
ii opennebula-gate 6.0.0.2-1.ce all OpenNebula Gate server (Community Edition)
ii opennebula-libs 6.0.0.2-1.ce all OpenNebula libraries (Community Edition)
ii opennebula-node-kvm 6.0.0.2-1.ce all Services for OpenNebula KVM node (Community Edition)
ii opennebula-provision 6.0.0.2-1.ce all OpenNebula infrastructure provisioning (Community Edition)
ii opennebula-provision-data 6.0.0.2-1.ce all OpenNebula infrastructure provisioning data (Community Edition)
ii opennebula-rubygems 6.0.0.2-1.ce all Ruby dependencies for OpenNebula (Community Edition)
ii opennebula-sunstone 6.0.0.2-1.ce all OpenNebula web interface Sunstone (Community Edition)
ii opennebula-tools 6.0.0.2-1.ce all OpenNebula command line tools (Community Edition)
/etc/nginx/sites-enabled/nebula
upstream oned {
server 127.0.0.1:2633;
}
upstream sunstone {
server unix:/run/one/sunstone.socket;
}
upstream onegate {
server 127.0.0.1:5030;
}
upstream websocketproxy {
server 127.0.0.1:29876;
}
# Workaround https://github.com/OpenNebula/addon-context-linux/issues/218
map $http_x_onegate_token $one_frontend {
"~.+" "onegate";
default "sunstone";
}
server {
listen 192.168.230.14:80 default_server;
root /usr/lib/one/sunstone/public;
index index.html index.htm;
server_name grichka.eole.lan;
access_log /var/log/nginx/opennebula-sunstone-access.log;
error_log /var/log/nginx/opennebula-sunstone-error.log;
client_max_body_size 50G;
proxy_hide_header "X-Content-Type-Options";
underscores_in_headers on;
location / {
try_files $uri @sunstone;
}
location /RPC2 {
include proxy_params;
proxy_pass http://oned;
}
location /websockify {
proxy_pass http://websocketproxy;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_send_timeout 30m;
proxy_read_timeout 30m;
}
location @sunstone {
# Admin only connectxon
# allow 192.168.230.30;
# deny all;
include proxy_params;
proxy_pass_request_headers on;
# Either Sunstone or onegate based on x_onegate_token header
proxy_pass http://$one_frontend;
}
}