You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Probably] Cloudflare Connectivity Issues
Getting:
"XIVLauncher failed to check for updates"
"Updating Dalamud/Core/DalamudAssets"
longer than usual launch times with a tiny XIVLauncher popup
You probably are having a connectivity issue to:
Kamori (our proxy server that hosts version checks and assets)
Cloudflare (which is front of Kamori to protect it from being hit too hard)
You probably are affected by the current DDOS to SE's servers, but this can also be caused by generally connectivity or routing issues to them as well. (Blame your ISP)
There isn't anything we can do to help you with these issues as they're outside of our control. You may have a better experience by changing your internet connection (try a mobile hotspot, use a different wifi/ethernet connection), or by using a VPN. (See early posts in this channel)
The text was updated successfully, but these errors were encountered:
[Probably] Cloudflare Connectivity Issues
Getting:
"XIVLauncher failed to check for updates"
"Updating Dalamud/Core/DalamudAssets"
longer than usual launch times with a tiny XIVLauncher popup
You probably are having a connectivity issue to:
Kamori (our proxy server that hosts version checks and assets)
Cloudflare (which is front of Kamori to protect it from being hit too hard)
Getting:
"Cannot check ffxivboot version"
"Cannot obtain gate status"
other login failures
You probably are affected by the current DDOS to SE's servers, but this can also be caused by generally connectivity or routing issues to them as well. (Blame your ISP)
There isn't anything we can do to help you with these issues as they're outside of our control. You may have a better experience by changing your internet connection (try a mobile hotspot, use a different wifi/ethernet connection), or by using a VPN. (See early posts in this channel)
The text was updated successfully, but these errors were encountered: