entourage2111

Hi all, I've been using Unraid for over 7 years without issue. I was on Unraid 6.8 for the longest time. A few months ago I decided to upgrade from 6.8 to the latest 6.12.10 (latest at time of update). I really regret that decision because, since then my server experience has completely changed for the worse... 1) The server randomly hangs after a few hours or sometimes days of use. I'm not able to even access the server locally and have to hard reboot to get back in. 2) If (1) doesn't happen, then I can access the server locally, but only to find all the docker app have closed. I have to take array offline then online to get it working. Without doing this, when I try to start an app I get the '403 error'. Again, this happens randomly after a few days. My diagnostics logs attached from today which I've pulled after a hard restart of the server. Appreciate any assistance / guidance anyone can provide. tower-diagnostics-20240602-1114.zip

I recently upgraded this docker and now I can't get on the 'history' page when accessing the docker through reverse proxy. Any one have any ideas?

Yes that's exactly what I was thinking. Use cache normally but if it detects i.e. 7 drives spun up, then cache = no and use turbo write. I guess it's me being very picky though, only a few clicks to operate.

Thanks for clarifying.👍

If in the shares settings, use cache is set to yes, does the 'auto' setting for write mode in disk settings bypass the cache if all the drives are spinning at the time of write?

Hi, silly me - that was the issue! I've now switched and it's all working. Thanks for taking the time to help me.

Hi everyone, I hope someone can provide me with some advice as I’m pulling my hair out over this. I followed the tutorial posted by spaceinvaderone (linked below) which shows how to setup letsencrypt https://www.youtube.com/watch?v=I0lhZc25Sro&t=753s Unfortunately as soon as I run letsencrypt, I get the error message in the log which states: Failed authorization procedure. blabla.duckdns.org (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://blabla.duckdns.org/.well-known/acme-challenge/wL2-Ux5ap6jNeo4TLJ44KY9Rp9OBcYjSqAZVlbBxnwA: Timeout during connect (likely firewall problem) I’ve made sure with my ISP (Virgin media-UK) that both port 80 and 443 are not blocked. I just can’t seem to get this setup. Can anyone guide me on this? Port forwarding looks to be fine on the router as I’ve looked at three different videos which explain how to do it on that router. Please see picture to below to show how its setup on the router side... Can anyone help? I would really appreciate it

is anyone else getting the error "your version is too old, please update" and then the container closes. Anyone have a fix? I can't see any option to update...

I actually have done that and according to every cert checking website, the domain hamza219421.duckdns.org has a fully verified SSL certificate. Problem is, when I try to VPN into the server though, I still don't get the green lock despite the certificate being verified by every website I check.

I used this video posted by a popular member on this forum to setup a VPN to my home network so I can conect to unraid. For the latter half of the video, because I do not have my own domain name, I used duckdns and lets encrypt to create an SSL certificate. The docker did the job fine for what I needed it to do, I just needed advice on how to get the green lock when accessing my server from outside home.... I hope that makes sense

That's the thing. I don't know how to get it to go to https:// on the docker install page of letsencrypt. I've attached my settings with this post. Of course, when I try to go to https:\\192. bla bla when connected to the VPN that page doesn't load. But when I type in just the IP of my server, it goes to it just fine (but at the cost of not being secure)

Hi, Hoping someone can help me with regards to an ssl certificate problem I seem to have when using this docker to get certified. I used this docker to generate a ssl certificate for my duckdns address and everything went as planned. Even when I use various ssl certificate checking websites, they all show that the link is secure. However, when I access my home through VPN using chrome, the green padlock does not show and I'm left with an (information logo inchrome) which shows I may be at risk. Does anyone know how I can resolve this issue? FYI, the domain address for me is [email protected] Can I also add that when I try to access unraid locally at home, I don't get a 'green padlock' then either. I figure that doesn't matter since I'm at home locally but would love to have that special 'green padlock' when I try to access from elsewhere. Thanks a lot for the help