Fix
Where to get help
OCLP has no paid support. Help comes from the project's community, which is active and knowledgeable if you ask well.
On this page 4 sections
Short answer
The main place is the official OpenCore Patcher Paradise Discord, linked from the project's README. Also active: the r/OpenCoreLegacyPatcher subreddit and the MacRumors “on Unsupported Macs” threads for each macOS version. The GitHub issue tracker is used for announcements and confirmed bugs, not support.
Where
- Discord (official)
- OpenCore Patcher Paradise, maintained by the community. Its support forum has an “Information and known issues” post (Dortania).
- r/OpenCoreLegacyPatcher.
- MacRumors forums
- Long threads per macOS version, for example “macOS Tahoe 26 on Unsupported Macs Discussion”.
- GitHub
- Issues for announcements and real bugs.
How to ask so you get an answer
- Your Mac's model identifier (
sysctl hw.model) and any upgraded parts. - macOS version and build, OCLP version.
- What you did, what you expected, what happened, with exact error text or a photo.
- The OCLP log from
~/Library/Logs/Dortania/; for boot problems a photo of the verbose screen (turn on Verbose in Settings and rebuild OpenCore). - What you already tried from the troubleshooting page.
Collect the logs people will ask for
Dortania's debugging guide names three switches in OCLP's Settings: Enable Verbose Mode, Enable OpenCore DEBUG and Enable Kext DEBUG. Turn them on, rebuild OpenCore, install it to the drive and reproduce the problem. Then:
- OpenCore log. With OpenCore DEBUG on, every boot writes a text file to the EFI partition. Mount that partition (Dortania suggests the MountEFI tool) and copy it out.
- Kernel log. With Kext DEBUG on, run
sudo dmesg > ~/Desktop/DMESG.txtafter the problem happens. - The OCLP log in
~/Library/Logs/Dortania/for errors inside the app itself.
When you file a GitHub issue, Dortania asks for the Mac model you are patching, the target macOS, the macOS you are running now, your OpenCore build folder, and the logs above. Search first: a duplicate is closed without help.
What the issue tracker looks like in practice
The tracker is public, so we counted. Every number below comes from reports whose issue form names a specific Mac model; open them to see for yourself.
508 issues in OCLP's tracker name one Mac model in the form's “Machine Model” field (or in the title) for one of the 121 model identifiers we checked, searched on 5 November 2026.
| Year | Reports | Closed |
|---|---|---|
| 2020 | 9 | 100% |
| 2021 | 398 | 100% |
| 2022 | 97 | 99% |
| 2024 | 2 | 100% |
| 2025 | 2 | 100% |
| Topic | Non-Metal graphics (2008–2011) | Metal graphics (2012 and newer) |
|---|---|---|
| Graphics | 29% | 24% |
| Wi-Fi | 6% | 4% |
| Boot failure or black screen | 18% | 17% |
| Sleep and power | 12% | 13% |
| Audio | 4% | 2% |
| Bluetooth | 5% | 3% |
Two things follow. First, the tracker is mostly an archive: the large wave of reports dates from 2021 and 2022, when the project was new. In March 2022 the lead developer announced he would step back from development, and Dortania's docs still carry a notice that issues were put on hold; reports filed in 2024 and 2025 show the tracker accepts issues again. Second, the topics people report are the same ones the troubleshooting page covers, so search there before you post.
Stay safe
Nobody legitimate needs your Apple ID password, remote access to your Mac, or payment to help. Dortania says the project does not contact users by email.Keep going
Something wrong or out of date on this page? Email hello@oclp.dev and we will fix it (see our corrections policy).