TVH to listen to locolhost
Added by pixel24 pixel24 about 1 year ago
Hi@all,
I have TVH (HTS Tvheadend 4.3.0~pre+202309061207-0~built202309061318~gitfe4df311d~ubuntu23.04.1) installed on an Ubuntu server VM. I can reach the webinterface at:
http://[IP FROM server]:9981
TVH is supposed to provide the TV for Jellyfin (and only for Jellyfin). Jellyfin runs on the same VM. I would like to manage the access from Jellyfin to TVH via localhost (127.0.0.1). However, TVH does not seem to listen here:
root@media01:~# netstat -tulpen |grep 127
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 101 29116 578/systemd-resolve
tcp 0 0 127.0.0.54:53 0.0.0.0:* LISTEN 101 29118 578/systemd-resolve
udp 0 0 127.0.0.54:53 0.0.0.0:* 101 29117 578/systemd-resolve
udp 0 0 127.0.0.53:53 0.0.0.0:* 101 29115 578/systemd-resolve
udp 0 0 127.0.0.1:123 0.0.0.0:* 0 29789 607/ntpd
How can I get TVH to accept requests on 127.0.0.1?
with best
pixel24
Replies (8)
RE: TVH to listen to locolhost - Added by saen acro about 1 year ago
Tvheadend 4.3.0~pre+202309061207-0~built202309061318~gitfe4df311d~ubuntu23.04.1
This is unofficial version.
Your command is wrong
netstat -tulpen |grep tvheadend
tcp 0 0 0.0.0.0:9982 0.0.0.0:* LISTEN 0 27780 1128/tvheadend
tcp 0 0 0.0.0.0:9981 0.0.0.0:* LISTEN 0 27776 1128/tvheadend
udp 0 0 0.0.0.0:34824 0.0.0.0:* 124 28406 1128/tvheadend
udp 0 0 239.255.255.250:1900 0.0.0.0:* 124 28403 1128/tvheadend
as you see 0.0.0.0:* mean every interface not only lo
If use some peudo-virtualization search problem in pseudo-networking.
RE: TVH to listen to locolhost - Added by pixel24 pixel24 about 1 year ago
saen acro wrote:
This is unofficial version.
yes I am aware of that. However, I do not want to give up the convenience of the package system (apt). Is that a disadvantage? Or is there an official repository for (Debian/Ubuntu)?
Your command is wrong
Oh, my bad. Here I get:
root@media01:~# netstat -tulpen |grep tvheadend
tcp6 0 0 :::9982 :::* LISTEN 0 26942 721/tvheadend
tcp6 0 0 :::9981 :::* LISTEN 0 26939 721/tvheadend
udp 0 0 239.255.255.250:1900 0.0.0.0:* 120 16354 721/tvheadend
udp6 0 0 :::41141 :::* 120 16357 721/tvheadend
So it does not listen for IPv4. Which is strange since I have TVH under:
can be reached. I have not touched the file: /etc/default/tvheadend yet. Do I need to change the values:
TVH_HTTP_PORT=""
TVH_HTSP_PORT=""
set yet?
If use some peudo-virtualization search problem in pseudo-networking.
No, this is an Ubuntu server VM running under Proxmox.
RE: TVH to listen to locolhost - Added by saen acro about 1 year ago
ps aux |grep tvheadend
Let see how is started service.
There is a official repo see wiki
https://tvheadend.org/projects/tvheadend/wiki/AptRepositories
RE: TVH to listen to locolhost - Added by pixel24 pixel24 about 1 year ago
root@media01:~# ps aux |grep tvheadend
hts 721 0.1 0.3 994960 51256 ? Ssl Okt03 2:41 /usr/bin/tvheadend -f -p /run/tvheadend.pid -u hts -g video -6
root 12286 0.0 0.0 6604 2176 pts/0 S+ 16:35 0:00 grep --color=auto tvheadend
RE: TVH to listen to locolhost - Added by saen acro about 1 year ago
-6, --ipv6 Listen on IPv6
remove -6 from service command line
service tvheadend status
will show you location
mine is in
/lib/systemd/system/tvheadend.service
RE: TVH to listen to locolhost - Added by pixel24 pixel24 about 1 year ago
saen acro wrote:
remove -6 from service command line
ok, I have removed and restarted the service
root@media01:~# ps aux |grep tvheadend
hts 12525 5.9 0.2 929412 34008 ? Ssl 17:21 0:00 /usr/bin/tvheadend -f -p /run/tvheadend.pid -u hts -g video
root 12585 0.0 0.0 6604 2176 pts/0 S+ 17:22 0:00 grep --color=auto tvheadend
root@media01:~# netstat -tulpen |grep tvheadend
tcp 0 0 0.0.0.0:9982 0.0.0.0:* LISTEN 0 89542 12525/tvheadend
tcp 0 0 0.0.0.0:9981 0.0.0.0:* LISTEN 0 89539 12525/tvheadend
udp 0 0 0.0.0.0:48352 0.0.0.0:* 120 90368 12525/tvheadend
udp 0 0 239.255.255.250:1900 0.0.0.0:* 120 90365 12525/tvheadend
I always thought 0.0.0.0 means all interfaces?
RE: TVH to listen to locolhost - Added by pixel24 pixel24 about 1 year ago
Now the access from Jellyfin (on the same machine) should be possible via 127.0.0.1?