[{"data":1,"prerenderedAt":282},["ShallowReactive",2],{"blog:how-to-use-midjourney-in-china":3},{"zh-CN":4,"en":151},{"blocks":5,"faq":132},[6,9,11,13,17,19,21,23,25,28,30,50,52,55,57,59,61,64,72,75,98,100,103,112,115,117,119,121,123,125,128,130],{"type":7,"html":8},"p","Midjourney 目前主要通过 Discord 使用——先要有 Discord，再在里面用指令找机器人生图。这意味着实际上有两段连接：一段是 Discord 本身能不能正常收发消息，另一段是生成的图片能不能顺利传回频道。指令发出去了却一直不出图，多数时候卡在第二段，和 Discord 文字聊天正不正常是两件事。",{"type":7,"html":10},"少数账号现在能直接在 Midjourney 官网生成图片，但目前多数人还是走 Discord 这条路，这篇主要按这条路来讲。",{"type":7,"html":12},"下面先说清楚这两段连接分别负责什么，再给一套排查步骤，最后是常见报错和让出图更稳的习惯。",{"type":14,"id":15,"html":16},"h2","bp-why","为什么指令发出去了却一直不出图",{"type":7,"html":18},"第一种最直接：Discord 本身打不开，登录不上或者消息发不出去，这是网络没到，换一条能稳定连接海外网络的线路能解决，这一层和用不用 Midjourney 没关系。",{"type":7,"html":20},"第二种是指令能发出去，Discord 显示机器人正常回应，但生成结果一直不出现，或者缩略图裂开、加载到一半。这一段是生成的图片单独从远端传回频道，和发指令用的文字连接不是同一条路，一条通不代表另一条也通。",{"type":7,"html":22},"第三种是排队和生成速度本身。Midjourney 按服务器负载和账号的订阅档分配生成资源，高峰期排队变长、生成变慢，这是服务本身的调度，不是网络工具能改变的一层。",{"type":7,"html":24},"三种原因表现都可能被说成「用不了」或者「卡住了」，但对应的动作完全不同：第一种该换网络，第二种换个节点重新打开频道多半就好，第三种只能等，或者错开高峰，纠结网速对第三种没有帮助。",{"type":14,"id":26,"html":27},"bp-discord","Discord 连接和出图这一段：两件不同的事",{"type":7,"html":29},"把这两段拆开看，才知道卡住的时候该换节点还是该等一等。",{"type":31,"align":32,"head":34,"rows":39},"table",[33,33,33,33],null,[35,36,37,38],"环节","负责什么","卡住时的表现","换节点有没有用",[40,45],[41,42,43,44],"Discord 本身","登录、发指令、看到文字回复","打不开、发不出指令、一直转圈","有用，换一个稳定节点基本能解决",[46,47,48,49],"Midjourney 出图","排队生成、把图片传回频道","指令发出去了，但图一直不出来或者缩略图裂开","部分有用（图片传输这一段），排队和生成速度由 Midjourney 自己决定",{"type":7,"html":51},"分清楚卡在哪一段，能省掉很多没用的尝试——文字都能发，却对着排队转圈换十个节点，基本不会有效果。反过来，如果连指令都发不出去，先别怀疑是不是排队排太久，回去检查 Discord 本身的连接状态才对。",{"type":14,"id":53,"html":54},"bp-longsession","挂着 Discord 很久，为什么偏偏是图片传不过来",{"type":7,"html":56},"Discord 客户端和服务器之间会一直保持一条连接，文字消息和机器人的状态更新都走这条连接。图片不一样：机器人回复里只是给了一个地址，客户端要另外单独去图片服务器拉一次，走的是完全不同的第二条路。平时这两条路都通，感觉不出区别。",{"type":7,"html":58},"挂机时间一长，第一条连接偶尔会自己断开重连，Discord 客户端处理得很隐蔽，重连之后文字照样收发正常，你几乎看不出发生过什么。图片走的是另一条路，如果重连之后到图片服务器这一段刚好不通，看到的就是「指令回复正常，图一直不出来」——两件事表面上绑在一起，其实是两条连接分别出的问题。",{"type":7,"html":60},"排队机制在长时间使用时也会放大这一点。账号的生成额度用完之后，后面的任务会自动排进更慢的队列。挂着窗口没注意到额度已经用完，看到的就是「之前很快，这张怎么这么久」，不是哪里坏了，是这一张排到了慢队列里。",{"type":14,"id":62,"html":63},"bp-checklist","机器人已经回复，图却迟迟不出现时，按这个顺序看",{"type":65,"items":66,"ordered":71},"list",[67,68,69,70],"\u003Cstrong>看机器人这条消息本身有没有进度\u003C\u002Fstrong>：正在生成的任务通常带一个百分比或者转动的图标，两者都没有，多半还在排队，没轮到，不是传输的问题。","\u003Cstrong>看同一个频道里别人的图能不能加载\u003C\u002Fstrong>：能，问题在你到图片服务器这一段；大家的图都刷不出来，多半是那一侧暂时出了状况，等一等比反复重试有用。","\u003Cstrong>换一个节点，把频道整个关掉重新打开\u003C\u002Fstrong>：比在原页面反复刷新更管用，缩略图经常在重新打开的时候就补全了。","\u003Cstrong>确认本地存储没有占满\u003C\u002Fstrong>：Discord 客户端会在本地缓存图片，存储空间紧张的设备偶尔会悄悄在这一步失败，表现和网络问题几乎一样。",true,{"type":14,"id":73,"html":74},"bp-steps","使用和排查步骤",{"type":76,"items":77},"steps",[78,82,86,90,94],{"title":79,"body":80},"第一步：连接并固定一个节点",[81],"打开\u003Ca href=\"\u002Ffeatures\u002F\">快橙\u003C\u002Fa>并连接，中途不要切换。整个测试过程保持同一个节点，方便判断问题出在哪一段。",{"title":83,"body":84},"第二步：下载并登录 Discord，加入机器人所在的服务器",[85],"下载安装 Discord，登录账号，加入 Midjourney 官方服务器，或者已经请了机器人的自己的服务器——两种都能用指令生图，选哪个不影响后面的排查步骤。",{"title":87,"body":88},"第三步：先测文字，确认 Discord 本身没问题",[89],"在任意文字频道发一条消息，看看发得出去、机器人的其他回复能不能正常显示。这一步顺利，说明 Discord 本身和基础网络都没问题。",{"title":91,"body":92},"第四步：发一条生图指令，单独测出图这一段",[93],"用生图指令生成一张图，等待结果。指令发出去、机器人确认收到，但迟迟不出图或者图片裂开，问题就缩小到出图传输这一段。",{"title":95,"body":96},"第五步：出图卡住时换一个节点重新打开频道",[97],"多数缩略图裂开或者加载不完整，换节点刷新一次就能看到完整图片，不需要重新发指令排队。",{"type":99},"downloads",{"type":14,"id":101,"html":102},"bp-errors","常见报错和情况",{"type":65,"items":104},[105,106,107,108,109,110,111],"\u003Cstrong>Discord 本身打不开或者一直转圈\u003C\u002Fstrong>：网络没到，换一条能稳定连接海外网络的线路。","\u003Cstrong>文字发得出去，指令却没反应\u003C\u002Fstrong>：先确认机器人在线、指令格式没打错，这一步和网络关系不大。","\u003Cstrong>指令确认收到，但图一直不出来\u003C\u002Fstrong>：出图传输这一段单独卡住，换节点重新打开频道试试。","\u003Cstrong>缩略图裂开或者只加载一半\u003C\u002Fstrong>：图片没传完整，刷新或者换节点通常能看到完整版本。","\u003Cstrong>排队时间比平时长很多\u003C\u002Fstrong>：高峰期服务器负载高，这是 Midjourney 自己的调度，换网络工具不会让队排得更快。","\u003Cstrong>同一个服务器，别人出图正常，只有自己一直卡\u003C\u002Fstrong>：大概率是自己这边到图片传输那一段的线路问题，和服务器、和别人的网络没关系。","\u003Cstrong>换手机和电脑测试，结果不一样\u003C\u002Fstrong>：两边用的网络环境不一定相同，先确认两台设备是不是都连着稳定的线路，再比较结果。",{"type":14,"id":113,"html":114},"bp-stable","让出图更稳的几个习惯",{"type":7,"html":116},"固定一个常用节点，别在生图过程中来回切换。指令和出图各走各的连接，频繁切换反而容易让两边都不稳定。",{"type":7,"html":118},"先测文字再测出图。这一点和\u003Ca href=\"\u002Fblog\u002Fhow-to-use-discord-in-china\u002F\">Discord 在国内怎么用\u003C\u002Fa>里「文字正常不代表语音也正常」是同一个判断思路——这里换成了「文字正常不代表出图也正常」，逻辑完全一样。",{"type":7,"html":120},"避开明显的高峰时段。同样的指令，排队时间可能差好几倍，这不是网络的问题，错开高峰能省不少等待时间。",{"type":7,"html":122},"生成结果出来之后尽快保存。频道里的历史消息多了之后，早期的图片有时候要往上翻很久才能找到，看到满意的结果先存到本地，比事后再去翻省事。",{"type":7,"html":124},"诚实地说：网络工具能做的是让 Discord 连得上、图片传得完整；排队快慢和生成速度，是 Midjourney 自己的服务器和订阅档决定的，这一点和\u003Ca href=\"\u002Fblog\u002Fhow-to-use-claude-ai-in-china\u002F\">Claude 在国内怎么用\u003C\u002Fa>里「账号层面的限制网络解决不了」是同一个道理。",{"type":14,"id":126,"html":127},"bp-final","总结",{"type":7,"html":129},"Midjourney 在国内不好用，很多时候不是完全连不上，而是 Discord 本身和出图这一段被当成了同一个问题——实际上它们走的不是同一条路。指令都发得出去，说明网络基础没问题，出图慢或者卡住，先看清楚是哪一段再决定要不要换节点。",{"type":7,"html":131},"网络这一段可以做得很省心：固定节点、Discord 和出图分开判断、卡住就换一个。\u003Ca href=\"\u002Forder\u002F\">快橙\u003C\u002Fa>每天提供免费试用时长，注册后即可领取——先发一条生图指令测一下，等结果完整出来，再决定要不要长期用。",[133,136,139,142,145,148],{"q":134,"a":135},"Midjourney 在国内怎么用，需要先装什么？","先装好\u003Ca href=\"\u002Ffeatures\u002F\">快橙\u003C\u002Fa>并连接，再下载安装 Discord，加入 Midjourney 的服务器或者自己请了机器人的服务器，才能开始用指令生图。",{"q":137,"a":138},"指令发出去了，但图片一直不出来，是哪里的问题？","Discord 本身能正常收发文字，说明基础连接是通的；图迟迟不出来，多数是生成结果传回频道这一段单独卡住，和文字指令能不能发是两件事。",{"q":140,"a":141},"换节点能让出图变快吗？","传输这一段换节点可能有帮助；排队时间和生成速度本身，是 Midjourney 根据服务器负载和账号订阅档决定的，网络工具改变不了这部分。",{"q":143,"a":144},"是不是一定要用 Discord，能不能直接上官网？","部分账号可以在 Midjourney 官网直接生成，但目前多数人还是通过 Discord 用指令生图，这篇主要讲 Discord 这条路。",{"q":146,"a":147},"图片缩略图裂开或者加载一半，怎么办？","这是图片从生成结果传回来的时候没传完整，换一个节点重新打开频道，通常能看到完整图片。",{"q":149,"a":150},"快橙能保证出图速度吗？","快橙负责让 Discord 和图片传输这两段连接都尽量稳定；排队和生成速度由 Midjourney 自己的服务器和订阅档决定，不是网络工具能改变的。详见\u003Ca href=\"\u002Ffeatures\u002F\">功能介绍\u003C\u002Fa>。",{"blocks":152,"faq":263},[153,155,157,159,161,163,165,167,169,171,173,191,193,195,197,199,201,203,209,211,233,234,236,245,247,249,251,253,255,257,259,261],{"type":7,"html":154},"Midjourney today mainly runs through Discord — you need Discord first, then you ask the bot inside it to render with a command. That means there are really two connections here: whether Discord itself sends and receives normally, and whether the rendered image makes it back to the channel in one piece. A command that goes through with nothing ever appearing is almost always the second one, unrelated to whether text chat in Discord works fine.",{"type":7,"html":156},"A handful of accounts can now render directly on Midjourney's own site, but most people are still on the Discord path, which is what this guide focuses on.",{"type":7,"html":158},"The rest of this covers what each of those two connections is responsible for, then a way to check which one is at fault, then the errors people actually hit and a few habits that keep rendering more reliable.",{"type":14,"id":15,"html":160},"Why a command goes through with no image ever appearing",{"type":7,"html":162},"The first case is the most direct: Discord itself won't open, won't log in, or won't send messages. That's the network not arriving, and switching to a route that reliably reaches overseas networks usually fixes it — unrelated to Midjourney specifically.",{"type":7,"html":164},"The second case is a command that sends fine, with the bot acknowledging it normally, but the result never shows up, or the thumbnail looks broken or half-loaded. That's the rendered image being delivered back from the remote server on its own, a different path from the text connection the command travelled on.",{"type":7,"html":166},"The third case is the queue and render speed itself. Midjourney allocates rendering capacity based on server load and the account's subscription tier — longer queues and slower renders at peak times are the service's own scheduling, not a layer any network tool changes.",{"type":7,"html":168},"All three get described as "it's not working" or "it's stuck," but the response differs: switch networks for the first, switch nodes and reopen the channel for the second, and just wait — or avoid peak hours — for the third. Worrying about connection speed doesn't help with the third one at all.",{"type":14,"id":26,"html":170},"Discord itself and rendering are two different things",{"type":7,"html":172},"Splitting these two legs apart is what tells you whether to switch nodes or just wait it out.",{"type":31,"align":174,"head":175,"rows":180},[33,33,33,33],[176,177,178,179],"Leg","Responsible for","What it looks like when stuck","Does switching nodes help",[181,186],[182,183,184,185],"Discord itself","Login, sending commands, seeing text replies","Won't open, commands don't send, spins forever","Yes — a stable node usually fixes it",[187,188,189,190],"Midjourney rendering","Queueing, generating, delivering the image to the channel","Command went through but no image, or a broken thumbnail","Partly — helps the transfer leg; queue and render speed are Midjourney's own call",{"type":7,"html":192},"Knowing which leg is stuck saves a lot of wasted effort — switching through ten nodes while staring at a queue that's simply slow accomplishes basically nothing. The reverse is true too: if commands aren't even sending, don't assume it's a long queue — go back and check Discord's own connection first.",{"type":14,"id":53,"html":194},"Why a long Discord session breaks specifically at image delivery",{"type":7,"html":196},"Discord keeps one connection open the whole time you're signed in, and that connection carries text messages and the bot's status updates. Images are different: the bot's reply just contains a link, and the client fetches the actual file from Discord's own image servers as a separate request on a different path entirely. Most of the time both are working, so you never notice they're separate.",{"type":7,"html":198},"The longer a session runs, the more likely that first connection quietly drops and reconnects on its own. Discord handles this smoothly enough that text keeps flowing and you never notice it happened. The image fetch travels a different path, though, so if the route to the image servers is briefly down right after that reconnect, what you see is "the bot replied fine, the image just won't show up" — two things that look tied together but are really two connections in two different states.",{"type":7,"html":200},"Queueing compounds this over a long session too. Once an account's faster generation allowance runs out, whatever is still in flight quietly drops into a slower queue. Leave the window open without noticing the allowance ran out, and the result looks like "this used to come through fast, why is this one taking forever," when nothing actually broke.",{"type":14,"id":62,"html":202},"When the bot has replied but the image still won't show, check in this order",{"type":65,"items":204,"ordered":71},[205,206,207,208],"\u003Cstrong>Look for progress on the bot's own message.\u003C\u002Fstrong> A job that's actively rendering usually shows a percentage or a spinning icon. Neither one means it's probably still queued and hasn't started, not a delivery problem.","\u003Cstrong>Check whether other people's images in the same channel load.\u003C\u002Fstrong> If they do, the route between you and the image servers is the issue; if nobody's images are loading, that side is likely having a moment, and waiting beats retrying.","\u003Cstrong>Switch nodes and close the channel completely before reopening it.\u003C\u002Fstrong> This works better than refreshing the same view repeatedly — reopening often fills in a thumbnail that was stuck.","\u003Cstrong>Confirm local storage isn't full.\u003C\u002Fstrong> Discord caches images on the device, and a device short on space can fail quietly at exactly this step, looking exactly like a network problem.",{"type":14,"id":73,"html":210},"Using it and checking what's wrong",{"type":76,"items":212},[213,217,221,225,229],{"title":214,"body":215},"Step one: connect and stay on one node",[216],"Open \u003Ca href=\"\u002Fen\u002Ffeatures\u002F\">FastOrange\u003C\u002Fa> and connect without switching mid-test. Staying on one node throughout makes it possible to tell which leg is actually at fault.",{"title":218,"body":219},"Step two: install Discord and join a server with the bot",[220],"Download and log into Discord, then join Midjourney's official server or your own server with the bot already invited — either works for generating with commands, and it doesn't affect the steps that follow.",{"title":222,"body":223},"Step three: test text first to confirm Discord itself is fine",[224],"Send a message in any text channel and check that it goes through and that other bot replies display normally. If that works, Discord and the base connection are both fine.",{"title":226,"body":227},"Step four: send a render command to test the delivery leg on its own",[228],"Generate an image with a command and wait for the result. If the command sends and the bot acknowledges it, but the image never appears or shows up broken, the problem is narrowed down to the delivery leg.",{"title":230,"body":231},"Step five: switch nodes and reopen the channel when a render is stuck",[232],"Most broken or incomplete thumbnails clear up after switching nodes and refreshing the channel — no need to resend the command and queue again from scratch.",{"type":99},{"type":14,"id":101,"html":235},"Errors people actually hit",{"type":65,"items":237},[238,239,240,241,242,243,244],"\u003Cstrong>Discord itself won't open or spins forever.\u003C\u002Fstrong> The network isn't arriving — switch to a route that reliably reaches overseas networks.","\u003Cstrong>Text sends fine, but a command gets no response.\u003C\u002Fstrong> Check that the bot is online and the command syntax is correct first — this one has little to do with the network.","\u003Cstrong>The bot acknowledges the command, but no image ever shows up.\u003C\u002Fstrong> The delivery leg is stuck on its own — switch nodes and reopen the channel.","\u003Cstrong>A thumbnail looks broken or only half-loaded.\u003C\u002Fstrong> The image didn't finish transferring — refreshing or switching nodes usually gets the complete version.","\u003Cstrong>The queue is taking much longer than usual.\u003C\u002Fstrong> Server load is high at peak times — that's Midjourney's own scheduling, and no network tool speeds up the line.","\u003Cstrong>On the same server, everyone else renders fine and only you get stuck.\u003C\u002Fstrong> Most likely the route between you and the image-delivery leg specifically, unrelated to the server or anyone else's connection.","\u003Cstrong>Testing on a phone versus a computer gives different results.\u003C\u002Fstrong> The two may not be on the same network conditions — confirm both are on a stable route before comparing results.",{"type":14,"id":113,"html":246},"Habits that keep rendering more reliable",{"type":7,"html":248},"Stay on one familiar node and avoid switching back and forth mid-render. Commands and rendered results travel separate connections, and switching often risks destabilizing both.",{"type":7,"html":250},"Test text before testing a render. That's the same logic as \u003Ca href=\"\u002Fen\u002Fblog\u002Fhow-to-use-discord-in-china\u002F\">"text is fine doesn't mean voice is fine" in using Discord in mainland China\u003C\u002Fa> — here it's "text is fine doesn't mean rendering is fine," and the reasoning is identical.",{"type":7,"html":252},"Avoid the obvious peak hours. The same command's queue time can differ by several times depending on when it's sent, which has nothing to do with the network — timing around peak hours saves real waiting.",{"type":7,"html":254},"Save results you like soon after they appear. Once a channel's history grows, scrolling back to find an early image gets tedious — saving it locally right away beats digging for it later.",{"type":7,"html":256},"To be honest about it: what a network tool can do is get Discord connected and images transferred completely. How fast the queue moves and how fast rendering runs are Midjourney's own servers and subscription tiers at work — the same point covered for account-level limits in \u003Ca href=\"\u002Fen\u002Fblog\u002Fhow-to-use-claude-ai-in-china\u002F\">using Claude in mainland China\u003C\u002Fa>: a network tool doesn't lift a restriction that lives at the account or service level.",{"type":14,"id":126,"html":258},"In summary",{"type":7,"html":260},"Midjourney struggling in mainland China is often not a total connection failure — it's Discord itself and the rendering leg getting treated as one problem when they actually travel separate paths. If commands are sending fine, the network foundation is solid; a slow or stuck render is about figuring out which leg it is before deciding whether to switch nodes.",{"type":7,"html":262},"The network side of this can be made genuinely simple: stay on one node, judge Discord and rendering separately, and switch when something's stuck. \u003Ca href=\"\u002Fen\u002Forder\u002F\">FastOrange\u003C\u002Fa> gives every registered account free trial time every day — send one render command, wait for the full result, then decide whether to keep it.",[264,267,270,273,276,279],{"q":265,"a":266},"What do I need installed to use Midjourney in mainland China?","Install \u003Ca href=\"\u002Fen\u002Ffeatures\u002F\">FastOrange\u003C\u002Fa> and connect first, then download Discord and join Midjourney's server or a server that already has the bot invited — that's what lets you generate images with commands.",{"q":268,"a":269},"A command goes through but no image ever appears. What's wrong?","If Discord sends and receives text normally, the base connection is fine. An image that never appears is usually the delivery leg carrying the result back to the channel stalling on its own, separate from whether the text command went through.",{"q":271,"a":272},"Does switching nodes make rendering faster?","It can help the delivery leg specifically. The queue time and render speed themselves are set by Midjourney based on server load and the account's subscription tier — no network tool changes that part.",{"q":274,"a":275},"Do I have to use Discord? Can I use the website directly?","Some accounts can generate directly on Midjourney's own site, but most people still generate through Discord with commands, which is what this guide mainly covers.",{"q":277,"a":278},"A thumbnail looks broken or only half-loaded. What now?","That's the image not finishing its transfer back from the render. Switch to a different node and reopen the channel, and it usually shows up complete.",{"q":280,"a":281},"Can FastOrange guarantee render speed?","FastOrange keeps both the Discord connection and the image transfer as stable as it can. Queue time and render speed are set by Midjourney's own servers and subscription tiers — not something a network tool changes. See \u003Ca href=\"\u002Fen\u002Ffeatures\u002F\">what the app does\u003C\u002Fa>.",1793276292243]