Important update!

The CoolerControl devs are now maintaining an official Docker container so I will be deprecating mine. I have updated the template, repo, etc to reflect this, and added a warning in the logs. If you are already running the container you can update the repo to coolercontrol/coolercontrold:latest and it should just keep on working! Thanks for everyone's support!

I'm attempting to create a new profile and apply it to my fans, but I get an error message that the profile could not be applied. Are there any logs anywhere I could look at?

4 hours ago, Krakout said:

I'm attempting to create a new profile and apply it to my fans, but I get an error message that the profile could not be applied. Are there any logs anywhere I could look at?

You can look at the logs in the container by clicking the CoolerControl icon/logo in the top left.

Just now, guniv said:

You can look at the logs in the container by clicking the CoolerControl icon/logo in the top left.

Facepalm

I was looking for logs in the app...

Just now, Krakout said:

Facepalm

I was looking for logs in the app...

Yep, in the app. The Docker container.

19 hours ago, guniv said:

Yep, in the app. The Docker container.

Ok, here it is:

WARN coolercontrold::api] Internal Error: Error on nct6795:fan1 for Manual Control - Unable to set pwm_enable for /sys/class/hwmon/hwmon2/pwm1_enable to 1. Most likely because of a limitation set by the driver or a BIOS setting; Error: Read-only file system (os error 30)

Going through this thread I see there was an option to switch from read only to rw (in a screenshot), but I don't have this option. Should I run it as privileged?

9 hours ago, Krakout said:

Ok, here it is:

WARN coolercontrold::api] Internal Error: Error on nct6795:fan1 for Manual Control - Unable to set pwm_enable for /sys/class/hwmon/hwmon2/pwm1_enable to 1. Most likely because of a limitation set by the driver or a BIOS setting; Error: Read-only file system (os error 30)

Going through this thread I see there was an option to switch from read only to rw (in a screenshot), but I don't have this option. Should I run it as privileged?

Did you read through the setup guide included in the container's description? You need to go mount your fans to the container. It sounds like you only have hwmon mounted at the moment, which is included in the template as read-only.

15 hours ago, guniv said:

Did you read through the setup guide included in the container's description? You need to go mount your fans to the container. It sounds like you only have hwmon mounted at the moment, which is included in the template as read-only.

God dammit, I'm so stupid. I had done it initially, but must've lost it when I was trying to get it to work a long time ago... thanks!

On 6/19/2025 at 8:48 AM, guniv said:

My best guess here is that perhaps the CoolerControl container is starting before the script that enables drivetemp has a chance to start.

Maybe one way around this would be to uncheck "Autostart" for the container in the Docker tab of Unraid and add this line to the drivetemp script:
docker start CoolerControl

So that will start the container after drivetemp has been enabled.

On 6/19/2025 at 8:48 AM, guniv said:

My best guess here is that perhaps the CoolerControl container is starting before the script that enables drivetemp has a chance to start.

Maybe one way around this would be to uncheck "Autostart" for the container in the Docker tab of Unraid and add this line to the drivetemp script:
docker start CoolerControl

So that will start the container after drivetemp has been enabled.

THANK YOU.

I think this is an important consideration for all users of this container. I made a merge request for the CC docs; hopefully I contributed correctly.

dang, I installed this per guide: https://docs.coolercontrol.org/installation/unraid.html
but only my cpu fan showed up. case fans and other sys fans are nada even with the added driver downloads

1 hour ago, ratmanjones said:

dang, I installed this per guide: https://docs.coolercontrol.org/installation/unraid.html
but only my cpu fan showed up. case fans and other sys fans are nada even with the added driver downloads

Yeah, driver support can be iffy and some motherboard manufacturers tend to have better support for this than others. If you manage to get anything working, and if you think the docs should be updated to reflect it, please let us know!

Am I missing something or is there a way to get alerts to go from the Docker to the Unraid Notification system. When I try to create a new alert I just get a weird windows popup:

8 minutes ago, Arbadacarba said:

Am I missing something or is there a way to get alerts to go from the Docker to the Unraid Notification system. When I try to create a new alert I just get a weird windows popup:

There is not a way to have CC send notifications to Unraid's notification system.

Figured out what I was doing wrong... I had more than one UI window open and needed to close them all and restart the Docker

OK, how about a way to include a temperature from a Windows VM? As a way to add the GPU temp and fan speeds to the list so that in the event of a hot running GPU I can spin up the case throughput fans?

I have my Case fans running off the cpu to some extent but also have them spinning up if a drive gets hot... Would be great to add the GPU into the mix.

I also have a USB thermistor that I have been wanting to get into the mix as well... But I haven't tried very hard yet.

10 hours ago, Arbadacarba said:

OK, how about a way to include a temperature from a Windows VM? As a way to add the GPU temp and fan speeds to the list so that in the event of a hot running GPU I can spin up the case throughput fans?

I have my Case fans running off the cpu to some extent but also have them spinning up if a drive gets hot... Would be great to add the GPU into the mix.

I also have a USB thermistor that I have been wanting to get into the mix as well... But I haven't tried very hard yet.

If it's a device being passed through to a VM then Docker/Unraid/CoolerControl would not also be able to access it. That would be something you'd set up in the VM. I know the Windows program FanControl is very very similar.

But is there a daemon for windows that can pass things back to coolercontrol?

If my second system were a linux machine I understand I could pass sensor data back to a single instance can't I?

Please understand... I LOVE this thing. In less than 2 days I've been able to fine tune my fans in the server that sits next to my desk so that it is nearly silent 90% of the time... and spins up correctly when it needs additional cooling.

Thank You SO much.

Another thing though: I've noticed that if I'm watching youtube videos they stop and stutter when I have the CoolerControl graph open... I run a little tablet monitor on my desk to show me stats and such and I've had it running since I installed this to monitor and adjust the cooling system.

I generally let videos run in a window and have been suffering a lot of buffering that wasn't there before. I just noticed that if I close the Graph Tab it instantly recovers and starts up again as soon as I go back to the graph..

I just launched the graph on the tablet natively not acting as a monitor for the PC and it seems fine... So I guess it's not a server issue but rather something in Edge...

Thanks Again

Seems like I can leave it running in chrome as well... So it's just doing something funny to edge...

UPDATE - It's not just CoolerControl that is doing it... I suspect the issue is with Edge not CoolerControl

Edited April 5Apr 5 by Arbadacarba

5 hours ago, Arbadacarba said:

But is there a daemon for windows that can pass things back to coolercontrol?

Not that I know of. I would be surprised if there was.

5 hours ago, Arbadacarba said:

Another thing though: I've noticed that if I'm watching youtube videos they stop and stutter when I have the CoolerControl graph open... I run a little tablet monitor on my desk to show me stats and such and I've had it running since I installed this to monitor and adjust the cooling system.

I generally let videos run in a window and have been suffering a lot of buffering that wasn't there before. I just noticed that if I close the Graph Tab it instantly recovers and starts up again as soon as I go back to the graph..

I just launched the graph on the tablet natively not acting as a monitor for the PC and it seems fine... So I guess it's not a server issue but rather something in Edge...

I am guessing that displaying the CC page in a browser takes a lot of resources on the system showing the page.

This is veering into general support for CC and I'm mainly here to help with Docker specific issues. If you want additional help with setup or reporting bugs I would join the discussion on the Discord.

Will do thanks

I can't get my Nvidia GPU to be detected. The drivers are installed correctly though, because I can see the temps display correctly on the unraid dashboard. I've tried adding --gpus=all and --runtime=nvidia, but no dice. I'm running in privileged mode and can see and control other devices just fine.

This is what I get in the logs:

[2026-04-20T18:06:25Z INFO coolercontrold] Super-I/O hardware detection disabled by environment variable

[2026-04-20T18:06:25Z INFO coolercontrold] Initializing Devices...

[2026-04-20T18:06:25Z INFO coolercontrold] Liquidctl Integration is Disabled

[2026-04-20T18:06:25Z INFO coolercontrold::repositories::service_plugin::service_plugin_repo] Initialized Service Plugin Devices: {}

[2026-04-20T18:06:25Z INFO coolercontrold::repositories::gpu::gpu_repo] Initialized GPU Devices: {}

[2026-04-20T18:06:25Z INFO coolercontrold::repositories::hwmon::devices] Could not read PCI ID database: pci.ids database not found at any known path, device name information will be limited

23 minutes ago, BreakfastPurrito said:

I can't get my Nvidia GPU to be detected. The drivers are installed correctly though, because I can see the temps display correctly on the unraid dashboard. I've tried adding --gpus=all and --runtime=nvidia, but no dice. I'm running in privileged mode and can see and control other devices just fine.

This is what I get in the logs:

[2026-04-20T18:06:25Z INFO coolercontrold] Super-I/O hardware detection disabled by environment variable

[2026-04-20T18:06:25Z INFO coolercontrold] Initializing Devices...

[2026-04-20T18:06:25Z INFO coolercontrold] Liquidctl Integration is Disabled

[2026-04-20T18:06:25Z INFO coolercontrold::repositories::service_plugin::service_plugin_repo] Initialized Service Plugin Devices: {}

[2026-04-20T18:06:25Z INFO coolercontrold::repositories::gpu::gpu_repo] Initialized GPU Devices: {}

[2026-04-20T18:06:25Z INFO coolercontrold::repositories::hwmon::devices] Could not read PCI ID database: pci.ids database not found at any known path, device name information will be limited

Would you mind posting a screenshot of your full Docker config for the container just to double check? Like this (this is mine, will be slightly different):

Are there still current issues with drivetemp?

On 7.2.6 but the potential instability warning gives me pause.

1 minute ago, kramttocs said:

Are there still current issues with drivetemp?

On 7.2.6 but the potential instability warning gives me pause.

As long as you're above whatever is in the docs you should be fine. I have never had an issue across four systems.

Appreciate it!