104-0265 Error when connecting

I get the 104-0265 error when trying to join a match

Interesting, this error is related to the BOSS Module, related to SpotPass add-on communications. That is all I can tell you, as I am not aware of this error.

Are you on SSSL or Inkay? Ensure you have your DNS set to Auto-Obtain, and if not try using this guide: Error code 104-2210 [Unofficial Pretendo Wiki]

(I am aware this is for a different code, though it applies to this one too.)

Credit to @Joshua8600PNID for this information on: Error code 104-0265 Wii-U - #4 by Joshua8600PNID

I’m on Inkay, dns is on auto and already tried the -2210 solution, didn’t work

How did you install Inkay? Manually or via the Aroma Updater?

Just a minute, let me check something, I may know what is happening.

Ok, I think that the BOSS Client is simply experiencing a downtime event currently. I would say to give it a few hours check in and report back. Let me know if you need further assistance.

is there a diffrence/preferable option?

I don’t understand your comment, would you mind elaborating?

it was in response to your question on where I installed inkay (aroma or manual)

Well, there is no preferable option exactly. I was just wondering how you installed it.

is there a wesite or similar where I can check the status of the boss client?

Not to my knowledge, no.

The BOSS Module can be a bit strange at times, it has downtime here and there, the issue will most likely resolve itself with time.

An outage has not been confirmed and I doubt any systems are down at this time.

I didn’t exactly state it was confirmed, but suggested the idea, just because the module has been a bit strange in the past from my memory.

With this error in SPlatoon, you need to clear Shared Save Data for Splatoon to re-get news data.

  1. System Settings
  2. Data Management
  3. Splatoon Data Location
  4. Splatoon
  5. Delete SHARED DATA ONLY. do not delete the actual save data
  6. relaunch splatoon

it should work now. if you get the same error a 2nd time, do it all again. @BigKafka

Was this issue resolved @BigKafka?

Topic closed due to lack of response.