Unable to connect to Duty Finder server. Please try again later.

[eaglenitewillow]

Been having the same problem myself as well. can't seem to get an answer from anyone anywhere. Still waiting for a reply from square enix about the matter too.

getting kinda ridiculous that no one from there has even bothered to put a reply in here to say they know and are working on it

[LivKoten]

I'm having it as well on Hyperion. Started today, can't really doing anything end game now.

[PandaPause]

Posted this in 2 other threads but signing this one as well.

[letovash]

I forgot to put my info.

character: Leto Vash
Server: Gilgamesh

[Sleigh]

Tried queueing for a NM Titan, 3/4 accepted, one withdrew (not intentionally), then it said reserving instance for a few minutes until I cancelled it. After all that, I can not start a queue, it errors me out immediately.

Sleigh Presty
Diabolos server.

Edit: Relogging fixed it for me and the party.

[Bumbee]

I have this problem too. Server Moogle.
reboot pc, box, relog are not fixed it.
I can't do any instance since today.

[letovash]

I bet everyone in japan is asleep. Does anyone know when they wake up and fix things?

[docbon]

Having the same issue with my character on Ultros. Had to call off the coil group we were planning on doing tonight since I couldn't get in, no matter what I did.

[Kirei]

Having the same issue.

Character: Kirei Koneko
Server: Hyperion

[Artoid]

Character: Art Mew
Server: Sargatanas

Pretty much the same error as everyone else is describing. Tried to enter the binding coil of Bahamut after last nights maintenance, but kept getting the message "Unable to connect to Duty Finder server. Please try again later.".

Also tried Queuing for other activities through the duty finder register (The Howling Eye, The Navel, Amdapor Keep etc.), but the same error occurs. Attempts to fix this included -

- /logout
- /shutdown
- /shutdown + computer restart
- /shutdown + computer restart + internet reset
- Area change + /shutdown
- Retiring to an Inn room + /shutdown

The error is also still persisting after a 10-hour no-play period.

Bug report was submitted in-game after all attempts failed.