Support - Brewtendo

Common symptoms

e.g. "Connection test failed", games or eShop pages won't load, or your 3DS reports error codes like 003-1101, 003-1201, or generic DNS/timeout messages.

Why this happens (technical)

These errors usually mean your 3DS cannot reach Brewtendo's servers because of incorrect proxy settings, ISP DNS blocking, captive portals (hotel/coffee shop networks), or Wi‑Fi stability issues.

What to do

• Verify your proxy IP and port on the SD card: open SD:\luma\sysmodules\ and ensure the .ips is installed (see Homebrew section if missing).
• On your 3DS: System Settings → Internet Settings → Connection Settings → Change Settings → Proxy Settings → Detailed Setup. Re-enter the Proxy Server and Port exactly.
• Switch to a phone hotspot to rule out ISP blocking, and if it works on a hotspot, your home ISP may block the server IP or port.
• Try a public DNS like 1.1.1.1 or 8.8.8.8 in your router (not the 3DS) to avoid DNS redirection issues.

Common symptoms

Error messages such as 005-5602, 007-2920, 007-2001, or seeing an empty storefront with missing categories.

Why this happens (technical)

These usually indicate authentication, certificate, or API-response errors. If Brewtendo's eShop emulation returns unexpected headers or if Luma isn't patching correctly, the eShop client may refuse to show content.

What to do

• Confirm your system time & date are correct. Certificates can fail if the clock is skewed.
• Make sure the proxy is set (see Connection section) and that the .ips patch is in SD:\luma\sysmodules\.
• If you see an authentication error, try deleting Internet Settings for the connection and re-creating it (leave DNS as automatic unless troubleshooting DNS).
• Try a different region in eShop settings: some content differences can cause partial failures. This is a diagnostic step only.

Common symptoms

Black screen on boot, "external modules not loaded", the .ips patch not applied, or Luma settings appearing to be ignored.

Why this happens (technical)

Luma needs to be configured to allow game patching and load external modules. If your Luma build is older, or the .ips patch is in the wrong folder, Brewtendo won't be able to intercept eShop requests.

What to do

• Follow 3ds.hacks.guide to confirm Homebrew and CFW are properly installed.
• Insert your SD card into PC and confirm the patch file exists at: SD:\luma\sysmodules\brewtendo.ips (filename may vary).
• Boot holding Select to open Luma config -> enable Enable game patching and Enable loading external firms and modules. Save and reboot.
• If you have a custom sysmodule path, double-check that Luma's "payload" and "sysmodules" locations are correct.

Common symptoms

Temporary server errors, timeouts, or messages advising "try again later". Error codes like 002-0102, 002-0120, or similar.

Why this happens (technical)

Brewtendo servers may be offline for maintenance or facing network issues. This is typically transient but can appear as many different client-side errors.

What to do

• Check Brewtendo status channels (Discord / GitHub) for maintenance notices.
• Try again after 10–15 minutes, many server issues can occur, as we are still in beta.
• If persistent, gather details (time, console region, error code) and file a GitHub issue so developers can inspect server logs.

Common symptoms

Connection works on some networks (e.g., phone hotspot) but not others; intermittent failures; inability to resolve Brewtendo domains.

Why this happens (technical)

ISPs sometimes block or hijack DNS for region-locking or IP-based filtering. Network-level redirection can cause the 3DS to reach the wrong server or return unexpected responses.

What to do

• Temporarily switch to a mobile hotspot or different Wi‑Fi network to confirm it's ISP-specific.
• Change your router's DNS servers to 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google), instructions vary by router model.
• If router changes are unavailable, use a phone hotspot as a workaround while you file an ISP complaint.

How to read codes

3DS error codes are often generic. Below are common codes you might see when using Brewtendo and what they typically mean.

• 003-1101 / 003-1201 Proxy/DNS or route problems. Re-check proxy settings and try alternate DNS or network.
• 005-5602 Authentication/certificate mismatch. Check system time & ensure proxy is active.
• 007-2920 / 007-2001 eShop content parsing errors. Try alternate region or re-install the IPS patch.
• 002-0102 / 002-0120 Server-side temporary failures. Check status and wait 10–30 minutes.
• Other network timeouts Could be Wi‑Fi signal, router firewall, NAT restrictions, or ISP blocking.

Symptoms

Random crashes, graphical glitches in the eShop, or error codes not listed above.

What to try

• Backup your SD card and perform a clean re-copy of the Brewtendo files from the repo.
• Make sure your SD card is not corrupted: run an integrity check on your PC (chkdsk on Windows, or Disk Utility on Mac).
• Test with a different SD card if you suspect hardware problems.
• Try disabling custom themes or plugins, because custom themes sometimes interfere with Luma patches.
• Keep your console battery charged during troubleshooting, because low-battery conditions can cause odd failures.

Get help from the community & devs

If you can't fix the problem with the steps above, reach out to us. Please include:

• Your 3DS model & system version
• Error code(s) and exact text shown
• Steps you've already tried
• A photo or short video if possible