danktankk

I changed the location of `Docker vDisk location: /mnt/user/system/docker/docker.img` to `/mnt/cache/system/docker/docker.img` and this seems to have *slightly improved the responsiveness of the webUI. Still not enough to matter unfortunately. Still up for ideas.

I like the functionality of the `LAN/WAN` option very much and think it is definitely something that is needed, however I use cloudflare subdomains with nginx and authelia for both LAN and WAN. How do I set this up so that `LAN` points to `subdomain.domain.one` and `WAN` points to `subdomain.domain.two`? I do not ever need it to point to `IP:PORT` - even for the unraid server. Currently it just adds the entire sub.domain.com:port for every container lol Thanks for any help

I have 2 cache drives. Both NVME. One for Plex by itself and the other for the rest of my appdata. That is definitely not the issue to my knowledge Thank you for the reply, but you not experiencing any lag at all is dubious, but I can't prove you wrong. Are you running the webUI on the actual server?

Is there any way to improve the load times of the unraid webui? I have used unraid for years and have never really been happy with the sluggish nature of the interface. I realize this is not a bug - that I know of. Im not asking for a miracle here or anything of the sort. I am just hoping that someone might have found a way to get the webUI to perform better. I am sure a lot of us have had the issue with waiting an inordinate amount of time to get it to load even when unraid is running just fine. I am not talking about when there are issues, a container starting, processes processing, lightning hit, the world exploding, etc... Maybe there is a better way to interact with the UI for unraid than using a browser per se? If there is, please let me know. To recap or TL/DR; In general, is there anything I can do to improve performance/responsiveness in my browser/aternative access method to have a better UX? SSH and CLI are fine, so that doesnt need to be an answer

I am getting an error for grafana in the logs showing a userId=0 I dont have a user 0, I do have user 1, 2, and 3 though. Here is the error message I am getting spammed with. There is no username assiciated with it that i see either. I am using unraid 6.10.3 I dont understand this error message. What can I do to correct it? What is userId=0? Thank you. I also have this container installed, and under installed apps, it is there, but when I look for this container in CA, it says it isnt installed. Just something else strange going on that I noticed.

I did something similar, again with help from @halienelf docker exec -it mongo mongo db.adminCommand( { setFeatureCompatibilityVersion: "5.0" } ) exit works fine. EDIT: fwiw, if your container is named something different than mongo, then chg the first mongo to match the container name.

I just wanted to add my 2 cents to this thread to thank @Squid for keeping this one alive. I also think this should be integrated into unraid 6.x.x for those of use with a lot of containers. It is a "must have" for me.

Im not sure about that. Hopefully someone else may know

A quick fix until setting the featureCompatibilityVersion higher, is to add `:5` to the tag and it will work as expected. Credit goes to @HalienElf.

jdupes is outdated by almost a year now but says its up to date in nerd pack. Any chance this can be looked into?

i never could get this latest version to display the icons for dockers or VM's. I guess it doesn't really matter now as development for this is gone now anyway. Was a good run. Thanks

For me, the lockups were caused by running a cron backup job for single, selected appdata from userscripts. This interfered with the backup/restore appdata plugin in settings as they were trying to run at the same time. Once I changed the time to something else, it never locked up after that. I would turn off all cron jobs if you use any and see if that helps your issue.

Im having what is probably an easy fix, but I havent been successful yet. When I run: php artisan register:app appname I am getting the error: Could not open input file: artisan I have tried bashing into the container and using the console link as well. I have tried various folder locations from heimdall root and further in as well to run the command. Any help would be appreciated. I am sure I am missing something simple. Thanks! EDIT: Got it. Never mind...

I'm at about 40 days now in 6.9.2 It wasn't hardware for sure. Sent from my SM-G996U using Tapatalk

lol ok thanks for the update

thanks ill give that a try

If you are referring to the RAM speed, yes I did that a while back. Sent from my SM-G996U using Tapatalk

Thats definitely an option, but I think I will just remove the plugin. Thanks for the reply.

I have the same issue. My system is AMD and inexplicably freezes about every 3 days or so and requires a hard reset. No syslog errors... Nothing... No help either. It's not hardware for sure. Sent from my SM-G996U using Tapatalk

Simply ignoring this message isnt that easy when you have to look through your log files and see hundreds if not thousands of these messages. Its a lot to sort through. Is there a way to keep this out of the log files at least?

Awesome. Thank you!

Using this command I am able to stop the extremely annoying log entry: nvidia-smi --persistence-mode=1 Is there a way to make this command stick? It doesnt stay in this mode permanently after using it. Any help is appreciated. Thanks!

I still dont have this particular issue as the RAM is still humming along just fine @ 3200MHz without any issues. But it is an interesting topic for sure - Albeit nothing to do with what my problem is/was. Running for 3+ days fine without any issues still. I wont say its good until after a week or more though.

Maybe you should reread what you quoted me typing. I didnt say it was a secret. I didnt say it wasnt a "fact." What I said was that it was a limitation, which is exactly what it is. Im not sure there was any reason at all for your post.

Im sure no AMD owner has any issue at all with this... lol I am surprised that I have never known of this issue. Why isnt there more backlash as a result of this ridiculous limitation? This isn't my issue (for now) but it easily could be one day. I gotta say this kinda pisses me off.