Aidan13

Members
  • Posts

    40
  • Joined

  • Last visited

Recent Profile Visitors

299 profile views

Aidan13's Achievements

Rookie

Rookie (2/14)

2

Reputation

3

Community Answers

  1. Wish List: Love to be able to set certain file locations as a Favorite that will be at the top of the list when selecting locations for copy or move. Tim N
  2. Now that I look at this makes complete sense, not sure why I didn't see it before. Read part of the user shares wrong, I am still pretty new to linux systems I've read the User Share propably 3 times already and I'm only getting bits and pieces as I read. I'll keep reading. Thanks for the help Tim N
  3. So I have my Movie Share set to have 2TB (14TB drive) for minimum free space. I have 2 drives set as Included Discs. My allocation method is "Fill-Up". I copy/move my movie files from my windows PC to my UnRaid Server, using Dynamix File Manager plugin on my unraid server. This is my copy from/to location: /mnt/remotes/WindowsPC_Disc M/Video /mnt/disk5/Movies/ Not sure why but I have gone past my minimum free space on my 1st disk drive. my files are not automatically switching to my 2nd included drive. Not sure if it is my Dynamix plugin or I have a setting incorrect. I went a ahead and moved files from my full disc to my empty disc. Then I read that this was a no no. Moved files appear to be fine and my full disc is now showing it is below my minimum threshold. I was thinking that my copy to location being disk5 may be the reason?? Any help would be great. Thanks Tim N
  4. Finally got it figured out, going over Network Access again, I saw a little note saying network must be on "eth0"; lght bulb went off. I had taken apart my build again to add some fans and put it all back together & I hooked up my lan cable to the wrong port, its always the small things. Tim N
  5. Finally got it figured out, going over Network Access again, I saw a little note saying network must be on "eth0"; lght bulb went off. I had taken apart my build again to add some fans and put it all back together & I hooked up my lan cable to the wrong port, its always the small things. Tim N
  6. Finally got it figured out, going over Network Access again, I saw a little note saying network must be on "eth0"; lght bulb went off. I had taken apart my build again to add some fans and put it all back together & I hooked up my lan cable to the wrong port, its always the small things. All is right in the world, at least for today. Thanks to all who helped Tim N
  7. I'd like to see a simple copy of the file address. So where ever you are within the file structure of unraid I can click a button and this will copy the file address.
  8. This thread "about:blank#blocked for all WebUI links" By Alexstrasza gave me new info. The container CA form has a generic WebUI address of http://[IP]:[PORT:8096]. Change this to the generic address to the actual hard address eg. http://192.168.0.5:8096, this gave me a Timeout error but it is a change. The 2 addresses I find for jellyfin are the JELLYFIN_PublishedServerUrl: and the Port Mapping ip addresses. Both of these address give me a timeout error. Is there a different ip address that I should be using for jellyfin WebUI? Thanks Tim N
  9. 2/9/24 I have the same issue with all my dockers. I ended up deleting all my dockers and I reinstalled only 1 container so this problem was smaller for me. I also had the same issue as sasbro97 where my container did not show a web address in the port mapping area. When I reinstalled 1 container this solved the port mapping missing an ip address. Dizzienoo's post gave me some relief: With adding the ip address to WebUI at the containers CA form did change the aboutblank#blocked error to a "The connection has timed out" error, which gives me some hope. I'm thinking the ip address I have added to WebUI is incorrect. I have tried the JELLYFIN_PublishedServerUrl: ip address and the ip address shown for port forwarding both of these address gave me the timeout error. If anyone knows the correct ip address to use for the jellyfin WebUI, it would be brilliant if passed this on. Thanks Tim N
  10. does anyone know the actual IP address jellyfin uses for webgui. My port forwarding address is 172.17.0.2. My JELLYFIN_PublishedServerUrl: is 192.168.0.5 I have entered both of these directly in browser and get the error "The connection has timed out". I have also entered these into the Container Form for WebGui and this also gave me a timeout error. Makes me think these address are incorrect. At the very least I am not getting the about:blank#blocked error. At this point I will take any change as positive progress. Tim N
  11. Never mind found it: https://github.com/orgs/linuxserver/packages/container/package/Jellyfin That url takes me to here: https://github.com/linuxserver/docker-jellyfin/pkgs/container/Jellyfin Tim N
  12. Is there a way to see what address the webgui is using to open a page? I tried the 3 IP address shown in Docker Containers - port mapping and I get "The connection was reset" error. Tim N
  13. I am having a frustrating issue with the WebGui not opening a webpage. When I try to access the WebGui i get a blank web page with "about:blank#blocked". The app was working for a week or so, I was able to setup my media libraries and watch shows on my jellyfin clients. I just cant access the webgui from my windows PC or my tablet which was no problem before. I have disabled every security barriers on all my web browsers (chrome, firefox, brave and edge) with no luck. I have added web IP addresses as trusted site. I have shutdown & restarted server. Unistalled jellyfin and reinstalled (along with all my other containers) still get "about:blank#blocked". Now since i uninstalled and reinstalled jellyfin I cant access the webgui and I am unable to acces jellyfin from any of my clients. I've been at this for roughly 5 days and I am out of ideas. I'm hoping you can help. I've attached the jellyfin logs from when I last installed jellyfin container. Here also is a screen shot of my container basic stats Thanks for any help Tim N Jellyfin container Log - new instal.txt
  14. Reinstalled jellyfin container... still getting "about:blank#blocked". I have done everything I can think of turned off every security feature I can think of, added unraid server to trusted site, added the jellyfin port mapping ip address to trusted sites. I am back to NO on Use SSL/TSL, in managment access. I am at a loss, I really liked unraid for a lot of reasons but not being able to use docker is kindof a deal breaker. The most common reason given for getting the about:blank#blocked error is an address too long, or bad certificate. Now I am unable to open jellyfin from a web browser or my clients on the TV. Going from bad to worse... Thanks for all the help Tim N
  15. I noticed that, just didnt think much of it. This is the one container I didnt want to delete, I have deleted all other docker except jellyfin. I will do this now including image and rebuild this container. Ill let you know it this works. Thanks for help Tim N