hiddenpcmaster

I noticed the lack of a response over the last 16 hours so.... On behalf of the Unraid team, Welcome and I feel the same way too! I also enjoy the community support.

Instead of browsing, try putting in you unraid server's IP address. Then map the drive if successful.

Thank you Trurl. Now I see what you mean.

What a RUSH!!! Thank you Squid! My starship is fully capable of reaching warp 10 now with ease! Seriously, I'm not sure how I managed to get my docker image on the array in the first place, but after following your excellent instructions to the letter, Success! I have to admit it felt like a leap of faith but after seeing those containers re-populate, well, you should have seen the grin on my face. One small issue is a custom network deleted itself during the process, but was a simple fix. You made my day sir! Thank you again.

Gentle nudge. I know this community is one of the best around. I'm sure somebody can help me right?

Changing your flash drive I would recommend use of the USB Flash Creator tool for the easiest and most streamlined experience.

I've been using Unraid for ever! But since a couple of updates ago I've noticed slowness when updating/pulling docker containers. It appears to happen on the Extracting stage of the layers and it's directly correlated to the layer size (larger layer == longer extract time). It's gotten bad enough where I can't update some of my containers. I'm not sure where to start for troubleshooting this. (running 6.12.2). Diagnostics attached unraid-diagnostics-20230708-1028.zip

Update: I got my instance of MeshCentral up and running on UNRAID flawlessly since this was posted following IBRACORP's video

Stardate 101058.95 Upgraded from 6.11.5 to 6.12 with no issues. Thank you for the great work everyone!

I've been trying to get this to work for a few weeks now. anyway, whatever free time I can find. I loaded the container typhonragewind/meshcentral behind NGINX proxy manager and can't get agents to load on either remote or local computers. Does anyone with a similar setup have a "sample" config.json file that I can see to compare with mine? My json file is clean but I'm coming up with a 502 gateway error now.

Captains log : Stardate -300135.9916286149 Updated from 6.11.2 to 6.11.3 with No issues.

Captains log : Stardate 100443.35 Updated from 6.11.1 to 6.11.2 with No issues. Keep up the good work!

Captains Log: Stardate-52822 I just Upgraded from 6.9.2 to 6.10.2 With all the activity in the forums about some issues relating to 6.10, I opted to wait until the next release. I'm happy to report NO ISSUES. Thank you all for the hard work, everything is working!

I use the FREE version of Veeam backup for windows. It works flawlessly. Sent from my iPhone using Tapatalk

JasonK and Burizado Thank you! I've turned off "strict port forwarding" by saying "no" and now I'm up again! (toronto) Just curious, are you using the nextgen endpoints file or the original? (I am experiencing a hit on performance though but it's working, After running for awhile it's running much better)

Almost an ex-PIA user here. Now all PIA server locations that used to support port forwarding are all down. Even though I have over a year and a half left on my subscription I'm willing to jump ship. Does anyone have a recommendation for a new "deluge" vpn provider? and why? Thank you.

PIA User here. I just had the issue occur where Deluge was completely down and couldn't log into the Gui. With a lot of combing through this topic I simply changed my PIA server location that supports port forwarding and low and behold, I'm back up again. I hope this helps someone.

How can you only choose one thing I like best about unraid?? That's almost impossible! Virtual Machines!!!! About what I would like in 2020, If you kept it just the way it is, I'd be very content.

Try using the following syntax http://localhost:10090/ It just worked for me.

Thank you burtjr. I appreciate your input also.

johnnie.black You have made my day! I'm really at a loss as to why this happened to begin with but greatly appreciate your sending me in the right direction.

Thanks! I'm getting the following error: root@unraid:~# xfs_repair -v /dev/md1 Phase 1 - find and verify superblock... - reporting progress in intervals of 15 minutes - block cache size set to 699976 entries Phase 2 - using internal log - zero log... zero_log: head block 216043 tail block 213757 ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this. root@unraid:~# Can you tell me what this means?

Help? What should I do? unraid-diagnostics-20170331-1644.zip I didn't even realize one disk was unmountable until after I found data loss. Other than that the disk's smart status is reporting A.O.K. I would really appreciate any steps I need to take. Thank you. Walter