Tvheadend

To completely start over, do:
sudo /etc/init.d/tvheadend stop
sudo rm -rf /home/hts/.hts/tvheadend/
sudo dpkg-reconfigure hts-tvheadend
sudo /etc/init.d/tvheadend start

Note: this deletes your entire config!

Thanks!

Somehow i can't login again.
I did this procedure again and it's not working for me now.
How can I completely eliminate the need for web-UI login?

Sure, I've done the same thing. I trust my local network, and I've put tvheadend behind a secured Apache reverse proxy for internet access.

sudo /etc/init.d/tvheadend stop
sudo rm -rf /home/hts/.hts/tvheadend/

Now, edit /etc/init.d/tvheadend:
DAEMON_ARGS="-f -u hts -g video -C"

Next, start tvheadend:
sudo /etc/init.d/tvheadend stop

And, now undo the change to the /etc/init.d/tvheadend script:
DAEMON_ARGS="-f -u hts -g video"

Thanks a lot Mark Wormgoor :)

That tip does not work for me, i've tried everything now ..

Hi,
from root
killall -9 tvheadend

tvheadend -C

After that go to access control and create admin user from web interface.

Or from root after killing tvheadend go to /home/hts/tvheadend/accesscontrol and edit options by hand.
Coz directory hidden, better to navigate from mc :))

P.S.
If you want the more reasonable access rights for /dev/dvb devices, create the appropriate rule for udev. Find, where these rules are at your system, the standard position is /etc/udev/rules.d. Create here the file 15-dvb.rules, containing the line:

SUBSYSTEM=="dvb", ACTION=="add", MODE="0666"

The filename is not critical, only it has to have the extension 'rules' and it should not interfere with others rules, already present in your linux box.
After that tvheadend works much better ( at least for me).

Regards.

Hey, thanks for that. Now i've been able to login. But i have to run:

killall -9 tvheadend
tvheadend -C

Everytime i reboot my computer to be able to login with my account, is there a way to fix that?

By the way, i can't find any file in /home/tvheadend/accesscontrol, only superuser in /home/hts/.hts/tvheadend where it says:

{
"username": "my user name"
"password": "my password"
}

and those login does works after i've used killall and tvheadend -C commands..

Hi.
It depends from which user you launch tvheadend.
Please check script /etc/init.d/tvheadend as described in 5th post.
If you reboot computer tvheadend working from user hts (u option) and you have to edit options in /home/hts/.hts but if you launch it from root all settings is in /root/.hts folder.
Make first "universal" superuser with star in first, second and third fields and all options enabled "v"
Make second user with some username and pass also all enabled(especially admin). Save. After rebooting delete
(or disable) first say "universal" user. Simplest way is to have identical ./hts folders in /home/hts and in /root too.
Regards.

Reply with steps to recover access after being locked out due to a wrong config change:

1) login with ssh and stop TVH with systemctl stop service.tvheadend42.service
2) starting TVH with a default config in the home directory (/storage) with tvheadend -C
keep this session open.
3) configure an admin account with a passwd in addition to the default account * via the web-interface
4) stop the new tvheadend sesion with ^C.
5) moving old account details with:
cd /storage/.kodi/userdata/addon_data/service.tvheadend42
mv accesscontrol/ accesscontrol_old
mv passwd/ passwd_old
cp -r ~/.hts/tvheadend/accesscontrol .
cp -r ~/.hts/tvheadend/passwd/ .
6) start TVH again with systemctl start service.tvheadend42.service

Hope this helps

Edit (2023-12-12) :
I ran into a similar issue again, but now on WSL2 Ubuntu.
The above steps didn't help me this time.
I found I had multiple issues.
Steps that helped me to understand the issue better:

sudo systemctl stop tvheadend.service
# in a second window:
sudo journalctl --unit=tvheadend.service -f
# back in the first window:
sudo systemctl start tvheadend.service

On of my issues was

 config: Found legacy '.hts/tvheadend', consider moving this to '.config/hts' instead. 

::ffff:192.168.1.10 [ Kodi Media Center ]: Unauthorized access

Hello.
I will tack on to this thread with something somewhat topical. My installation is an add-on to LibreELEC 9.2.2.

My wife wanted access to record/schedule so I wanted to a) change the default asterisk account to a named account (say 'admin') w/password, and b) create a new account (say 'wife') for her. Seemed easy enough.

I renamed the asterisk account to 'admin' and then went to create a password for it. Typed in 'admin' for the username and then either tabbed down or pressed enter for the password field (don't remember), and just like that... I lost access to the system. I get a login prompt and that's that. I have not yet created the 'wife' account.

I can ssh into the box and can view/edit user file(s). I found two locations with accesscontrol directories:

1. /storage/.kodi/userdata/addon_data/service.tvheadend42/accesscontrol
2. /storage/.hts/addons/tvheadend/accesscontrol

Each location contains one user file, each is a different file name (long string of digits), and each with a different user. One is 'admin' and the other '*'. Neither has a password placeholder.

Is there any way I can recover admin web access to the server? Any help/ideas much appreciated.

I suspect you already tried some of the steps I shared before because normally there is no /storage/.hts/...
Do you have a /storage/.kodi/userdata/addon_data/service.tvheadend42/passwd/ directory also?
The password 'placeholder' is not in the accesscontrol file, but in a separate file under the passwd/ directory.
I have not tried with password-less accounts, but maybe you can just copy over the accesscontrol directory from ~/.hts/tvheadend/ (step 5)

Thank you Ron! I am back in business. Amazing what happens when one follows instructions.

I stopped the service and copied the master account over per Step 5. I then deleted the messed up account file. The web interface wouldn't launch when I started the service, so I rebooted the box. The system came back clean with the one '*' account and all my configuration intact. Will have to read up on account creation a bit more carefully next time.

BTW, there was no 'passwd' directory that I could find. Possibly something auto-created on first entry?

i've tried everything now but nothing worked for me. [[https://get-shareit.com/]] [[https://get-vidmateapk.com/]]