Bug #1559
Unauthorized when trying to access web interface
100%
Description
I have just built tvheadend from git and have run into an authentication problem when trying to access the web interface.
I have verified the settings are still the same in accesscontrol and also in superuser.
I have also tried dpkg-reconfigure, which has not solved this.
Can you offer me any suggestions as to how i rectify this please
Thanks
History
Updated by Adam Sutton almost 12 years ago
- Status changed from New to Need feedback
Debug log please. And git version info (latest git means nothing to me).
Adam
Updated by David Hewings almost 12 years ago
Hi Adam
Sorry about being so vague.
I have just installed from the git, which includes the latest commit a9584156a3567b85dc5a4b4dea36fd45be88fc8e.
I'm not sure how I can get a debug log, as I cannot access the web interface.
I will try going back through the commits and fine where the error occurs.
Thanks
David
Updated by David Hewings almost 12 years ago
Hi Adam
I have located the latest commit which works and autheticates ok.
0400599d606e5781eb776f4d49e3ab4bdfca326a
Anything after this causes me to get authentication errors.
I have also replicated this on a 2nd machine (alhtough very similar spec)
Thanks
Updated by Adam Sutton almost 12 years ago
I cannot understand this, that fix was to ensure a return value is sent (in response to certain valid JSON API requests). Without the response some browsers waited (until timeout) for a response and caused the UI to appear to not respond to configuration changes.
I cannot see how it would affect authentication and I cannot repeat this with my own setup. Can you paste the contents of your .hts/tvheadend/accesscontrol directory (i.e. what's in each file) - obscure the passwords ofc.
Adam
Updated by David Hewings almost 12 years ago
Hi Adam
Here is the info:
Filename: 1
{ "enabled": 1, "username": "user", "password": "pass", "comment": "Default access entry", "streaming": 1, "dvr": 1, "dvrallcfg": 1, "webui": 1, "admin": 1, "id": "1" }
Thanks for looking at this
David
Updated by Adam Sutton almost 12 years ago
I think I can see a bug in the access creation, can you try adding:
prefix: "0.0.0.0/0",
To that file, note last entry inside {} must not have comma, the rest should.
Adam
Updated by David Hewings almost 12 years ago
Thanks Adam
You're a star! Worked like a treat!
Cheers mate
Updated by Adam Sutton almost 12 years ago
- Category changed from 11 to General
- Status changed from Need feedback to Accepted
- Assignee set to Adam Sutton
- Target version set to 3.4
The problem appears to be that default entries are not being created with default prefix, this has been changed recently (as part of IPv6 support) so that's probably what's happened.
Adam
Updated by Adam Sutton almost 12 years ago
- Status changed from Accepted to Fixed
- % Done changed from 0 to 100
Applied in changeset commit:c7aaa0b913b0a8f2c930a354ee1562c4d2a393e0.