[{"data":1,"prerenderedAt":239},["ShallowReactive",2],{"blog:vpn-login-problems":3},{"zh-CN":4,"en":128},{"blocks":5,"faq":109},[6,9,11,13,17,19,21,24,26,43,45,47,50,52,54,65,68,70,72,80,82,85,87,95,98,100,102,105,107],{"type":7,"html":8},"p","登录卡在验证码这一步，十次里八次不是账号或密码的问题，是验证码没收到，或者收到得太晚、太乱。短信验证码和邮箱验证码失败的原因完全不同，混在一起排查只会越试越乱——先弄清楚自己收到的是哪一种，再往下查。",{"type":7,"html":10},"排查原则不变：\u003Cstrong>一次只改一个变量\u003C\u002Fstrong>。同时重发验证码、换手机号、又联系客服，账号解锁了也不知道是哪一步起的作用。",{"type":7,"html":12},"这几种原因里，前两种自己几分钟就能解决，后两种往往需要等待或者找客服核实身份。按下面的顺序查一遍，能很快知道自己属于哪一种，不用每一种都从头试一遍，也不用把所有可能性同时怀疑一圈。",{"type":14,"id":15,"html":16},"h2","bp-triage","先看清楚：这次用的是短信还是邮箱",{"type":7,"html":18},"打开输入验证码的那个页面，看清楚提示的是发到手机还是发到邮箱——这一步决定了后面该往哪个方向查。两者失败的原因几乎不重叠，认错方向会白白浪费时间。",{"type":7,"html":20},"有些账号注册时留的联系方式不止一种，登录页面弹出的提示文字通常会把发送目标遮掉一部分保护隐私，比如只显示手机号中间几位或者邮箱开头几个字符，对照一下能不能认出这是不是自己常用的那一个，认不出来就是下一节要讲的情况。",{"type":14,"id":22,"html":23},"bp-delay","最常见：验证码还在路上，只是比想的慢",{"type":7,"html":25},"多数所谓的「登录失败」，其实是验证码没到，人已经等不及点了重发，甚至重发了好几次。短信和邮箱的送达速度、常见的卡点完全不一样：",{"type":27,"align":28,"head":30,"rows":34},"table",[29,29,29],null,[31,32,33],"方式","常见延迟","最常见的失败原因",[35,39],[36,37,38],"短信验证码","通常几秒到一分钟内","运营商把验证类短信当成营销短信过滤，或者手机信号本身不稳定",[40,41,42],"邮箱验证码","几秒到几分钟不等，取决于邮件服务商","被邮箱自带的垃圾邮件规则拦下来，或者邮件服务商本身在排队处理",{"type":7,"html":44},"超过正常等待时间还没收到，才值得考虑下一步；没到时间就连续点重发，反而容易把自己绕进后面要讲的「用错验证码」那个坑里。",{"type":7,"html":46},"短信偶尔卡在运营商那一侧，跟信号格数没关系——格数满格也照样可能被过滤，因为过滤发生在运营商的服务器上，不是手机这一端。邮箱的延迟大多和验证码本身没关系，是那一封邮件在服务商的处理队列里排到了后面，尤其是使用量很大的免费邮箱，高峰期慢个几分钟很正常。",{"type":14,"id":48,"html":49},"bp-wrong-identifier","第二常见：验证码到了，但用错了识别方式",{"type":7,"html":51},"有些人注册的时候用的是某个不常用的邮箱，或者通过第三方账号登录时留下的是一个中转邮箱地址，这次登录却在往自己常用的那个邮箱或手机号上找验证码，自然找不到。这种中转地址平时根本不会主动去看，验证码安安静静躺在里面，人却在另一个收件箱里干等。",{"type":7,"html":53},"还有一种更容易忽略的变体：手机号前面的国家代码不对，或者当初注册用的是海外号码，这次却拿着一个国内号码去要验证码，系统对不上号自然发不出来，表现上跟「没收到」完全一样，原因却是账号识别层面的问题。",{"type":55,"items":56},"steps",[57,61],{"title":58,"body":59},"怎么确认",[60],"回想一下当初注册用的到底是哪一个邮箱或者手机号，尤其是有没有通过其他账号授权登录过——留下的联系方式可能不是自己以为的那一个。",{"title":62,"body":63},"怎么处理",[64],"换到当初注册时用的那个邮箱或手机号上找验证码；确实不记得的，联系\u003Ca href=\"\u002Fcontact\u002F\">客服\u003C\u002Fa>核实账号绑定的具体联系方式，比反复猜快得多。如果记得自己用过某个第三方账号登录过，先从那个第三方账号本身的设置里查一下当时授权用的是哪个邮箱，往往比直接联系客服更快。",{"type":14,"id":66,"html":67},"bp-expired","少见但容易踩：验证码过期或者被后来的重发覆盖",{"type":7,"html":69},"多数验证码有效期只有几分钟，而且重新发送一次，之前发出去的那条会自动失效——只有最新收到的那一条能用。如果手机或邮箱里同时躺着两三条验证码，很容易输错成前面已经失效的那一条，尤其是几条验证码位数相同、格式一样，肉眼很难一眼分清哪条是最新的。",{"type":7,"html":71},"这种情况在邮箱里更常见，因为邮件客户端经常按对话线索把几封验证邮件归在一起显示，翻开看到的第一条未必是时间最靠后的那一条。养成看时间戳的习惯，不要单凭排在最上面这一点来判断新旧。",{"type":55,"items":73},[74,77],{"title":58,"body":75},[76],"登录页提示验证码错误或已过期，同时收件箱里能翻到不止一条验证码，基本就是这个原因。",{"title":62,"body":78},[79],"找到时间戳最新的那一条，其余的直接忽略，不用删除也不用管。输入最新这一条还提示错误，才需要再重发一次，重发之后同样只用最新的那条。",{"type":81},"downloads",{"type":14,"id":83,"html":84},"bp-lockout","更少见：连续输错，账号被临时锁定",{"type":7,"html":86},"短时间内多次输错验证码或者密码，账号会被自动临时锁定一段时间，这是安全机制在保护账号，不是系统故障——如果不是本人在尝试登录，连续输错几次本身也是一个提醒信号，而不只是麻烦。锁定期间不管重发多少次验证码都没用，因为登录这一步本身被暂停了，跟验证码对不对已经没关系。",{"type":55,"items":88},[89,92],{"title":58,"body":90},[91],"页面明确提示账号被临时锁定或者需要稍后再试，而不是验证码错误，就是这种情况。",{"title":62,"body":93},[94],"按提示等锁定时间过去，或者联系客服提前核实身份解锁。账号安全机制的设计原理可以看\u003Ca href=\"\u002Fsecurity\u002F\">快橙怎么处理连接安全\u003C\u002Fa>。",{"type":14,"id":96,"html":97},"bp-limits","什么时候该联系客服，别自己反复试",{"type":7,"html":99},"有两种情况，自助操作基本解决不了。原来绑定的手机号已经停用，同时又忘了当初有没有留邮箱，两条找回渠道都断了，这时候继续重发验证码没有意义，得靠客服走身份核实流程重新绑定——这个过程需要提供能证明账号归属的信息，比如注册时间、用过的设备型号，提前想好能省一轮来回。",{"type":7,"html":101},"另一种是登录请求本身就没发出去——如果这张网络本身对某些流量做了额外限制，连接和登录都会一起受影响，这属于另一类问题，可以看\u003Ca href=\"\u002Fblog\u002Fvpn-blocked-by-network\u002F\">公司或校园网把 VPN 拦了怎么办\u003C\u002Fa>。区分这两种情况的办法很简单：登录页面能不能打开、点击发送验证码有没有报错。页面打不开或者点了发送没反应，是网络层面的问题；页面正常、发送也提示成功了，只是验证码没到，才是这篇从头讲到这里的情况。分清楚是哪一种，能省掉很多来回试的时间。",{"type":14,"id":103,"html":104},"bp-final","总结",{"type":7,"html":106},"登录失败先看验证码走的是短信还是邮箱，多数情况只是没到或者用错了、用旧了；少数情况是账号被临时锁定或者绑定的联系方式已经失效，这两种自助操作解决不了，直接找客服比反复重发快。记住只用最新一条验证码这一点，能省掉一大半反复重试的时间。",{"type":7,"html":108},"装应用、登录账号这条链上的另一个常见卡点是安装本身被系统拦下来，表现和登录失败很像，但原因完全不搭边，\u003Ca href=\"\u002Fblog\u002Fvpn-app-wont-install\u002F\">App 装不上、提示未受信任怎么办\u003C\u002Fa>专门讲了这部分。登录顺利之后，\u003Ca href=\"\u002Ffeatures\u002F\">功能介绍\u003C\u002Fa>里有账号能覆盖的具体范围，注册后每天有免费试用时长可以先用起来。",[110,113,116,119,122,125],{"q":111,"a":112},"验证码要等多久才算正常？","短信通常几秒到一分钟内送达，邮箱偶尔会因为邮件服务商排队等上几分钟。超过五分钟都没收到，才值得考虑重发或者换一种方式。",{"q":114,"a":115},"连续点了好几次重发，该用哪一条验证码？","只有最新收到的那一条有效，之前发出去的全部自动失效。混着试只会越试越乱，找到最后一条重新输入就好。",{"q":117,"a":118},"收不到短信，是运营商的问题还是应用的问题？","多数情况下是运营商那边把这类验证短信当成营销短信过滤了，不是应用没发出去。换成邮箱验证一次，能很快排除是不是这个原因。",{"q":120,"a":121},"换了手机号，还能登录原来的账号吗？","取决于账号当初绑定的是手机号还是邮箱。绑定的是收不到的旧手机号，需要先通过邮箱或者联系客服换绑，不是重新注册就能解决的。",{"q":123,"a":124},"验证码提示错误，但明明是刚抄下来的？","大概率是重发过后这一条已经不是最新的了，或者已经过了有效期。重新发一次，只用最新收到的那条码再试。",{"q":126,"a":127},"一直登录失败会不会把账号锁住？","短时间内连续输错太多次，账号会被临时锁定一段时间保护安全，等锁定过去再试，或者联系\u003Ca href=\"\u002Fcontact\u002F\">客服\u003C\u002Fa>提前解锁。",{"blocks":129,"faq":220},[130,132,134,136,138,140,142,144,146,161,163,165,167,169,171,181,183,185,187,195,196,198,200,208,210,212,214,216,218],{"type":7,"html":131},"Getting stuck at the verification code step is, eight times out of ten, not actually about a wrong password — it's a code that never arrived, or arrived too late and too tangled with earlier ones. SMS codes and email codes fail for completely different reasons, and troubleshooting them as if they were the same thing only adds confusion. Work out which one you're dealing with first, then keep going from there.",{"type":7,"html":133},"The same rule as always: \u003Cstrong>change one variable at a time\u003C\u002Fstrong>. Resend the code, switch phone numbers and contact support all in the same breath, and even once the account unlocks you won't know which step actually did it.",{"type":7,"html":135},"Of these causes, the first two are usually fixed in a few minutes on your own; the last two typically need waiting it out or a support agent verifying your identity. Working through them in order tells you which one applies quickly, without testing every possibility at once or trying every fix in one go.",{"type":14,"id":15,"html":137},"First, check: is this SMS or email?",{"type":7,"html":139},"Open the screen asking for the code and read carefully whether it says it went to a phone or an email — this one detail decides which direction to look in next. The causes barely overlap between the two, and guessing wrong wastes time for nothing.",{"type":7,"html":141},"Some accounts have more than one contact method on file, and the login screen usually masks part of the destination for privacy — showing only the middle digits of a phone number, or the first few characters of an email. Check whether you recognise it as the one you normally use; if you don't, that's exactly the next section.",{"type":14,"id":22,"html":143},"Most common: the code is on its way, just slower than expected",{"type":7,"html":145},"Most so-called "login failures" are really just a code that hasn't arrived yet, with someone too impatient to wait hitting resend, sometimes more than once. SMS and email differ a lot in how fast they typically land and where they typically get stuck:",{"type":27,"align":147,"head":148,"rows":152},[29,29,29],[149,150,151],"Method","Typical delay","Most common failure cause",[153,157],[154,155,156],"SMS code","Usually seconds to under a minute","Carrier filters this kind of text the way it filters marketing messages, or the signal itself is unstable",[158,159,160],"Email code","Seconds to a few minutes, depending on the provider","Caught by the mailbox's own spam rules, or simply queued at the mail provider's end",{"type":7,"html":162},"Past the normal wait with nothing arriving is when the next step is worth considering. Hitting resend before that window is up is exactly what walks you into the "used the wrong code" trap covered further down.",{"type":7,"html":164},"An SMS occasionally gets stuck on the carrier's side for reasons that have nothing to do with signal bars — full bars and all, it can still get filtered, because the filtering happens on the carrier's own servers, not on the phone. Email delays usually have nothing to do with the code itself; that particular message is simply sitting further back in the provider's processing queue, and a free mailbox under heavy load running a few minutes behind during peak times is completely normal.",{"type":14,"id":48,"html":166},"Next most common: the code arrived, just not where you were looking",{"type":7,"html":168},"Some people register with a rarely used email, or sign in through a third-party account that leaves behind a relay address rather than their usual one — and then go looking for the code in their everyday inbox or phone number, where it was never going to show up. That relay address is one nobody actively checks; the code sits there quietly while the person waits on an entirely different inbox.",{"type":7,"html":170},"There's a less obvious variant too: the wrong country code on a phone number, or an account originally registered with an overseas number now being asked to receive a code on a domestic one. The system simply can't match the two, so nothing gets sent — which looks exactly like "never arrived" but is really an identity-matching problem underneath.",{"type":55,"items":172},[173,177],{"title":174,"body":175},"How to confirm it",[176],"Think back to exactly which email or phone number was used at registration, especially whether sign-in ever happened through another account's authorization — the contact method on file may not be the one you'd assume.",{"title":178,"body":179},"How to fix it",[180],"Check the email or phone number actually used at registration for the code. If you genuinely can't recall it, \u003Ca href=\"\u002Fen\u002Fcontact\u002F\">contact support\u003C\u002Fa> to confirm what's on file — that's faster than guessing repeatedly. If you remember signing in through a third-party account, checking that account's own settings for which email it authorized often beats going straight to support.",{"type":14,"id":66,"html":182},"Rarer, easy to fall into: the code expired or got overtaken by a later resend",{"type":7,"html":184},"Most codes are valid for only a few minutes, and sending a new one automatically kills the previous one — only the most recent is usable. With two or three codes sitting in a phone or inbox at once, it's easy to type in one that already expired, especially when they're the same length and format and impossible to tell apart at a glance.",{"type":7,"html":186},"This shows up more in email, since mail clients often group several verification messages into one thread, and the one on top when you open it is not necessarily the most recent by time sent. Get in the habit of checking the timestamp rather than assuming the one on top is the newest.",{"type":55,"items":188},[189,192],{"title":174,"body":190},[191],"The login page says the code is wrong or expired, and there's more than one code sitting in the inbox — that's usually this exact cause.",{"title":178,"body":193},[194],"Find the one with the latest timestamp and ignore the rest; no need to delete them. Only resend again if that latest one still comes back as wrong, and after resending, again use only the newest one.",{"type":81},{"type":14,"id":83,"html":197},"Rarer still: too many wrong attempts locked the account",{"type":7,"html":199},"Enough wrong codes or passwords in a short window triggers an automatic temporary lock — that's the security mechanism doing its job, not a system fault. If it wasn't you attempting to log in, several failed attempts in a row is itself worth noticing, not just an inconvenience. Nothing about resending more codes helps during a lock, because the login step itself has been paused, independent of whether the code is right.",{"type":55,"items":201},[202,205],{"title":174,"body":203},[204],"The page explicitly says the account is temporarily locked or to try again later, rather than saying the code is wrong — that's this case.",{"title":178,"body":206},[207],"Either wait out the lock as instructed, or contact support to verify your identity and unlock it sooner. The reasoning behind the account security mechanism is covered on \u003Ca href=\"\u002Fen\u002Fsecurity\u002F\">how FastOrange handles connection security\u003C\u002Fa>.",{"type":14,"id":96,"html":209},"When to contact support instead of trying again",{"type":7,"html":211},"There are two situations self-service generally can't resolve. If the phone number on file is no longer active and there's no memory of an email ever being added, both recovery paths are cut off — resending more codes at that point accomplishes nothing, and only a support agent walking through identity verification can reattach the account. That process asks for information proving the account is yours, like roughly when it was registered or which device it was used on — having that ready in advance saves a round trip.",{"type":7,"html":213},"The other situation is when the login request itself never went out at all — if the network you're on adds its own restrictions to certain traffic, both the connection and the login attempt suffer together, which is a different category of problem covered in \u003Ca href=\"\u002Fen\u002Fblog\u002Fvpn-blocked-by-network\u002F\">office or campus network blocking your VPN\u003C\u002Fa>. Telling the two apart is simple: does the login page even open, and does clicking send throw an error? A page that won't open or a send button with no response points at the network. A page that works fine, with send reporting success, and still no code showing up — that's everything covered here. Knowing which one you're dealing with saves a lot of back-and-forth.",{"type":14,"id":103,"html":215},"In summary",{"type":7,"html":217},"For a failed login, check whether the code is SMS or email first — most of the time it simply hasn't arrived yet, or the wrong one, or an old one, got used. The rarer cases are a temporarily locked account or a contact method that's no longer reachable, and self-service can't fix either of those — going straight to support beats resending again. Remembering to use only the most recent code alone saves most of the repeated attempts.",{"type":7,"html":219},"Another common snag on the way to logging in is the install itself getting blocked by the system, which looks similar to a login failure but has nothing to do with it — \u003Ca href=\"\u002Fen\u002Fblog\u002Fvpn-app-wont-install\u002F\">what to do when an app won't install or shows as untrusted\u003C\u002Fa> covers that part specifically. Once logged in, the \u003Ca href=\"\u002Fen\u002Ffeatures\u002F\">features page\u003C\u002Fa> lays out exactly what an account covers, and every registered account gets free trial time daily to start with.",[221,224,227,230,233,236],{"q":222,"a":223},"How long is a normal wait for a verification code?","SMS usually lands within a few seconds to a minute; email occasionally takes a few minutes if it's queued at the provider's end. Past five minutes with nothing showing up is when resending or switching methods is worth considering.",{"q":225,"a":226},"I hit resend several times. Which code should I actually use?","Only the most recently received one is valid — every earlier one is automatically dead. Mixing them up only adds confusion; find the last one and enter that.",{"q":228,"a":229},"Is a missing SMS code the carrier's fault or the app's?","Most of the time the carrier is filtering that kind of message the same way it filters marketing texts — the app did send it. Testing email instead rules this out quickly.",{"q":231,"a":232},"I got a new phone number. Can I still log into my old account?","Depends on whether the account is tied to that phone number or to an email. If it's tied to a number you can no longer receive texts on, you'll need to switch it through email or support first — re-registering will not fix it.",{"q":234,"a":235},"The code says it's wrong, but I just copied it down.","It's most likely no longer the latest one after a resend, or it has expired. Send a new one and use only the code you just received, nothing from before it.",{"q":237,"a":238},"Can too many failed logins lock the account?","Yes — too many wrong attempts in a short window triggers a temporary lock as a safety measure. Either wait it out, or \u003Ca href=\"\u002Fen\u002Fcontact\u002F\">contact support\u003C\u002Fa> to verify your identity and unlock it sooner.",1793276291384]