Closed mattmary closed 1 year ago
I've tried to replicate your issue with a fresh installation but was unable to. My install log looks virtually identical to yours: https://pastebin.com/SMeenMms. Checking my service log it also looks pretty much the same (with the exception of the last line): https://pastebin.com/7aQLwdbP.
As far as the superuser file mentioned, this does not seem to be required since the app is working and the file is not present in my setup:
ls -lah /var/packages/tvheadend/var/
total 20K
drwxr-xr-x 1 sc-tvheadend synocommunity 192 Jan 1 09:40 .
drwxr-xr-x 1 root root 116 Jan 1 09:38 ..
drwx------ 1 sc-tvheadend synocommunity 64 Jan 1 09:39 accesscontrol
drwx------ 1 sc-tvheadend synocommunity 832 Jan 1 09:39 bouquet
drwx------ 1 sc-tvheadend synocommunity 64 Jan 1 09:39 caclient
drwx------ 1 sc-tvheadend synocommunity 256 Jan 1 09:39 codec
-rw------- 1 sc-tvheadend synocommunity 1.6K Jan 1 09:40 config
drwx------ 1 sc-tvheadend synocommunity 12 Jan 1 09:39 dvr
drwxr-xr-x 1 sc-tvheadend synocommunity 24 Jan 1 09:39 epggrab
-rw-r--r-- 1 sc-tvheadend synocommunity 11 Jan 1 09:39 .lock
drwxr-xr-x 1 sc-tvheadend synocommunity 26 Jan 1 09:39 pip-cache
drwx------ 1 sc-tvheadend synocommunity 448 Jan 1 09:39 profile
-rw-r--r-- 1 sc-tvheadend synocommunity 7.4K Jan 1 09:39 tvheadend.log
-rw-r--r-- 1 sc-tvheadend synocommunity 5 Jan 1 09:39 tvheadend.pid
This may seem simple but have you tried rebooting your NAS as well as accessing the web interface using a private window or in incognito mode (to eliminate all cached cookies)?
As a final thought you can also take a look at the permissions on the source files for the webui. They should look like this if it's a fresh installation:
ls -all /var/packages/tvheadend/target/share/tvheadend/src/webui/static/extjs/
total 2024
drwxr-xr-x 1 sc-tvheadend synocommunity 100 Nov 28 20:59 .
drwxr-xr-x 1 sc-tvheadend synocommunity 340 Nov 28 20:59 ..
drwxr-xr-x 1 sc-tvheadend synocommunity 6 Nov 28 20:59 adapter
drwxr-xr-x 1 sc-tvheadend synocommunity 4 Nov 28 20:59 examples
-rw-r--r-- 1 sc-tvheadend synocommunity 1370541 Nov 28 21:34 ext-all-debug.js
-rw-r--r-- 1 sc-tvheadend synocommunity 699742 Nov 28 21:34 ext-all.js
drwxr-xr-x 1 sc-tvheadend synocommunity 18 Nov 28 20:59 resources
Hello,
I think this is a browser problem: after reinstalling, I probably was authenticated. Instead of setting up my credentials, I just clicked on the sign in button with any credentials and tvheadend opened.
Is this a new Bug?
Package Name
tvheadend
Package Version
4.3.20221128
Device Model
DS918+
Device Architecture
x86_64
Firmware Version
7.1
What happened?
Hello,
this issue follows my problem to reinstall the package: https://github.com/SynoCommunity/spksrc/issues/5538 After installation, I opened the tvheadend URL and have been to define the basic configuration values. I then restarted the service and reopen the URL: it requests me my credentials (I'm sure of them, and copied pasted them from notepad): but I get a 403 forbidden.
To check if I did not make a mistake in my password,
After this new reinstall, I have not been asked to set configuration values: I get directly a 403.
it seems that I'm not the only one with this issue: in the tvheadend support, there is this topic https://tvheadend.org/boards/4/topics/44706. I've tried to force the admin credentials with this superuser file, but the filesystem seems different from this topic.
So my questions are:
Thanks for your help
Reproduction steps
Install Log