Start with a browser and service check
Open the Modrinth website in a normal browser and confirm whether the project or search page loads. This does not prove the launcher uses the same endpoint, but it helps distinguish a broad service issue from a launcher-specific request.
If the service is unavailable or returns an error for many users, wait for the official service to recover. Do not download a repacked mod or modpack from a random mirror simply because the launcher cannot reach Modrinth.
- Check the exact project slug or link.
- Confirm the system clock and HTTPS access.
- Look for a proxy, VPN, DNS filter or firewall rule.
- Read the first Modrinth/API error in the PineconeMC log.
Check PineconeMC's Modrinth connection
- Restart after a temporary failureClose PineconeMC, wait briefly and reopen it. If the same endpoint fails, preserve the log instead of repeating restarts.
- Review proxy and firewall settingsMake sure the launcher can reach the required HTTPS services. A browser may work through one proxy while the launcher uses another configuration.
- Check metadata cacheBack up the data directory, then clear only the relevant stale metadata cache if the log points to invalid or incomplete cached data.
- Try a simple projectTest a small, known-compatible mod or pack. A single project failure may be a version or dependency problem rather than a global Modrinth outage.
When a Modrinth modpack downloads but fails
A successful download does not guarantee a successful launch. Check the Minecraft version, loader, Java runtime, required dependencies and memory settings. Use the modpack guide to keep the imported pack separate from experiments.
If the project page lists a specific loader or release, select that exact version. Avoid mixing a Fabric pack with Forge mods or adding a newer dependency simply because it appears in search results.
| Symptom | Likely area |
|---|---|
| Search is empty | Network, API, service or cache |
| Project opens but install fails | Version, loader or dependency metadata |
| Pack installs but crashes | Java, memory, incompatible mod or configuration |
| Only one project fails | Project release or version mismatch |
Use a safe fallback
If you need a pack immediately, use the creator's official project page or a documented export rather than an executable “fixer”. Keep the original link and release information so you can verify what was installed.
If Modrinth works in a browser but not in the launcher after a clean data-directory test, report the reproducible endpoint and release details to the official project issue tracker. Remove private tokens and account information from the report.
Practical summary
A safe ElyPrismLauncher Modrinth not working workflow
ElyPrismLauncher Modrinth not working can mean several different things: the project list is empty, a search never finishes, a pack link cannot be resolved, a download stops or the imported instance fails later. Identify the stage first. A browser check, launcher log and small test project can separate a Modrinth service problem from a loader or modpack problem.
If ElyPrismLauncher Modrinth not working appears after a network change, compare the Modrinth project page in a browser with the same action inside PineconeMC. A browser result does not prove that every API request works, but it can show whether the service is broadly reachable. Record the API hostname, HTTP status, timeout or JSON error instead of guessing from the empty screen.
When ElyPrismLauncher Modrinth not working affects only one account, instance or data directory, check the selected profile, proxy settings and cached metadata. Close the launcher and back up the data directory before removing a narrowly identified cache. Do not delete worlds or an entire instances folder to repair a project search.
A pack can download successfully and still fail on launch because its Minecraft version, loader, Java runtime or dependencies are wrong. Read the pack manifest and compare the required version with the instance. Start the unmodified pack once, then add shaders, performance mods or custom files one at a time.
If the Modrinth service is available but the launcher continues to fail, try a clean data directory or a manual project download from the creator's official page as a comparison. Keep the original archive and manifest. A fallback is evidence for diagnosis, not a reason to trust an unknown mirror or executable installer.
For a useful report, include the exact project or pack URL, launcher release, operating system, instance version, loader, network state and first relevant log line. Remove account tokens, private paths and server credentials before sharing anything. This makes a recurring ElyPrismLauncher Modrinth not working issue easier for the project team to reproduce.
- Identify whether search, metadata, download or launch is the failing stage.
- Match the modpack manifest to the instance version and loader.
- Keep official project links and sanitized logs when reporting a failure.
Implementation notes
Confirm the failing Modrinth stage before rebuilding
A Modrinth issue should be classified as search, metadata, download, import or launch. Each stage uses different evidence. Search and metadata failures point toward service access or cache; an import failure points toward an archive or manifest; a launch failure points toward the Minecraft version, loader, Java or dependencies.
Use the same project URL and instance version when comparing PineconeMC with a browser or a manual official download. Keep the original archive and do not add extra mods while diagnosing. The goal is to know whether the project data is missing, the launcher cannot retrieve it or the game cannot use it.
When the service is reachable but the launcher remains empty, preserve the log and data-directory comparison for a report. Remove account details and local paths. A concise report with one project, one release and one first error is easier to reproduce than a complete private profile.
- Classify search, metadata, download, import or launch first.
- Keep one unchanged project and instance for comparison.
- Share sanitized logs rather than private account data.
Last checks
Close an ElyPrismLauncher Modrinth not working check
Once the project loads or the pack launches, keep the project URL, pack version and instance export. If ElyPrismLauncher Modrinth not working returns after an update, compare those records first instead of adding unrelated mods or deleting a working world.
- Keep one verified project and pack version.
- Export a working instance before updates.
- Compare the first failed stage after a change.
Common questions
Modrinth troubleshooting FAQ
Why does Modrinth work in my browser but not PineconeMC?
The launcher may use a different API endpoint, cache, proxy or certificate path. Identify the failing request in the launcher log.
Should I clear all launcher files?
No. Back up instances and clear only relevant cache data after the log points to a stale or corrupt cache.
Can I download a modpack from a random mirror?
Avoid unknown executable repacks and unverified mirrors. Use the creator's official project page or a documented export.
Why did my Modrinth pack install but not launch?
Check the Minecraft version, loader, Java runtime, dependencies, memory and any extra mods added after import.