snolly 5 Posted March 14, 2020 Share Posted March 14, 2020 Is it just me or this has come back in 6.8.3? 1 Quote Link to post
sniffles 0 Posted January 3 Share Posted January 3 yep i am having the issue with updating the web ui value. Ran into it when i stood up a second instance of a docker image and tied it to a new port. everything works fine and i can get to it by manually entering the port, but after updating the web ui value it still takes me back to the one that came as a default. Quote Link to post
EthanBB 1 Posted February 8 Share Posted February 8 Good evening, is fix for this being worked into 6.9? Or even already addressed in beta? Thank You! Quote Link to post
Squid 2983 Posted February 8 Share Posted February 8 So far as I know, every thing works 100% perfectly. Unless you can give step by step on what you're doing when it's giving the wrong URL. Quote Link to post
titansilber 1 Posted February 22 Share Posted February 22 I'm running into this problem when creating jellyfin containers (default 8096). I'm having issue with iGPU hardware transcoding, so I tried creating a new, separate jellyfin container (8099) in addition to the existing one (8098). Then I nuked both of them and tried just re-creating one, which now only goes to the container default of 8096. Quote Link to post
30 posts in this topic Last Reply
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.