Tvheadend

Hi, I have setup OpenVPN on my server. Using that I can access (not only) my tvheadend server from the outside world in a secure way: from my smartphone I have full access to the tvheadend web UI.
Using this solution offers the same advantages to all other functionalities on my server.
Not sure what your functional requirements for the reverse proxy are, but thought I'd share my setup :)
regards,
Ruud.

I'm making tvheadend available to SSL (certificate verified) clients with the following NGINX configuration, hope it helps:

ssl_certificate                 /etc/nginx/tvheadend.something.hu.pem;
ssl_certificate_key             /etc/nginx/tvheadend.something.hu.pem;
ssl_client_certificate          /etc/nginx/rootca.pem;
ssl_protocols                   TLSv1;
ssl_verify_client               on;
tcp_nopush                      on;
upstream tvh {
        server                  127.0.0.1:9981;
}

server {
        listen                  [::]:443;
        ssl                     on;
        server_name             tvheadend.something.hu;
        location / {
                proxy_pass http://tvh;
        }
}

I've done some research on apache's mod_proxy. According to the information I found my apache proxy configuration is correct but the initial redirect from tvheadend is not according to the specifications, it returns a 302 header with a relative location (/extjs.html) where it should return a fully qualified URL, in my case http://localhost:9981/extjs.html.

The redirect call is initiated in src/webui/webui.c function page_root.
This function calls src/http.c function http_redirect

I think the http_redirect function could be rewritten to combine the supplied location (/extjs.html) with the server part of the url (in my example http://localhost:9981). I have not found out how to retrieve the server part of the url from the http_connection structure used for all http communication.

I'm also not sure if this should remain a feature request or a bug report, if the conclusion I get from the apache docs that the relocation header should contain a full URL then this is a (small) bug.

Hi,

I'm in the same case as Ronald. I use a main Apache vhost to get multiple access to services using ProxyPass on directory.
TVHeadEnd is not right with this. Get same error.
The point is, a lot of the others apps I run can have an option set for the contect path, so instead of running in / they can be running in /context_path/ and this make them working with apache proxy.

What Endre gives is not the same type of proxy it's a tvheadend.domain.tld and not domain.tld/tvheadend (not same use)

Hi Adam,

Is the fix present in the packaged versions ?
Cannot wait to try it behind a proxy :)

Thanks,

Cédric

no, its only available in master. It will be available in 3.4.

Adam

Ok thank you, wait for 3.4 so