Tvheadend

Does no one have any suggestions?

I can't login in over port 9981 or port 9982 (over my client TVHClient Android app).

I know that the /etc/init.d script has run and the system is listening on port 9981 and 9982.

At this point, all I have is the package install so it installs with the only user being the superuser (with the correct user/password in the superuser file at /home/hts/.hts/tvheadend/superuser.

So when I go to 192.168.1.100:9981 and get prompted for my username/password, it should be reading the superuser text file and matching it with the username/password I provide.

Is there any reason why it wouldn't be reading it? Or reading it incorrectly?

Any other suggestions? Could it have anything to do with the new hard drive I installed?

Thanks!

Have you tried starting tvheadend with the --noacl option? (disables access control) Then you can use the webif to change users/passwords.

[[https://tvheadend.org/boards/5/topics/22023?r=22024#message-22024]]

John Hanley wrote:

Does no one have any suggestions?

I can't login in over port 9981 or port 9982 (over my client TVHClient Android app).

I know that the /etc/init.d script has run and the system is listening on port 9981 and 9982.

At this point, all I have is the package install so it installs with the only user being the superuser (with the correct user/password in the superuser file at /home/hts/.hts/tvheadend/superuser.

So when I go to 192.168.1.100:9981 and get prompted for my username/password, it should be reading the superuser text file and matching it with the username/password I provide.

Is there any reason why it wouldn't be reading it? Or reading it incorrectly?

If you've setup an account within Tvheadend using the same username as the superuser that may explain why you're seeing this problem.

Any other suggestions? Could it have anything to do with the new hard drive I installed?

Thanks!

Joe User wrote:

Have you tried starting tvheadend with the --noacl option? (disables access control) Then you can use the webif to change users/passwords.

[[https://tvheadend.org/boards/5/topics/22023?r=22024#message-22024]]

So I added the --noacl option in the /etc/init/tvheadend.conf script. After rebooting I was able to access the web ui in Firefox. I added a user (not the same as my superuser), removed the --noacl option, rebooted, and the web ui asks me for a username and password again, but the username/password doesn't work. Neither does my superuser name/password. So back to where I was.

I also could not see the addition of accesscontrol files in my /home/hts/.hts/tvheadend directory so have no idea where tvheadend is storing the username/password of the user I created above. It seems to have saved the user somewhere as starting the UI before I rebooted showed the user was there.

Any thoughts as to what to try next?

Thanks!

I have similar problem 3 times incorrect login and on forth it's OK.
Even when password is saved in browser.

Mine won't login no matter how many times you try. :-(

John Hanley wrote:

Mine won't login no matter how many times you try. :-(

I recommend you delete the contents of /home/hts/.hts/tvheadend & try again. Edit the init script and change the ARGS param to "-f -C --noacl" and restart. Once you're in disable "HTTP digest authentication" in Config -> General -> Base.

I deleted the contents of tvheadend and changed the ARGS parameters as suggested. After rebooting, I went into my webui. However, I could not find any "HTTP digest authentication" in Config->General (there was no Base). Different version perhaps?

I added a new user, closed the webui, opened the webui again, and the user was still there.

I removed the -C --noacl from the init script, rebooted and attempted to login to the webui with as my new user. No luck.

I added the --noacl back in and rebooted. When I got back into my webui I noticed the user was no longer there.

I checked, and there was no "accesscontrol" directory added to /home/hts/.hts/tvheadend.

This makes me wonder if the webui is somehow not able to read or write to /home/hts/.hts/tvheadend.

Could be a permissions thing? I checked and the directory is owned by user hts.

Thoughts?

Thanks!

John Hanley wrote:

I deleted the contents of tvheadend and changed the ARGS parameters as suggested. After rebooting, I went into my webui. However, I could not find any "HTTP digest authentication" in Config->General (there was no Base). Different version perhaps?

I added a new user, closed the webui, opened the webui again, and the user was still there.

I removed the -C --noacl from the init script, rebooted and attempted to login to the webui with as my new user. No luck.

I added the --noacl back in and rebooted. When I got back into my webui I noticed the user was no longer there.

I checked, and there was no "accesscontrol" directory added to /home/hts/.hts/tvheadend.

This makes me wonder if the webui is somehow not able to read or write to /home/hts/.hts/tvheadend.

Could be a permissions thing? I checked and the directory is owned by user hts.

Thoughts?

Thanks!

try to write to the directory as the hts user.

sudo -u hts /bin/bash
touch /home/hts/.hts/tvheadend/test.file
rm /home/hts/.hts/tvheadend/test.file
exit

try to write to the directory as the hts user.

[...]

Marvelous! This was the key.

I did NOT have permission to create the file test.file. Upon further investigation, I found that when I swapped out my /home drive, I did not set the ownership & permissions properly on /home. I had set proper ownership of all subdirectories of /home, but /home itself was set to a user and not root, and permissions were only for the user.

I changed my /home ownership to root with a chmod 755 and now I can login just fine! I copied over my backed up tvheadend files and I have my channels back.

I just knew it had something to do with permissions somewhere. It seemed rather odd that things went awry when I put in a new hard drive but copied over all the working files.

I will let you all know if there are any other troubles.

Thanks for the help!