FFXIV Error 10105 | Fix Login Lockouts Fast

FFXIV Error 10105 tends to show up after a rough disconnect. The client crashes, your console sleeps mid-zone, your router hiccups, or the launcher hangs. You reopen the game, pick your character, and then you’re stopped at the door.

Most of the time, this is not a “broken account” moment. It’s a session mismatch. The lobby still thinks your character is logged in, even if you’re staring at a login screen.

This article walks you through a clean order of fixes. Start with the quickest wins, then move to the deeper network checks if the error keeps coming back.

FFXIV Error 10105 In Plain Terms

When you log into Final Fantasy XIV, your character session is tracked across a few steps: launcher, lobby, data center handshake, then world login. If something cuts out mid-step, your session can linger for a bit on the server side.

That lingering session is what makes ffxiv error 10105 feel stubborn. You can have a solid internet connection and still get blocked because the last session has not fully dropped yet.

You’ll notice one of these patterns:

• Only one character fails — One character is “stuck,” while alts can log in.
• It follows a disconnect — You were booted, then the next login attempt triggers the error.
• It pairs with other codes — You may also see 2002 or 90002 around the same time, tied to unstable routing or brief packet loss.

Check Server Status And Maintenance First

Before you change settings, make sure the game servers are behaving. If your world or data center is having issues, no local tweak will stick.

Do this check in under a minute:

1. Open The World Status Page — Use the official status page to confirm your world and data center are online: na.finalfantasyxiv.com/lodestone/worldstatus/.
2. Read Any Notices — If a login issue or emergency maintenance is listed, stop trying to log in for a while. Repeated attempts can add frustration without changing the outcome.
3. Try A Different World Visit Later — If you were planning a world visit, wait until the status page looks calm again, then retry.

If everything is green and stable, move on. The fixes below are aimed at clearing the stuck session and reducing the chance of it happening again.

Fast Steps That Clear A Stuck Session

Start here. These steps are safe, quick, and often enough to knock the session loose.

1. Wait Ten Minutes — Close the game fully and give it time. A short wait often lets the old session time out.
2. Power Cycle Your Network — Unplug your modem and router, wait a full 60 seconds, then plug them back in and let them settle.
3. Restart The Device — Reboot your PC or console, not just the game. A full restart clears stuck network states.
4. Log Into Another Character — If you can, log into an alt for a minute, then log out cleanly and retry the stuck character.
5. Switch To A Wired Connection — If you’re on Wi-Fi, plug in Ethernet for the test. Even one brief Wi-Fi drop can cause the lingering-session problem.

If you’re back in, take one extra minute to log out cleanly once. Exit to the title screen, then close the client. That clean exit helps the next login behave normally.

Fixing Ffxiv Error 10105 On PC And Steam

If you’re on Windows (standalone or Steam), the goal is twofold: stop the disconnect that triggers the stuck session, and remove local blocks that break the handshake.

Launcher And Client Checks

1. Run The Launcher As Admin — Right-click the launcher and choose Run as administrator, then try logging in again.
2. Verify Game Files — On Steam, use Verify integrity of game files. On the standalone client, use the built-in file check if available.
3. Close Overlay Tools — Turn off overlays for the test (Steam overlay, Discord overlay, capture tools). Keep the setup simple while you troubleshoot.

Clean Network Resets On Windows

If the error repeats often, reset the Windows network stack. This can fix odd DNS or socket states after a crash.

1. Open Command Prompt — Search “cmd,” then run it as administrator.
2. Flush DNS — Run ipconfig /flushdns, then press Enter.
3. Reset Winsock — Run netsh winsock reset, then press Enter.
4. Restart The PC — Reboot fully, then test the login again.

Quick Table Of Symptoms

Use this quick map to choose your next move without guessing.

What You See	What It Often Means	What To Try Next
Error after a crash	Old session still active	Wait, then reboot router
Only one character fails	Character session stuck	Log an alt briefly, then retry
Frequent 90002 too	Connection drops mid-play	Switch to Ethernet, test routing
Steam only issues	Local file or overlay conflict	Verify files, disable overlays

Console Fixes For PS5, PS4, And Xbox

On consoles, you have fewer toggles, which is nice. The tradeoff is that sleep mode and quick-resume behavior can leave the game in a weird state after a network dip.

Console Reset Steps

1. Fully Quit The Game — Don’t leave it suspended. Close the app from the home menu.
2. Restart The Console — Use Restart, not Rest Mode. Then launch the game fresh.
3. Forget And Rejoin Wi-Fi — If you can’t run Ethernet, remove the Wi-Fi network and add it again.
4. Test A Different Network — A phone hotspot for a one-minute login test can tell you if the home network is the culprit.

Settings That Reduce Repeat Disconnects

1. Turn Off Rest Mode Downloads — Background downloads can spike latency during play.
2. Pause Large Updates — Patch downloads on the same network can cause packet loss.
3. Use Ethernet If Possible — A stable cable link cuts out a big chunk of “random” drops.

If you’re seeing ffxiv error 10105 mainly after coming back from rest mode, treat that as your signal. Close the game before rest, then relaunch when you’re ready to play.

Router, Firewall, And Port Settings

If you keep getting the error after clean restarts, look at the connection path between you and the data center. The goal is steady traffic, not raw speed.

Firewall Allow List On PC

1. Allow The Game Executables — Add the FFXIV launcher and game exe files to your firewall allow list.
2. Temporarily Disable Third-Party Antivirus — For one test run, turn it off, log in, then turn it back on.
3. Avoid Double Firewalls — Router security plus a strict PC firewall can block traffic twice.

Ports Used By The Game

If your router is strict, you may need to allow the ports the game uses. Square Enix lists these on the official system requirements page: na.finalfantasyxiv.com/system_requirements/.

The page lists TCP ports that may be used, including 80, 443, 54992–54994, 55006–55007, and 55021–55040. If you set port rules, use the exact ranges shown there and follow your router brand’s steps.

Routing Tests That Tell The Truth

Sometimes the issue is not your home setup, but the route your ISP takes to the data center. You can test this without installing anything.

1. Run A Ping Test — Ping a stable site for two minutes. If you see drops, fix the home link first.
2. Try A VPN As A Test — A VPN can change your route. If the error vanishes on VPN, the weak point is likely routing, not your device.
3. Swap DNS Providers — Try a public DNS on your router or device, then reboot and retest.

Use the VPN step as a diagnostic. If it helps, you’ve learned something useful about routing. If it doesn’t, you can remove it and keep troubleshooting locally.

When To Contact Square Enix And What To Include

If you’ve tried the fast steps, tested wired, and the error keeps hitting the same character for hours, it’s time to bring in Square Enix. This is also the right move if the issue started after a crash and never cleared across a full day.

When you reach out, send clean details so you don’t get stuck in back-and-forth messages.

1. Write Down The Exact Error — Include the full code and where it appears in the login flow.
2. List Your Platform — PC (Steam or standalone), PS5, PS4, or Xbox, plus your data center and world.
3. Note What Changed — New router, ISP change, patch day, console sleep behavior, or a recent crash.
4. Share What You Tried — Waiting, router reboot, wired test, DNS swap, file verify, and firewall allow list.
5. Add Timing — Include the date and local time window when it happens most often.

If the error clears after a long wait, keep your setup steady for a day or two. Avoid sleep-mode logins, stick to Ethernet if you can, and log out cleanly once per session. That simple routine reduces the odds of getting trapped behind the same login lockout again.