Error 300002

[Aladwar]

It's not our networks or anything user-related, trust me-- it's 100% S-E. My connection is flawless outside of FFXIV. Games, streaming, everything works fine. FFXIV won't even work properly when I eliminate the router from the equation. I realize it's easy to dismiss this as "lol user error" when you think you've "fixed" it, but trust me, it's not user-related.

And I was without the error for about 3 days straight, then it came back. So even if you think you've fixed it, you may not have.

This was my experience this week as well. I was able to play all week long without connection issues of any kind, and the issue started returning (albeit more infrequently) this afternoon. I'm sure it will be resolved soon, and it has already gotten better.

[Kayos]

This has happened to me lie 20x already today...

[Aladwar]

30002 every 9 minutes like clockwork today. :/

[Burningthought]

It's not our networks or anything user-related, trust me-- it's 100% S-E. My connection is flawless outside of FFXIV. Games, streaming, everything works fine. FFXIV won't even work properly when I eliminate the router from the equation. I realize it's easy to dismiss this as "lol user error" when you think you've "fixed" it, but trust me, it's not user-related.

And I was without the error for about 3 days straight, then it came back. So even if you think you've fixed it, you may not have.

Nope it's fixed. It may not have anything to do with your router you might just have a spotty internet connection.

Try going on someone else's network, or a fast food chain with wifi and see if you still get the error. During the alpha/beta phases there was a lot of 30002s going around and i'm 100% sure it was the server congestion, but then people started getting chains of them for no apparent reason, but they could go onto a different network and play completely smoothly.

Not only all that crap, but the issue doesn't seem to be that widespread or else they'd issue a statement on it.

The only other time I got the error was during the alpha/beta periods on University internet (shitty) and even then I also had issues with the patcher, steam, and websites would occasionally not load at all.

[jPuff]

So even though this is literally the only program of like 20 I have connection issues with, it's my connection. Gotcha.

[Cooleko]

This is why tech support always starts with "did you turn on your computer?" then would follow up with "did you remember to disconnect the cat5 cable from the router and put it into your pc when bypassing the router?". If removing your router breaks the connection to the game that is what we call a PICNIC.

[izembo]

just because other things run fine doesnt mean ffxiv will run fine, it could still be the connection, just out of curiousity what isp do you have and is it a shared connection?

[Nexxus]

Problem is back today /o\ didnt saw it happend for a week.

3 times connections lost in less than 1h

[CrstyCptSteveWitherspoon]

It's SE's problem. I'm sure it's partially my isp with the 'spotty' connection, however when I get a 30002 error in game and I'm still able to surf the web and talk on teamspeak I know it's not just my fault. I hope they fix this crap. I can't afk over night to sell stuff, I'm disconnecting during synths and local leves, it's really taking away from the game. From my experience any kind of hiccup in your internet connection would always result in a dc from XI. I played warhammer with the same connection and over a 4-5 month period I think I dc'd maybe once. Twice tops. I had the occasional 'lag' for 20s and then everything caught up, but I never dc'd like this. I have a new isp now and don't have these random hiccups anymore at least to the point where I don't connection to other programs but I still have problems with SE clients. I think it's just shitty programming on their end. They're pretty notorious for that.

[sruon]

I'd say it's your ISP.

Probably a shitty internet backbone network or something.

[izembo]

has this issue been resolved or has everyone stopped playing?

[Drakath]

I personally didn't start getting this error until the last few days, but I've started to get it with such frequency I've stopped playing.