[GH-ISSUE #1625] App version v4.2.0 and earlier update no longer works #905

Closed
opened 2026-05-05 06:51:05 -06:00 by gitea-mirror · 12 comments
Owner

Originally created by @jussikuosa on GitHub (Sep 27, 2024).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1625

Before opening the issue, have you...?

  • Searched for existing issues
  • Looked through the wiki
  • Updated MonitorControl to the latest version (if applicable)

Describe the bug

https://monitorcontrol.app/ gives

Error 1000 Ray ID: 8c99f6d8d8deca81 • 2024-09-27 08:01:10 UTC
DNS points to prohibited IP

What happened?

You've requested a page on a website (monitorcontrol.app) that is on the [Cloudflare](https://www.cloudflare.com/5xx-error-landing/) network. Unfortunately, it is resolving to an IP address that is creating a conflict within Cloudflare's system.
What can I do?

If you are the owner of this website:
you should [login to Cloudflare](https://www.cloudflare.com/login?utm_source=error_100x) and change the DNS A records for monitorcontrol.app to resolve to a different IP address.

Steps to reproduce

Try to browse to https://monitorcontrol.app/

Expected behavior

Able to see the site and download the latest release

Anything else?

This started from me noticing that the control app doesn't update both monitors anymore. I tried to upgrade the app but that fails (likely due to the DNS issue described).

See: External Keyboard Brightness Control Not Working on All Monitors #1531 for my root problem.

Environment Information (please complete the following information)

-
Originally created by @jussikuosa on GitHub (Sep 27, 2024). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1625 ### Before opening the issue, have you...? - [X] Searched for existing issues - [X] Looked through [the wiki](https://github.com/MonitorControl/MonitorControl/wiki) - [X] Updated MonitorControl to the latest version (if applicable) ### Describe the bug https://monitorcontrol.app/ gives ``` Error 1000 Ray ID: 8c99f6d8d8deca81 • 2024-09-27 08:01:10 UTC DNS points to prohibited IP What happened? You've requested a page on a website (monitorcontrol.app) that is on the [Cloudflare](https://www.cloudflare.com/5xx-error-landing/) network. Unfortunately, it is resolving to an IP address that is creating a conflict within Cloudflare's system. What can I do? If you are the owner of this website: you should [login to Cloudflare](https://www.cloudflare.com/login?utm_source=error_100x) and change the DNS A records for monitorcontrol.app to resolve to a different IP address. ``` ### Steps to reproduce Try to browse to https://monitorcontrol.app/ ### Expected behavior Able to see the site and download the latest release ### Anything else? This started from me noticing that the control app doesn't update both monitors anymore. I tried to upgrade the app but that fails (likely due to the DNS issue described). See: External Keyboard Brightness Control Not Working on All Monitors #1531 for my root problem. ### Environment Information (please complete the following information) ```markdown - ```
gitea-mirror 2026-05-05 06:51:05 -06:00
Author
Owner

@waydabber commented on GitHub (Sep 27, 2024):

The current version of MonitorControl app is no longer upgradable. Although the DNS issue will be fixed, future updates will not work from the v4.2.0 version (due to an issue with the required digital signatures).

<!-- gh-comment-id:2378778511 --> @waydabber commented on GitHub (Sep 27, 2024): The current version of MonitorControl app is no longer upgradable. Although the DNS issue will be fixed, future updates will not work from the v4.2.0 version (due to an issue with the required digital signatures).
Author
Owner

@CHKE9 commented on GitHub (Sep 29, 2024):

yeah no longer works, instantly crash when trying to adjust brightness on m1

<!-- gh-comment-id:2381543924 --> @CHKE9 commented on GitHub (Sep 29, 2024): yeah no longer works, instantly crash when trying to adjust brightness on m1
Author
Owner

@Hassan0x00A commented on GitHub (Sep 30, 2024):

The current version of MonitorControl app is no longer upgradable. Although the DNS issue will be fixed, future updates will not work from the v4.2.0 version (due to an issue with the required digital signatures).

Is the project still being actively maintained? Are there plans for future releases to address these issues or will the current version be the last? Any clarification would be helpful.

<!-- gh-comment-id:2382371275 --> @Hassan0x00A commented on GitHub (Sep 30, 2024): > The current version of MonitorControl app is no longer upgradable. Although the DNS issue will be fixed, future updates will not work from the v4.2.0 version (due to an issue with the required digital signatures). Is the project still being actively maintained? Are there plans for future releases to address these issues or will the current version be the last? Any clarification would be helpful.
Author
Owner

@waydabber commented on GitHub (Sep 30, 2024):

Take a look at the recent discussion here @Hassan0x00A - https://github.com/MonitorControl/MonitorControl/issues/1570

I plan to do something with the repo, possibly release a more official beta of 4.3.x. Updates from 4.2.0 will not work due to a signing issue. However currently only about 6-7k ppl downloaded the 4.3.1 version so I am not even sure how much demand there is for MonitorControl anymore (I think BetterDisplay is clearly a better alternative for most both in terms of functionality and support), so I have some doubts on whether I should work on a MonitorControl 5.0 or not.

<!-- gh-comment-id:2382396655 --> @waydabber commented on GitHub (Sep 30, 2024): Take a look at the recent discussion here @Hassan0x00A - https://github.com/MonitorControl/MonitorControl/issues/1570 I plan to do something with the repo, possibly release a more official beta of 4.3.x. Updates from 4.2.0 will not work due to a signing issue. However currently only about 6-7k ppl downloaded the 4.3.1 version so I am not even sure how much demand there is for MonitorControl anymore (I think BetterDisplay is clearly a better alternative for most both in terms of functionality and support), so I have some doubts on whether I should work on a MonitorControl 5.0 or not.
Author
Owner

@Hassan0x00A commented on GitHub (Sep 30, 2024):

I've tried BetterDisplay but I find it a bit overwhelming as there are a lot of options that I don't need. I was looking for something simple to control the brightness of my external monitors, and I think most people need the same.

<!-- gh-comment-id:2382406451 --> @Hassan0x00A commented on GitHub (Sep 30, 2024): I've tried BetterDisplay but I find it a bit overwhelming as there are a lot of options that I don't need. I was looking for something simple to control the brightness of my external monitors, and I think most people need the same.
Author
Owner

@waydabber commented on GitHub (Sep 30, 2024):

Right. I am not sure about most people based on download stats, but I get that there is a certain number of users who prefer MonitorControl, that's why I released an unofficial version that mostly works on Sequoia - feel free to use it! :) I certainly welcome other developers joining in to help ironing out any issues the version still has.

<!-- gh-comment-id:2382467159 --> @waydabber commented on GitHub (Sep 30, 2024): Right. I am not sure about most people based on download stats, but I get that there is a certain number of users who prefer MonitorControl, that's why I released an unofficial version that mostly works on Sequoia - feel free to use it! :) I certainly welcome other developers joining in to help ironing out any issues the version still has.
Author
Owner

@jcontini commented on GitHub (Sep 30, 2024):

Huge MonitorControl lover here! I use Brew to install (with the Raycast plugin). Came here because I noticed that it wasn't working on my external monitor after upgrading to Sequoia. Is the signing issue still an issue if we install through brew?

<!-- gh-comment-id:2382893183 --> @jcontini commented on GitHub (Sep 30, 2024): Huge MonitorControl lover here! I use Brew to install (with the Raycast plugin). Came here because I noticed that it wasn't working on my external monitor after upgrading to Sequoia. Is the signing issue still an issue if we install through brew?
Author
Owner

@waydabber commented on GitHub (Sep 30, 2024):

To some extent, yes. Accessibility permissions will likely break. But I think brew should be able to install the new version (when and if one is provided).

<!-- gh-comment-id:2382919718 --> @waydabber commented on GitHub (Sep 30, 2024): To some extent, yes. Accessibility permissions will likely break. But I think brew should be able to install the new version (when and if one is provided).
Author
Owner

@JamesTJRead commented on GitHub (Sep 30, 2024):

BetterDisplay is overkill - I just need to control an external monitor with my keyboard.. this utility nails that task, very keen on a new version that address the Sequoia issue.

Wouldn't be surprised about low download stats for a beta version, personally I only found this repo once the app stopped working, it was something I installed years ago and forgot about while it worked in the background.

<!-- gh-comment-id:2384302703 --> @JamesTJRead commented on GitHub (Sep 30, 2024): BetterDisplay is overkill - I just need to control an external monitor with my keyboard.. this utility nails that task, very keen on a new version that address the Sequoia issue. Wouldn't be surprised about low download stats for a beta version, personally I only found this repo once the app stopped working, it was something I installed years ago and forgot about while it worked in the background.
Author
Owner

@waydabber commented on GitHub (Oct 1, 2024):

Right. Indeed, an added benefit of an issue like this is that ppl don't take an app like this granted. Just use the unofficial version, it should mostly work. I'll try to devote some time to figure out why the custom shortcuts thing doesn't seem to work properly - if I can't find a solution, I'll just remove that feature and release the version as an official beta, noting its deficiencies.

(Note: BetterDisplay should work the same, you can even set the icon to be hidden, it's a lightweight app. No need to use all features obviously.)

<!-- gh-comment-id:2385335230 --> @waydabber commented on GitHub (Oct 1, 2024): Right. Indeed, an added benefit of an issue like this is that ppl don't take an app like this granted. Just use the unofficial version, it should mostly work. I'll try to devote some time to figure out why the custom shortcuts thing doesn't seem to work properly - if I can't find a solution, I'll just remove that feature and release the version as an official beta, noting its deficiencies. (Note: BetterDisplay should work the same, you can even set the icon to be hidden, it's a lightweight app. No need to use all features obviously.)
Author
Owner

@jcontini commented on GitHub (Oct 1, 2024):

Found a workaround!

  • Crashing happened when I had Screen to control set to Change for all screens.
  • I changed it to Depends on mouse pointer position and so long as my cursor is on my ext monitor, MC is working fine again.

If I set to both, or put my cursor on my macbook screen and try to adjust, then it crashes again. Seems that MC trying to adjust the macbook screen is what's causing the crash.

<!-- gh-comment-id:2385481120 --> @jcontini commented on GitHub (Oct 1, 2024): Found a workaround! - Crashing happened when I had `Screen to control` set to `Change for all screens`. - I changed it to `Depends on mouse pointer position` and so long as my cursor is on my ext monitor, MC is working fine again. If I set to both, or put my cursor on my macbook screen and try to adjust, then it crashes again. Seems that MC trying to adjust the macbook screen is what's causing the crash.
Author
Owner

@waydabber commented on GitHub (Oct 1, 2024):

Ok, fixed the DNS issue with the update. This will not make future updates work, but at least for now the user will not get an error message but will be reassured that the 4.2.0 is the latest version.

<!-- gh-comment-id:2386806591 --> @waydabber commented on GitHub (Oct 1, 2024): Ok, fixed the DNS issue with the update. This will not make future updates work, but at least for now the user will not get an error message but will be reassured that the 4.2.0 is the latest version.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/MonitorControl#905
No description provided.