What URL to connect on dashboard workers?

[TitoBahe]

Do I need to have an end-point in my API to retrieve all the sessions created and then I use that end-point there?
I mean, It works when I redirect with my nginx from https://domain.com/dashboard to http://localhost:3000/dashboard and by that I can access the dashboard.
but for the worker I am redirecting https://domain.com/worker -> http://localhost:3000 and it doesnt work even when I used the setting recommended in the API's docs for nginx

[devlikepro]

Hi!
Likely it calls the path /api/sessions/ (not relative one) in Dashboard
Try following the guide and don't use suburi, so it must be https://waha.domain.com redirected to the whole container to http://localhost:3000

https://waha.devlike.pro/docs/how-to/install/

Agree that it's not super customizable, but it's the first time we get requests for subpath :D Usually subdomain is the way to handle workers

@TitoBahe feel free to create a feature request for supporting custom paths, it'll take some time and it's not in our roadmap yet, but likely will handle it in 2025 🤞
https://github.com/devlikeapro/waha/issues

[TitoBahe]

So, one question. I am a bit slow and didnt get it. Sorry for that.
But you said no suburi allowed but I have to use the https://waha.domain.com subdomain. I dont get it.
I read the docs and the nginxs is set to your domain.com and not waha.domain.com and I would prefer not to use my / from my domain.com just for using the dashboard.

Follwing the subdomain waha.domain.com I created in my nginx thats the config on the docs, or I am wrong?:

server {

    server_name waha.*****.com;
   
    location /.well-known {
        alias /var/www/ssl-proof/waha/.well-known;
    }

    location / {
        proxy_pass http://127.0.0.1:3000;  # WAHA Container na porta 3000
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-Ssl on; # Optional

        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header Connection “”;
        proxy_buffering off;

        client_max_body_size 0;
        proxy_read_timeout 36000s;
        proxy_redirect off;
    }


    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/*****.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/*****.com/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}

server {
    if ($host = waha.*****.com) {
        return 301 https://$host$request_uri;
    } # managed by Certbot
   
    server_name waha.*****.com;
    listen 80;
    listen [::]:80;
    return 404; # managed by Certbot
}

[devlikepro]

subdomain are fine, but not sub-"uri"

• 🟢 Good - https://waha-worker-1.example.com
• 🔴 Bad - https://example.com/waha-worker-1

Here's the guide, just replace <YOURDOMAIN.COM> to waha.*****.com
https://waha.devlike.pro/docs/how-to/install/#configure-nginx-and-lets-encrypt