Shadowrocket HTTPS decryption: a narrow debug tool, not a streaming switch

Keep Shadowrocket HTTPS decryption off unless you are on a test device writing rules and you understand the certificate you just installed. Banks, work phones, and family devices: off. It is not how catalogs unlock.

MITM lets the client see names inside TLS so you can write matchers. The cost is a trusted cert on the device. A neglected cert is a seat for someone else.

Narrow yes, wide no

• Yes: your own test unit, reproducing a matcher.
• No: banking, MDM, streaming “unlock” attempts.

Turn it off when you are done and delete leftover certs. Go back to the global check in rules. Install via the download page. FAQ, guides, import.

Field questions tied to this guide

• Required for streaming? No. Fix rules and DNS. Decryption is for visibility, not libraries.
• Certificate warnings everywhere? Turn MITM off and remove the profile/cert you installed.
• Work phone? No. Installing a root cert on MDM hardware is a policy problem you do not want.
• Rules remain after MITM off? Yes. Matchers still see names that were never inside TLS.

Change one control, then retest

While working through “Shadowrocket HTTPS decryption: a narrow debug tool, not a streaming switch”, write the download-page version, mode, protocol, and node name on the first line of a note. After each toggle, run one check only: 1.1.1.1/help or the exact page that failed. Changing Kill Switch, split rules, and nodes together makes the next failure un-debuggable. Get Shadowrocket packages only from the download page; permissions and device limits live in the FAQ and guides.

On office or hotel networks, finish captive portals and clear leftover PAC entries before you decide this article’s failure mode applies. A cellular A/B exposes router DNS and parental filters quickly. Avoid hammering login on a second device during the test so session kickouts are not mistaken for radio drops.

Pin the combination that works—SSID, node, protocol—and reuse it on that network instead of starting from Auto every time. Keeping slug rocket-mitm-https-decrypt as your note title makes the write-up searchable later.

When to stop and change layers

After five identical failures, stop. Recheck the documented build, confirm a single tunnel client, ensure Kill Switch was not blocking a portal, and verify the browser is not Direct in a split list. Stopping is how you escape the wrong layer.

When you ask for help, include time, SSID, mode, protocol, node names, and steps already tried. After recovery, verify egress in a clean browser so cache does not fake success, then write the split list or favorites back into your notes before the next reinstall.

Extra pass for “Shadowrocket HTTPS decryption: a narrow debug tool, not a streaming switch”: retest three minutes on a second network and confirm the download page build. If only one app fails, inspect split membership; if everything fails, inspect permissions and DNS first. One change at a time remains the fastest habit when debugging Shadowrocket.

Extra pass for “Shadowrocket HTTPS decryption: a narrow debug tool, not a streaming switch”: retest three minutes on a second network and confirm the download page build. If only one app fails, inspect split membership; if everything fails, inspect permissions and DNS first. One change at a time remains the fastest habit when debugging Shadowrocket.

Extra pass for “Shadowrocket HTTPS decryption: a narrow debug tool, not a streaming switch”: retest three minutes on a second network and confirm the download page build. If only one app fails, inspect split membership; if everything fails, inspect permissions and DNS first. One change at a time remains the fastest habit when debugging Shadowrocket.

Extra pass for “Shadowrocket HTTPS decryption: a narrow debug tool, not a streaming switch”: retest three minutes on a second network and confirm the download page build. If only one app fails, inspect split membership; if everything fails, inspect permissions and DNS first. One change at a time remains the fastest habit when debugging Shadowrocket.

Extra pass for “Shadowrocket HTTPS decryption: a narrow debug tool, not a streaming switch”: retest three minutes on a second network and confirm the download page build. If only one app fails, inspect split membership; if everything fails, inspect permissions and DNS first. One change at a time remains the fastest habit when debugging Shadowrocket.

Extra pass for “Shadowrocket HTTPS decryption: a narrow debug tool, not a streaming switch”: retest three minutes on a second network and confirm the download page build. If only one app fails, inspect split membership; if everything fails, inspect permissions and DNS first. One change at a time remains the fastest habit when debugging Shadowrocket.