-
-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
403 forbidden - repeating #254
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
Have you tried not setting a user/pass during the wizard and does the same thing happen? MacOS / Docker Desktop isn't something we support/test on. |
Trying no credentials now. Waiting for scan to complete.
I am surprised by net=host not working as my hdhomerun tuner mapping completed. I think I remember that being an issue and having to look into. Came up with net=host as the likely workaround. Last time I tried this I think I hung on getting the tuner mapped.
So I deleted all contents in the config folder. Deleted TVH container and image in docker app. Using brave browser I try private window and go to the web interface. A login prompt comes up and clicking “sign in” or enter on the prompt does nothing. Refreshed the login prompr.
… On Jun 7, 2024, at 8:04 AM, j0nnymoe ***@***.***> wrote:
Have you tried not setting a user/pass during the wizard and does the same thing happen?
Host networking does not work on MacOS - it's not supported via docker desktop.
—
Reply to this email directly, view it on GitHub <#254 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AO46OM35G2G374SVQ56I3NDZGGOUDAVCNFSM6AAAAABI6Q5IS6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJUGY4TOMRXGU>.
You are receiving this because you authored the thread.
|
Reason I mentioned about host networking, last I checked, it's a docker desktop limitation, not a container limitation. |
Understood. In the passwd file I see values but they are not decrypting to md5. If I knew how to stop the tvheadend service within the container I think I could fudge my way through. Either changing the password files or scripting for first run. I think first run is what go me though. Is this relevant?: https://skarnet.org/software/s6/s6-svc.html
I see s6 in a lot of places when reading folder contents.
… On Jun 7, 2024, at 8:31 AM, j0nnymoe ***@***.***> wrote:
Reason I mentioned about host networking, last I checked, it's a docker desktop limitation, not a container limitation.
—
Reply to this email directly, view it on GitHub <#254 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AO46OM42XINZBNTQNZIZTADZGGR2TAVCNFSM6AAAAABI6Q5IS6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJUG42DAMRRGI>.
You are receiving this because you authored the thread.
|
Could you try a different browser? Brave might be breaking it. You shouldn't need to do any messing around like stopping services etc. |
On safari I receive new behavior. Entering nothing in the login boxes and pressing sign in sends me to a 401 Unauthorized page with the two boxes showing in the middle to start a new Default login or just a New login. This is in a private window.
Is there an option, say within run options, to bypass all authentication? On local network with only two devices ever accessing, me as only user. Dont need it.
Either by Net=host or by port number I can access the gui. If you think net=host is relative to not being able to login I can change it. Brave was authored by the person who invented javascript so I thought that it would be better test than safari. Since the hdhomerun mapped and this is known to need net=host for TVheadend to work with the hdhomerun I am thinking I should try other methods first?
… On Jun 7, 2024, at 8:40 AM, j0nnymoe ***@***.***> wrote:
Could you try a different browser? Brave might be breaking it. You shouldn't need to do any messing around like stopping services etc.
—
Reply to this email directly, view it on GitHub <#254 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AO46OM2DIM53NFZOV7WR5ALZGGS5FAVCNFSM6AAAAABI6Q5IS6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJUG42TKMZSHE>.
You are receiving this because you authored the thread.
|
If you don't want authentication, just don't set any user/pass during the setup wizard. |
You just asked me to try that and after I did I reported back that it didnt work:
Either the login promt refreshes on brave browser or I am brought to a 401 Unathorized page on safari.
Not setting a login doesnt work. I still get prompted.
So its not worth asking for instruction how to manually change the password values in the passwd file? That seems like it would be the most logical place to look if I have credentialing problems. What is the hash on the values in that file?
… On Jun 7, 2024, at 9:05 AM, j0nnymoe ***@***.***> wrote:
If you don't want authentication, just don't set any user/pass during the setup wizard.
—
Reply to this email directly, view it on GitHub <#254 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AO46OMY5AURR2CSBFGYCQELZGGVYXAVCNFSM6AAAAABI6Q5IS6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJUG44TMOJYGE>.
You are receiving this because you authored the thread.
|
You seem to have something else interferring with you install, I'm able to deploy tvheadend with no problems here but using Linux/Docker Engine. The user details to my knowledge are all stored in the |
This is month 6 of not being able to install and use TVHeadend from docker (linuxserver) and across 3 different platforms. All with this exact issue. Intel and mac mixed. I will look in the config folder for user info that isn't aligning.
Most of the solved threads I see talk about resetting the user password via cli or killing the running instance of and restarting it up with —noacl or similar. I was hoping to accomplish one of these if not both before I ran in to the “works for me” reply. Thank you for your assistance. I will simply look for alternate software to run. No issues with any other containers. Just this one.
… On Jun 7, 2024, at 9:29 AM, j0nnymoe ***@***.***> wrote:
You seem to have something else interferring with you install, I'm able to deploy tvheadend with no problems here but using Linux/Docker Engine.
The user details to my knowledge are all stored in the /config volume for tvheadend.
—
Reply to this email directly, view it on GitHub <#254 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AO46OM2RIWYKLH35FHWG7B3ZGGYTVAVCNFSM6AAAAABI6Q5IS6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJUHA2DGMRSGY>.
You are receiving this because you authored the thread.
|
Appreciate that you might've been having this issue for 6 months on various platforms, though you've only opened this issue a couple hours ago. The issue is, specifically with the information you've provided in the issue, we just don't recommend MacOS nor docker desktop in any form for our containers. If you can replicate this issue on a linux host using docker engine (not desktop) then we can attempt to replicate. |
Understood. Thanks for letting me know. I was able to get a different container of tvheadend to get past the login issue but failed to stream a channel properly so I am closing the issue. |
Is there an existing issue for this?
Current Behavior
Nearing completion of initial configuration I am suddenly brought to a login page where the values I entered either during "wizard" or manual entry are not observed for password. I can get to the passwd file in docker shell but following all help posts I can find I cant kill the tvheadend process to modify the startup. It respawns. Not familiar with the commands to stop the service as none that are documented are working. My yaml:
services:
tvheadend:
image: lscr.io/linuxserver/tvheadend:latest
container_name: tvheadend
environment:
- PUID=501
- PGID=20
- TZ=America/New_York
- net=host
- RUN_OPTS= -C
volumes:
- /Users/darylkuchay/media/containers/tvheadend/config:/config
- /Volumes/dvr:/recordings
ports:
- 9981:9981
- 9982:9982
#devices:
#- /dev/dri:/dev/dri #optional
This is on macOS and with the uid/gid align with my user login and are working with several other containers.
I had the same issue when I was on previous hardware of a MSI cube N100 running opensuse leap.
If I missed docs please link.
Expected Behavior
I should be able to login to the web interface with the password that I set during setup. or during the wizard. I have tried both and this has repeated over ten times. I cant get out of the forbidden 403 repeating loop with the docker compose file as exampled. I have tried with and without the-C run option as well. If there is documentation on how to stop the container and adjust its startup and I missed it please link. Unfamiliar init system.
Steps To Reproduce
Use supplied docker-compose and add own directories and tested.
Environment
CPU architecture
arm64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: