[GH-ISSUE #38] Suggestion: Better reverse proxy support #17

New issue

Open

opened 2026-03-03 19:10:55 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 19:10:55 +03:00

Owner

Originally created by @zhv on GitHub (Aug 7, 2024).
Original GitHub issue: https://github.com/productiveops/dokemon/issues/38

Hello @salilponde,

I tried to setup dokemon under reverse proxy (nginx in my case) with custom URL path prefix but seems dokemon does not support such deployment mode. As I see dokemon serves frontend resources with / hardcoded in the beginning. Is it possible to change resources/REST API calls to be served with relative path?

nginx config example:

server {
    listen      80;
    location /dokemon/ {
        proxy_pass http://dokemon:9090/; # might be localhost or whatever your host
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

PS: Thank you for such great software product! BR.

Originally created by @zhv on GitHub (Aug 7, 2024). Original GitHub issue: https://github.com/productiveops/dokemon/issues/38 Hello @salilponde, I tried to setup dokemon under reverse proxy (nginx in my case) with custom URL path prefix but seems dokemon does not support such deployment mode. As I see dokemon serves frontend resources with / hardcoded in the beginning. Is it possible to change resources/REST API calls to be served with relative path? nginx config example: ``` server { listen 80; location /dokemon/ { proxy_pass http://dokemon:9090/; # might be localhost or whatever your host proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } } ``` PS: Thank you for such great software product! BR.