1. Why Midjourney Web Is a Multi-Hostname Workload
Midjourney in the browser is closer to a rich creative app than to a brochure site. You pull down a large single-page bundle, issue prompts, and wait while the service queues image generation work, streams previews, and fetches tiles, thumbnails, and upscaled assets. Many of those bytes do not come from the literal host you typed in the address bar. They often arrive via separate CDN hostnames—sometimes global edges you have seen on other products, sometimes vendor-specific patterns—which means “I added midjourney.com to my rules” is rarely sufficient for stable access.
The pain shows up when one leg of that chain is split across policies. Example: the HTML document and the main API ride your PROXY-MIDJOURNEY tag, but an asset host matches an early domestic DIRECT exception, or a broad GEOIP shortcut sends a websocket to a different egress than the session cookie expects. The UI does not always surface a crisp error—you get a persistent loading indicator, a blank grid, or an Imagine action that never completes even though the tab “looks” online. That is not mysterious AI behavior; it is inconsistent Clash split rules and node selection.
The mental model matches our other creative-AI pieces. Suno couples long jobs with media fetches; Sora couples orchestration with chunky downloads. Midjourney sits in the image column with similarly long-lived sessions. Treat it as a small, versioned set of measured suffixes—not a single keyword—and keep that block above catch-all rules. For listener ports, mixed stacks, and resolver vocabulary, start from our configuration documentation so YAML mistakes do not swamp real routing bugs.
2. Symptoms: Spinners, Half-Painted UI, or Stuck Imagine Jobs
Most reports fall into four buckets. First, the chrome of the app renders, but panels never fill with data—classic “shell loads, dynamic content does not,” which often means XHR or WebSocket connections to a hostname your profile never tagged. Second, interaction sort-of works until you start a heavy job; then progress stalls while DevTools shows hung requests to a CDN name that your log marks as DIRECT. Third, intermittent success when you toggle Wi-Fi versus cellular: that is a device-level policy mismatch or a captive portal path, not proof that “the node is worn out.” Fourth, everything fails with a clean HTTP 403 or account gate—that may be vendor policy or subscription state; do not spend an hour on split rules if the status code already says “no.”
TLS-only failures deserve parallel reading. If handshake errors cluster on one host while midjourney.com itself is fine, see Clash "TLS Handshake Timeout" in logs before you churn through exit pools, because SNI quirks and middleboxes can mimic a bad subscription on a single edge.
Fetch/XHR, WS, JS, and Img. Copy every distinct hostname you see while reproducing a stuck job. Compare that set line-by-line to your Clash connection log. If any hostname you care about hits DIRECT during the repro while siblings use your creative-proxy group, you have found the split.
3. midjourney.com, Subdomains, and CDN Names in Logs
Your authoritative list is what the browser actually requested this week, not a blog comment from last year. In many builds you will still see midjourney.com and various subdomains on the same registrable domain—APIs, static hosts, auth helpers—but vendors ship front-end refreshes often, and experiments can introduce new first-party suffixes. Start with DOMAIN-SUFFIX,midjourney.com only after you confirm it covers the eTLD+1 of the hosts in your trace; if the product calls a different base domain for a subset of traffic, that suffix needs its own explicit row.
CDN is a role, not one magical string. Edges may present as *.cloudfront.net, *.fastly.net, or other shared patterns. Blind DOMAIN-KEYWORD,cloud rules are a blunt instrument: they may miss the hostname you need or drag unrelated domestic traffic through a distant node. The disciplined pattern is: log the exact names during a failing session, promote the smallest suffix that covers them, and consider a tiny rule-providers file if your household maintains Git-backed profiles.
Some sessions still touch discord.com flows when Discord-backed identity or ancillary services appear in the network log. We do not promise a universal “also add Discord” line—verify initiator context—but if Clash shows login or OAuth traffic on Discord hostnames in the same user journey, either extend your creative group to those suffixes (with eyes open to side effects) or add a narrow companion rule you measured, similar to how we isolate product families in the Discord guide for desktop voice—different mechanism, same “do not guess” discipline.
| Kind | What to do in Clash | Pitfall |
|---|---|---|
midjourney.com (measured subdomains) |
DOMAIN-SUFFIX,midjourney.com,<your PROXY-MIDJOURNEY group> above broad GEOIP / MATCH |
A naked DOMAIN-KEYWORD,mid collides with unrelated brands; validate suffixes |
| Logged CDN / edge names | Add DOMAIN-SUFFIX only for hosts you observed; comment placeholders until measured |
Generic “proxy all Fastly” rules can break regional sites and game patches |
| Ancillary auth (if your trace shows it) | Optional extra suffix lines, still ordered above catch-alls, same policy group if appropriate | Over-wide Discord or Google catches can starve domestic latency-sensitive apps |
Capture, don’t guess
After each repro, export hostnames to a note beside your YAML. When the vendor ships a new bundle, diff that list the way you would diff code. That workflow keeps image generation reliable without turning your profile into an unmaintainable keyword dump.
4. Rule Order: First Match Wins—Nothing Steals the Chain
Clash evaluates rules top-down. A well-meaning GEOIP,US or domestic shortcut placed above your creative block can swallow the exact connections your UI needs, which makes DOMAIN-SUFFIX,midjourney.com at line 900 irrelevant theater. The opposite failure also happens: an early DIRECT row intended for a shopping mall captures a shared CDN IP range that also serves your creative tiles, so half the grid loads and half does not.
Practical ordering for this workload: measured product suffixes and their logged CDN companions; other SaaS you explicitly maintain; regional exceptions you have tested; GEOIP or equivalent; MATCH. The label names are less important than the invariant—every hostname on the critical path for a single session should hit the same policy bucket during that session.
If you also run a corporate VPN, browser PAC injection, or another tunnel, reconcile OS routing first. Compare the browser Network tab with the Clash hit log; when they disagree on a host, YAML edits will not converge until the OS picks a single steering path.
402/403 patterns as product responses, not as missing lines in your profile.
5. Example YAML: PROXY-MIDJOURNEY Group and Rules
The snippets below are structural examples. Rename proxies to match your subscription, validate against your core (Mihomo-class forks sometimes extend grammar), and never paste opaque YAML from strangers—profiles are executable configuration. The point is to show how a dedicated group and ordered rules interlock for Midjourney-class traffic.
Pair modest url-test tolerance with a sane interval so the group is not thrashing on micro-loss bursts while a long render runs. For tuning detail, read Clash url-test interval and tolerance.
proxy-groups:
- name: PROXY-MIDJOURNEY
type: url-test
proxies:
- us-west-stable-a
- us-west-stable-b
- jp-low-churn-browse
url: https://www.gstatic.com/generate_204
interval: 300
tolerance: 50List suffixes above your catch-alls and insert only commented placeholders for CDN edges until you replace them with measured names.
rules:
- DOMAIN-SUFFIX,midjourney.com,PROXY-MIDJOURNEY
# - DOMAIN-SUFFIX,your-cdn-host.invalid,PROXY-MIDJOURNEY # from Network log
- GEOIP,CN,DIRECT
- MATCH,FINAL-PROXYTeams can move the creative rows into a rule-providers bundle reviewed on a schedule—same hygiene we recommend for large media apps—so operator time scales with real hostname drift, not fear.
6. DNS, fake-ip, and TUN Alignment
DNS is half of any split rules story. If the tunnel resolver and the browser’s effective resolver disagree, you can fetch two different answers for the same CDN label, which shows up as flaky TLS, random reconnects, or a UI that never leaves loading. Fake-ip modes intentionally make terminal dig output diverge from what the browser sees; that is fine when you understand which lens you are using.
On TUN desktops, confirm the browser actually rides the stack you think—especially on Windows and macOS when Private Relay, another VPN, or split-tunnel corporateware is present. For Apple GUI clients, Clash Verge on macOS: system proxy and Network Extension covers the common foot-guns. If the adapter is not in play, even perfect YAML is theater.
If symptoms persist after alignment, Clash fake-ip filter and DNS explains resolver filters that masquerade as dead nodes. Creative apps with long sessions are sensitive to that failure mode.
7. Node Selection for Long Image Generation
A five-second probe does not prove a peer can hold multiplexed HTTPS and occasional WebSocket traffic for a multi-minute creative job. Nodes that look “fastest” sometimes reset under load, which surfaces as a stuck Imagine step rather than a clean error. Prefer slightly slower, low-churn exits with stable loss profiles; pair that with url-test tolerance that does not flip groups on every millisecond ranking change.
Geography still matters: some regions simply offer better round-trip stability to the orchestration endpoints your trace shows, while others add jitter that hurts tile striping. Use logs, not vibes—watch which outbound owns the hostnames you care about across an entire job. If your provider labels pools, a browsing-oriented pool is usually a safer default than ultra-UDP gaming routes unless packet capture shows QUIC reliance in your build.
Isolate the workload
Avoid throwing Midjourney into a catch-all bag that also carries bulk downloads and voice UDP unless you enjoy chasing Heisenbugs. A dedicated PROXY-MIDJOURNEY tag makes regressions readable: when only creative tabs degrade, you inspect suffix coverage and that group’s nodes, not unrelated traffic.
8. Self-Check Checklist
- Rule hits: During a full job, every
midjourneyand captured CDN hostname should hit your creative tag—not a strayDIRECThop mid-session. - Resolver parity: Reconcile tunnel DNS with what the browser uses; revisit fake-ip filters if only some connections fail.
- HTTP semantics: Auth and payment responses are product logic, not missing YAML.
- Stability over leaderboard ping: Steady RTT beats a jittery “best” node for long renders.
- Re-test on upgrades: Front-end deploys and Clash core updates both change observables—rerun your hostname capture.
Check a known-good tuple—suffix list, group name, DNS mode, representative node—into your personal runbook so the next regression is a diff, not a séance.
10. Terms and Scope
Changing the proxy path does not grant service rights where the publisher withholds them, bypass billing, or replace a legitimate account. Use Midjourney in line with its terms and applicable law. This article documents Clash configuration observability—split rules, node selection, DNS/TUN alignment—not circumventing abuse, fraud, or copyright controls.
We do not assist with evading verification, paywalls, or enforcement systems. If the product prompts for login or payment in its official UI, complete those steps there. Our routing guidance assumes endpoints are already permissible on your network when reached with a correctly configured client.
11. Summary
Midjourney on the web is a chained workload: first-party midjourney.com traffic plus CDN-hosted assets and long-lived sessions, all of which need a coherent Clash story. You win when your profile is explicit—measured DOMAIN-SUFFIX rows ordered above catch-alls, bound to a purpose-built proxy group whose node selection survives real creative jobs, backed by resolver and TUN settings that agree with what the browser does. That is the same discipline we use for Suno, Sora, and Character.AI, applied to the image generation column.
Opaque one-tap VPNs hide the evidence you need. Clash shows which rule matched, which node terminated TLS, and whether resolvers disagree. When you install or refresh the client, use our download page so packages match the documentation you rely on—not a random mirror.