mfwade

Members
  • Posts

    85
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

mfwade's Achievements

Rookie

Rookie (2/14)

12

Reputation

  1. This setup was used for nothing more than testing / lab use. It is not meant for production use. This not a tutorial on how to set up Unraid, VLAN's, routing, etc. It is expected that the individual setting this up has a basic understanding of how 'things' work. For this exercise I set up a 3 node distributed Minio cluster with 2 drives in each node. Your IP / DNS / Share / Drive / AppData / etc. locations may vary, set accordingly. You will need 3 IP's for this cluster: 192.168.10.241 192.168.10.242 192.168.10.243 You will need to set up DNS for this to work correctly: m1 - 192.168.10.241 m2 - 192.168.10.242 m3 - 192.168.10.243 Verify DNS is responding correctly: ping m1 ping m2 ping m3 They should all respond with the correct IP information Create drive / shares I creaded the drives / shares as follows: -minio-test -d1 -d2 -d3 -d4 -d5 -d6 Install the 1st instance of Minio: *Switch to Advanced View* Name: m1 WebUI: http://[IP]:[PORT:9001]/ Post Arguments: server --console-address ":9001" http://m{1...3}/data{1...2} Network Type: Custom: br0.10 -- vlan 10 (your network may vary) Fixed IP address: 192.168.10.241 Web UI: 9767 (leave as is - not needed in this configuration) Console UI: 9867 (leave as is - not needed in this configuration) Config: /mnt/user/appdata/m1 (locate on an SSD / cache drive) MINIO_ROOT_USER: (username must be the same on ALL instances) MINIO_ROOT_PASSWORD: (password must be the same on ALL instances) Remove original /data path variable Add 2 new additional path variables /data1: /mnt/user/minio-test/d1/ /data2: /mnt/user/minio-test/d2/ Create - do not start at this time Run Command: --name='m1' --net='br0.10' --ip='192.168.10.241' -e TZ="America/New_York" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Hulk" -e HOST_CONTAINERNAME="m1" -e 'TCP_PORT_9000'='9767' -e 'TCP_PORT_9001'='9867' -e 'MINIO_ROOT_USER'='username' -e 'MINIO_ROOT_PASSWORD'='password' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:9001]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/cheesemarathon/docker-templates/master/images/minio.png' -v '/mnt/user/appdata/m1':'/root/.minio':'rw' -v '/mnt/user/minio-test/d1/':'/data1':'rw' -v '/mnt/user/minio-test/d2/':'/data2':'rw' 'minio/minio' server --console-address ":9001" http://m{1...3}/data{1...2} Install the 2nd instance of Minio: *Switch to Advanced View* Name: m2 WebUI: http://[IP]:[PORT:9001]/ Post Arguments: server --console-address ":9001" http://m{1...3}/data{1...2} Network Type: Custom: br0.10 -- vlan 10 (your network may vary) Fixed IP address: 192.168.10.242 Web UI: 9767 (leave as is - not needed in this configuration) Console UI: 9867 (leave as is - not needed in this configuration) Config: /mnt/user/appdata/m2 (locate on an SSD / cache drive) MINIO_ROOT_USER: (username must be the same on ALL instances) MINIO_ROOT_PASSWORD: (password must be the same on ALL instances) Remove original /data path variable Add 2 new additional path variables /data1: /mnt/user/minio-test/d3/ /data2: /mnt/user/minio-test/d4/ Create - do not start at this time Run Command: --name='m2' --net='br0.10' --ip='192.168.10.242' -e TZ="America/New_York" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Hulk" -e HOST_CONTAINERNAME="m2" -e 'TCP_PORT_9000'='9767' -e 'TCP_PORT_9001'='9867' -e 'MINIO_ROOT_USER'='username' -e 'MINIO_ROOT_PASSWORD'='password' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:9001]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/cheesemarathon/docker-templates/master/images/minio.png' -v '/mnt/user/appdata/m1':'/root/.minio':'rw' -v '/mnt/user/minio-test/d3/':'/data1':'rw' -v '/mnt/user/minio-test/d4/':'/data2':'rw' 'minio/minio' server --console-address ":9001" http://m{1...3}/data{1...2} Install the 3rd instance of Minio: *Switch to Advanced View* Name: m3 WebUI: http://[IP]:[PORT:9001]/ Post Arguments: server --console-address ":9001" http://m{1...3}/data{1...2} Network Type: Custom: br0.10 -- vlan 10 (your network may vary) Fixed IP address: 192.168.10.243 Web UI: 9767 (leave as is - not needed in this configuration) Console UI: 9867 (leave as is - not needed in this configuration) Config: /mnt/user/appdata/m3 (locate on an SSD / cache drive) MINIO_ROOT_USER: (username must be the same on ALL instances) MINIO_ROOT_PASSWORD: (password must be the same on ALL instances) Remove original /data path variable Add 2 new additional path variables /data1: /mnt/user/minio-test/d5/ /data2: /mnt/user/minio-test/d6/ Create - do not start at this time Run Command: --name='m3' --net='br0.10' --ip='192.168.10.243' -e TZ="America/New_York" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Hulk" -e HOST_CONTAINERNAME="m3" -e 'TCP_PORT_9000'='9767' -e 'TCP_PORT_9001'='9867' -e 'MINIO_ROOT_USER'='username' -e 'MINIO_ROOT_PASSWORD'='password' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:9001]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/cheesemarathon/docker-templates/master/images/minio.png' -v '/mnt/user/appdata/m1':'/root/.minio':'rw' -v '/mnt/user/minio-test/d5/':'/data1':'rw' -v '/mnt/user/minio-test/d6/':'/data2':'rw' 'minio/minio' server --console-address ":9001" http://m{1...3}/data{1...2} Launch all 3 Minio instances. The logs will be littered with communications errors until all 3 devices are online and communicating with each other. Log example: When all 3 instances have been started and you see a screen similar to above (log output), log in to any of the Minio instances and click on Monitoring and then Metrics. You should see '3' Servers online and '6' Drives online. What's left: **Set up NPM - NGINX Proxy Manager so that when hitting the API or Console ports the requests are answered by any one of the 3 nodes. Right now I can configure to send to one of the 3 nodes. There is a custom area, just need to figure out how to fill that in. If anyone has experience with this, please chime in with examples / screenshots **Set up Prometheus for additional metrics and alerts. Anyone else what to take a crack at it? **Start messing with the S3 raw access policies - if anyone has experience with this, here is what I am trying to do. I need some help with tailoring the following: Allowing a specific user to log in, create/modify/delete/read/write to a bucket and then view all buckets under their username. As of right now I can have a user log in AFTER I create a username/password and bucket for them however, I have to specifically assign them permission to view the bucket I just created. I would rather just create the user account and then allow the user the ability to create their own. Original policy below that works when I log in as 'mfwade' and have created the bucket called 'mfwade' I can do nothing else... Formatting may be messed up due to copy and paste - context is correct.... Policy: { "Version": "2012-10-17", "Statement": [ { "Sid": "BucketAccessForUser", "Effect": "Allow", "Action": [ "s3:DeleteObject", "s3:GetObject", "s3:ListBucket", "s3:PutObject" ], "Resource": [ "arn:aws:s3:::mfwade/*", "arn:aws:s3:::mfwade" ] } ] } I hope this information helps others to set up something similar. If I can help in any way, please let me know.
  2. Check this out!!! I guess I need to write this up, will do later today / tomorrow.
  3. I was able to get it (single instance with multiple drives) working with 4 drives - in my case I just created 4 shares... This allows me the ability to create the bucket and tick off versioning, retention, etc. Post Arguments: server /data{1...4} --console-address ":9001" I deleted the original /data variable and created 4 new variables labeled data1 through data4, mounted to /data1 through /data4 respectively. So /data1 mounts to /mnt/user/test1/, rinse, lather, repeat. Now, just need to figure out how to add an additional server.
  4. Good Afternoon, Has anyone run a Minio cluster on their Unraid setup? If so, mind sharing the configuration - screen shots, extra parameters used, how its configured in Unraid? This would not be used in production, rather just messing around in a lab env. Thanks in advance. -MW
  5. Good Morning, Has anyone had an issue wherin the docker containers start to fail with an error message stating that (application failed to start) "Appfolder /config is not writable"? In addition, I am not able to write to any of the exported shares - e.g., TimeMachine reports errors, mounted shares, etc. This has happened on a few occasions previously and a simple reboot seems to fix it. Figured I would ask the group if this is something that needs to be explored further, possible bug, etc. For what its worth, my configuration hasnt changed i.e. change cache pools, add/remove drives, etc. CPU: Intel® Xeon® Gold 6226 CPU @ 2.70GHz Memory: 512 GiB DDR-4 Multi-bit ECC Ram usage: 7% Flash usage: 4% Log usage: 1% Docker: 47% If neeeded: Cache Pool Size: 3.8TB (2 drive mirror) Cache Pool FS: btrfs Used: 585 MB Free: 3.26 TB Log files attached. Thanks again. -MW hulk-diagnostics-20211110-1846_anon.zip
  6. Dumb question... Maybe I simply didnt see a spot for it in the settings. Is there a way to not display the persons email address/username/etc. (USER INFORMATION) on the page? Right norwit shows the Now Screening followed by the poster and then at the bottom shows something like: (TV-14), (1080p H.264), (English AC3 5.1), (Minutes), (% Watched,) (USER INFORMATION), (Platform)
  7. I dont use SWAG so cant comment there (use NPM instead). I see the following line in the nextcloud conf: 'overwritehost' => 'nextcloud.howardfarms.net', it should match your domain: 'nextcloud.awesomedomain.net', Ot, you simply didnt redact all of the information and in that case they should all match Let me know how it goes.
  8. NGINX Proxy Manager will do what you are looking for. Need only ports 80 and 443 open. You may need 32400 open for Plex as well (if you dont move to 443). For example: http://nextcloud.yourdomain.come => your IP (Dynamic of Static) =>NGINX => redirects to internal Unraid -- 192.168.x.x:port Same for others i.e. ftp, etc.
  9. Reboot fixed it. Still not sure what was going on. Containers were acting wonky, unable to write to shares, etc...
  10. Good Afternoon, Figured I would ask here before I just simply reboot... I am curious if anyone else has ever had an issuel like the following. When trying to create a folder on Unraid, I receive the following: This is something new that I havent experienced before. I tried searching the forums however, i guess my google fu isnt working and found no results. When trying to write from my Mac, i receive the following: Timemachine via SMB has stopped as well, not able to complete backups. I didnt even try from a Windows machine... I believe there are enough resources I have attached diagnostics as well. Thanks again. hulk-diagnostics-20210731-1336.zip
  11. Danuel, Post your Unraid setting for the Minio container. Here is how I have mine set. The CONSOLE port is now used for Web UI - management. The API port is what is used for client connectivity. Settings I used in Unraid (Advanced view): Reminder, when connecting software to perform backups, etc, (Arq, GoodSync, Cloudberry, etc.) you will connect to the API port. So, if using NGINX Proxy Manager, you would map the connection to 9769 (in the example above).
  12. Thanks to everyone for your help. All my Minio instances are now back up and all users are able to attach to the servers to perform backups, etc. Settings I used in Unraid (Advanced view): Reminder, when connecting software to perform backups, etc, (Arq, GoodSync, Cloudberry, etc.) you will connect to the API port. So, if using NGINX Proxy Manager, you would map the connection to 9769 (in the example above).
  13. Hello, Can someone post screenshots, tutorials, etc. of how they got this to work? I was able to clear the original issue: WARNING: MINIO_ACCESS_KEY and MINIO_SECRET_KEY are deprecated. Please use MINIO_ROOT_USER and MINIO_ROOT_PASSWORD No just need to figure out the following: WARNING: Console endpoint is listening on a dynamic port (34921), please use --console-address ":PORT" to choose a static port. Any help is sincerely approciated!
  14. Hello, Can someone post screenshots, tutorials, etc. of how they got this to work? I was able to clear the original issue: WARNING: MINIO_ACCESS_KEY and MINIO_SECRET_KEY are deprecated. Please use MINIO_ROOT_USER and MINIO_ROOT_PASSWORD No just need to figure out the following: WARNING: Console endpoint is listening on a dynamic port (34921), please use --console-address ":PORT" to choose a static port. Any help is sincerely approciated!
  15. Personally, I am not into having to make that many configuration changes, especially rooting a device... I would probably just stick with the double NAT and ensure the correct ports are forwarded through the ATT device to the Unifi. I found this - if you need it: https://www.att.com/support/article/u-verse-high-speed-internet/KM1010280/ Good luck and post back how you are progressing.