Install tvheadend on Ubuntu 22.04 does not create hts folder

Jef Bosk

No matter if you install via

curl -1sLf \ 'https://dl.cloudsmith.io/public/tvheadend/tvheadend/setup.deb.sh' \ | sudo -E bash

sudo apt-add-repository ppa:mamarley/tvheadend-git-stable

The installation routine does not create tha hts folder anymore.

Is this a Bug? If yes, is ther a workaround?

Saen Acro

Not a bug it create it in newer location.
It's uncomfortable in lot of situations.
Mostly if home path is on another disk, and make recording in default location.

Jef Bosk

I now purged tvheadend and reinstalled. it now created a folder under /home/USERNAME/.config

Lisa White

Hello Jef. I posted yesterday about the same problems as you are having. For some reason, the source developer originally changed the root directories from .hts to var/lib/tvheadend. Recently, the developer added .config folder (hidden on my system) really messing things up on my end. I have been using tvheadend for many years and it worked flawlessly about 97 percent of the time. The recent update caused my systems to crash and I spent many hours trying to figure out the reason why. I reinstalled by source code and deb file and both sill had same 403 problem. I had an old tvheadend backup and compared it to the new source and found the folder change and the subuser file was being installed in the wrong location. I solved the 403 problem by making the entire tvheadend source visible, not hidden. I changed permissions and gave all folders, subfolders and files full access to read, write and execute. I moved the subuser file into /var/lib/tvheadend/.config/hts/ location. Furthermore,take note of the location of the recording folder. I had to redirect that too. Next, using command line, stop tvheadend from running then command it to restart. Voila it worked!!!

There may be an easier way to fix this, but I am a linux novice and this worked for me. Hopefully, the developers get rid if the .config folder and change things back because I believe that there is going to be many posts regarding the 403 error. Hope it helps you!!
~Lisa

Jef Bosk

Hi Lisa, I would not say you are a linux novice...what you write sounds like rocket science to me. What I noticed, is that Ubuntu, in Version 22.04 has restricted user access to many more folders that is used to do in the previous versions. This may have forced the tvheadend guys to chance something, but they probably did not manage this in a good way. Can you tell me which main folders you changed the permissions for?

Lisa White

Jef, I opened terminal up while in the root area. (Here you will see etc, var lib etc.) Write the command, sudo chmod -R a+rwx /var/lib/tvheadend. (Make sure folder are visible) This gave me permission to move files within the hts folder. Others may disagree with this method but it worked for me. Move your superuser file into the hts folder where all the other files are stored. Clear your browser cache and open it up using your ip:9981. You should see the log on screen again and enter your credentials. This should eliminate the 403

One thing that I have noticed is that tvheadend changes some of the files permission back after you restart it. You may have to change permissions everytime you need to change something in the directories.

Good Luck!!

Jef Bosk

Tried this too, but didn't help. Unless I did something wrong.

Lisa White

Few questions: Are all the files in the directory under var/lib/tvheadend/.config/hts? Don’t forget the period before config in line.

Did you change permissions in terminal command not by using file folder option?

Did you move the superuser file into that hts folder? This is a must because that’s the webgui log in.

Did you clear the cache out on your internet browser that you use to log in?

After all that:

Did you system Stop tvheadend and start it back up by terminal command?

If you look at my post yesterday, I had the identical problem and all these steps worked for me. If none of these steps that I had listed work for you then I recommend a full purge of tvheadend and reinstall by built source code. Someone posted an excellent guide for Ubuntu 22 on how to build. After you build new and install, follow the above steps because you will definitely get the 403 using the current code.

I spent 8 hours figuring this 403 error yesterday and I believe that this is a bug. someone needs to change folders and eliminate the .config. and allow all files to be in same folder.

Good luck!!

Jef Bosk

Yes I did, but in a light different way that should at the end have the same result: I copied the the superuser file to /home/USERNAME/.config and renamed the original file in superuser_OLD.

Yes, I think all the files are there, see attached screenshot, showing the superuser I took from one directory above

Otherwise I purged and reinstalled tvheadend meanwhile already 6 or 7 times even swapping repositories ppa:mamarley <> dl.cloudsmith.io

I am not as skilled as you with Linux...I will try read and to understand your post tomorrow ;)

DeltaMikeCharlie

It seems that this was an intentional change to bring TVH on Debian in line with other Debian server packages.
https://github.com/tvheadend/tvheadend/pull/1540 https://tvheadend.org/d/8335-need-help-with-install

Lisa White

Jef, you are missing a bunch of folders and files

The hts folder should have the following to run tvheadend:

Access control, bouquet, calclient, channels, codec, dvr, epggrab, input, profile, service mapper, timeshift folders. The files not in folder should be: config, epgdb.v3, .lock and superuser.

I think you do not have the entire db installed. Purge the entire install and build from source.

I read the above post. The post that directed me to the link about the files being moved is full of crap. That update crashed my entire system which led me to the problem 403
Lisa

Jef Bosk

You mean purge and reinstall for the 8th or 9th time? Why should that make sense?

DeltaMikeCharlie

It seems that you have discovered a new bug.

The developers involved are aware of it and have also been able to reproduce it. A fix is under investigation, however, no timeline is currently available.

I suggest that you roll back to a previous version if you can and wait for the bug to be fixed before trying again.

Lisa White

Jef, that’s up to you. I was just trying to help. Did you read my last post? I looked at your photo and compared to my tvheadend directory. It appears that files and folders are missing. Build your own source instead of using those files from iCloud. The source build will make sure that you have all of the components to make the program work. As I explained multiple times today, you will still have to make the adjustments to the directories. After install, start the program and you should get the 403 error. System stop tvheadend through terminal and make all of the adjustments like I posted to the tvheadend directory. Do not rename superuser old. Remove it and paste into the hts folder. System restart tvheadend, clear cache in browser and log in. I duplicated this 24 hours ago and my system is running like a well oiled machine. I am using the same Ubuntu distro as yours. Sorry, but that’s all I have to offer you. Maybe somebody else will step in but it’s hard to get a response on this forum.

Lisa

Jonas Lang

What do you mean “it’s hard to get a response on this forum”. You decide to drop by occasionally and expect everyone to jump to attention. Really !!!

Jonas Lang

Has anyone tried this https://tvheadend.org/d/8133-tvheadend-build-and-install-on-ubuntu-22-04-64-bit-x86_64-platform-for-beginners

Lisa White

Listen up Jonas. Stop being a dick! I monitor this forum frequently. This forum is not as active as it use to be and sometimes it takes 24 hours or more to get a response. So do yourself a favor and butt out!! And of course I tried that. I mentioned it in one of my posts. Dah!!

Jonas Lang

Lisa White wrote:

> Listen up Jonas. Stop being a dick! I monitor this forum frequently. This forum is not as active as it use to be and sometimes it takes 24 hours or more to get a response. So do yourself a favor and butt out!! And of course I tried that. I mentioned it in one of my posts. Dah!!

Tone your language down or you’ll find yourself removed very quickly from the forum. I’m surprised anyone responds to you with that awful attitude.

You may “monitor the forum” but you contribute precious little to it and if that’s an example of your contribution I think we have all been spared.

Flole

Folks, please be nice to each other! It would definitely be nice to get some more details, and maybe even log messages that show what's going on.

Lisa White

This childish behavior started with him and his cyber bullying comments. Coming from a so called man that has minimal posts! He needs to grow up!