HocEman

Members
  • Posts

    12
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

916 profile views

HocEman's Achievements

Noob

Noob (1/14)

3

Reputation

  1. I upgraded and can confirm that I am no longer having the nginx issue. Thank you @EDACerton!!
  2. Yes, I was using the /minio on the end. Unfortunately, removing it still didn't work. It passed the initial connection test, but failed when running the backup. I am happy to say I did get this to work with the reverse proxy, and @NeoMatrixJR your comment led me in the right direction, so thank you! I created a sub domain for Minio instead. My configuration in Duplicati uses minio.mydomain.org and the ssl checkbox. The reverse proxy picks up the complete domain minio.mydomain.org and properly uses proxy_pass to the minio docker on the correct port. I am guessing something within minio does not like the /minio on the url.
  3. I have LetsEncrypt, Minio and Duplicati dockers running on Unraid on my local network. I have multiple remote PCs (Windows) running Duplicati and backing up to Minio on my Unraid server over the internet. I have reverse proxy setup for Minio as a subfolder (https://mydomain/minio) and I can successfully connect to Minio via a web browser both locally and remotely using that URL. If I use SSL and mydomain/minio in Duplicati from the remote PCs I get the "Failed to connect: The request signature we calculated does not match the signature you provided. Check your key and signing method." error. If I use that same URL on my local network I get a different error from Duplicati: "Failed to connect: Error making request with Error Code Forbidden and Http Status Code Forbidden. No further error information was returned by the service." The only way I can successfully connect to Minio through Duplicati is if I configure port forwarding on my router and use mydomain:portnumber as the URL (non SSL) both locally and remotely (I can use the IP Address:portnumber locally as well). It would be nice to have this working via the reverse proxy so it is more secure and I do not have to have that port open and exposed, but I just can't figure it out. Thanks in advance to any suggestions!
  4. @Tango I am having this exact same problem. Did you ever find a solution?
  5. Sure, a reboot is never a bad idea when things are not working properly, more so when it comes to Windows systems, but in this case it is worth a shot.
  6. I recently upgraded to 6.4 and this plugin is working for me. I did not have to re-install, it continued to work the same as it had on 6.3. Also in reference to your comment - "I noticed also that I don't have these mentioned empty recycle bin icons on the 'shares' page" - I do not have any recycling bin on the Unraid Shares page, I never have. I believe you are referring to the ".Recycle.Bin" folder that gets created when you delete something through SMB. This folder is located in the ROOT of your share and is visible through Windows Explorer. For example, if your Unraid SHARE is called Media and all your movies, TV Shows, etc. are in folders underneath it, the .Recycle.Bin folder will show up in the Media folder once you delete something in one of those sub folders. See the attached screen shot. I deleted a file from \\unraidname\media\Kids Movies from windows explorer. Now I have a .Recycle.Bin folder located at \\unraidname\media and the delete file is located in it.
  7. Were you able to accomplish excluding specific files or folders? I am looking to exclude a few sub folders in a share and can not get it to work. Any help would be appreciated. Thanks!
  8. OK, so I figured it out. @jack0w you actually did point me in the right direction. When I deleted my docker.img and reloaded the containers I used MY templates. I deleted my docker.img again, and this time installed the plex container from Community Applications and it worked. I use the LazyMan channel in Plex and it recently stopped working. It requires some edits to the hosts file to work. I was trying to edit the hosts file IN the docker so I tried to map the /etc container path to a host path in my template, and that caused the problem. I actually learned a lot from this mistake: 1. Unraid creates the /etc/hosts file every time the server is restarted so you will lose any edits (which was my problem in the first place, I rebooted my server and lost the edits I made months ago) 2. Docker containers (or at least this one) use the /etc/hosts file FROM the Unraid server - pulling it in when the docker is started. So any change made to the file on the server will not be seen by the docker container until after the container is restarted 3. There is an awesome plugin called "User Scripts" that allows you to create your own scripts (stored on the Unraid Flash drive) and run them through the GUI or on a schedule So this container is functioning properly again, and I also have the LazyMan channel working again by creating a simple script that adds the edits required to the Unraid hosts file using the "User Scripts" plugin.
  9. Out of the blue my plex docker container will not start. It gives this error in the log: importas: fatal: unable to exec /etc/s6/init/init-stage1: No such file or directory I have tried removing and re-adding the container, re-adding the container and pointing to a different config folder, deleting the container and the docker.img file. I still get this error. Any thoughts or other things to try? I am able to successfully install and run the plex media server docker container from the official plex repository (installed from community applications). So I think the issue is with the Linuxserver.io docker. I appreciate any help. Thanks!
  10. I was having the same problem, and figured out a solution. The codec needs to be updated inside the docker. Here are the steps I took to accomplish this: 1. ssh into your Unraid server (I am on Windows and use Putty) 2. Run the following command to be able to make changes inside the Air Video HD container: docker exec -it <container_name> bash (<container_name> should match what you see in the Unraid GUI, my was "AirVideoHD" so my command was "docker exec -it AirVideoHD bash" without the quotes) 3. You should now be making changes inside the container - the h.265 codec plugin is not available from the Ubuntu repositories, so you will need to add a repository: sudo apt-add-repository ppa:strukturag/libde265 4. Update the packages from the newly added repository: sudo apt-get update 5. Install the h.265 codec plugin for VLC: sudo apt-get install vlc-plugin-libde265 6. Type "exit" to return to the Unraid command line (No longer making changes to the Air Video HD container) 7. Restart AirVideoHD docker container from Unraid GUI (may not be necessary, but I wanted to make sure the changes stuck after the container was restarted) I was successfully able to stream and download videos using the h.265 codec and no longer received the "missing codec" error. (Air Video Converted the files to download to iOS) I am not sure if this container is still being maintained, as it has been over a year since the last update, but if it is, then hopefully this can be included in the next update. Hope this helps anyone having problems playing h.265 video files!
  11. I was able to work around it by setting a static IP address on the Ubuntu 16.04 VM. Not sure why it couldn't pull one from DHCP.
  12. I am experiencing the same thing, although I am running nRAID server Plus, version 6.1.9. My settings are similar to yours, and I am using br0 as the network. As you said, Ubuntu 14.04 works as expected, so something in 16.04 isn't playing nice. Unfortunately I do not have any ideas of what it is. Hopefully some more people will try to upgrade to Ubuntu 16.04 and this problem will see some more action.