This tutorial goes over the steps to configure chorus2 behind nginx reverse proxy so you can remotely control your Kodi setup.
First Enable Kodi Web Interface and set a username and password in the settings as explained here.
Then you can launch kodi web interface on Chromium and in the settings enable reverseproxy setup and also configure the port for your reverse proxy which usually is 443 for your nginx SSL.
For our nginx configuration, we need to note the following point in nginx reverse proxy docs:
A request URI is passed to the server as follows:
- If the
proxy_passdirective is specified with a URI, then when a request is passed to the server, the part of a normalized request URI matching the location is replaced by a URI specified in the directive:location /name/ { proxy_pass http://127.0.0.1/remote/; }- If
proxy_passis specified without a URI, the request URI is passed to the server in the same form as sent by a client when the original request is processed, or the full normalized request URI is passed when processing the changed URI:location /some/path/ { proxy_pass http://127.0.0.1; }Before version 1.1.12, ifproxy_passis specified without a URI, the original request URI might be passed instead of the changed URI in some cases.
Otherwise the way that kodi web interface tries to load images will not work.
## Kodi rewrite
# 1) WS for /jsonrpc (no prefix)
location ^~ /jsonrpc {
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-Real-IP $remote_addr;
proxy_read_timeout 360s;
proxy_pass http://10.10.1.5:9090;
}
# 2) Redirect bare /kodi → /kodi/
location = /kodi {
return 301 /kodi/;
}
# 3) Everything else under /kodi/ → strip prefix
location /kodi/ {
if ($request_uri ~ "^/kodi(?<after>/[^?]*)") {
set $new_path $after;
}
proxy_cache off;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_read_timeout 300s;
proxy_pass http://10.10.1.5:10080$new_path$is_args$args;
}
####
