Document proper reverse proxy setup

[schnuffle]

I've been reading the issues about using nginx as reverse proxy, so there're people where it seems to work.
The problem is that there isn't enough info to set it up properly.
My setup:

nginx:

location / {
    # First attempt to serve request as file, then
    # as directory, then fall back to displaying a 404.
    #try_files $uri $uri/ =404;
    proxy_pass http://127.0.0.1:3000;
}

location /ws {
    proxy_pass http://127.0.0.1:3000;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "Upgrade";
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-for $proxy_add_x_forwarded_for;
    proxy_set_header Host $host:$server_port;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_connect_timeout 600;
    proxy_read_timeout 600;
    client_max_body_size 1024M; # Set higher depending on your needs
}

Virtlyst config:

[wsgi]
    master = true
    threads = auto
    http-socket = 127.0.0.1:3000
    application = /usr/local/lib/libVirtlyst.so
    chdir2 = /usr/local/var/virtlyst
    static-map = /static=/usr/local/var/virtlyst/root/static

[Cutelyst]
    production = true
    DatabasePath = /usr/local/var/virtlyst/virtlyst.sqlite
    TemplatePath = /usr/local/var/virtlyst/root/src

[Rules]
    cutelyst.* = true
    virtlyst.* = true

Everything works fine but the console. When I open a console, I can find following error in the browser debug console:

ERROR: WebSocket error: Can't connect to websocket on URL: wss://127.0.0.1:3000/ws/2/2d8a0b35-e63d-4c46-b8ad-420d3fabf271

Now I ask myself, how is the WSS URL build up?

From testing it seem it uses http-socket = 127.0.0.1:3000.

I'll write the docs howto set it up properly, but I need a working setup first :-).

Regards

Schnuffle

P.S.: The connection to libvirt is with a local socket

[schnuffle]

I found the solution,
stupid me :-).
I'll make a PR to add some docs later on

[dantti]

okay :)

[dantti]

Or you can document it on the wiki which is open.

[schnuffle]

After some more testing I'm back to total confusion. I had one moment where it did work, but it's more by luck then by understanding what's wrong.
I've found a semi working config:

    location / {
        proxy_pass http://127.0.0.1:3000;
        proxy_redirect http:// $scheme://;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-for $proxy_add_x_forwarded_for;
        proxy_set_header Host $host:$server_port;
        proxy_set_header X-Forwarded-Host $host;
        proxy_set_header X-Forwarded-Proto $scheme;
    }

    location /ws {
        proxy_pass http://127.0.0.1:3000;
        proxy_redirect http:// $scheme://;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "Upgrade";
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-for $proxy_add_x_forwarded_for;
        proxy_set_header Host $host; # :$server_port;
        proxy_set_header Port $server_port;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_connect_timeout 600;
        proxy_read_timeout 600;
        client_max_body_size 1024M; # Set higher depending on your needs
    }

That one is working with Spice as Console but fails for VNC. And another disturbing thing is the keyboard layout, it's wrong no matter what I set.

So I have a working config, but I think before writing some docs, I need to assure that I know it'S correct and not just the first successful test

[schnuffle]

Getting closer.
Using Chromium the config works with VNC and Spice, just that with Spice the keyboard layout is wrong.

Setting the listen address for the console to localhost in the VM config works as well.

[dantti]

VNC usually gives some issues, but I myself have no issues with Spice, my config is as follows:

upstream virtlyst {
    server localhost:3000;
    keepalive 32;
}

server {
    server_name kvm;
    access_log /var/log/nginx/virtlyst.log;

    location / {
        include fastcgi_params;
        fastcgi_pass virtlyst;
        fastcgi_keep_conn on;                                                                                                                                               
    }                                                                                                                                                                       
    location /static {                                                                                                                                                      
        alias  /home/dnicoletti/code/Virtlyst/root/static;
        access_log /var/log/nginx/virtlyst-static.log; 
        expires    1d;                                                                                                                                                      
    }                                                                                                                                                                       
    location /ws {
        proxy_pass http://localhost:3001;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-for $proxy_add_x_forwarded_for;
        proxy_set_header Host $host:$server_port;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_connect_timeout 600;
        proxy_read_timeout 600;
        client_max_body_size 1024M; # Set higher depending on your needs 
    }

    listen [::]:81;
    listen 81;
}

[dolohow]

If someone is trying with reverse proxy setup while also using docker. I suggest to use network_mode: host, overwriting now default 80 port and using one of the above configuration.