How to Stop Nintendo Account connection attempts and ERPT logs generation in EMUNAND

[Willsito_GG]

Hello GBATemp Team,

First of all, thank you very much for your support and help in any adventure that we might have within this console scene

I am opening this post after searching for this information, in order to follow up with you about the following concern I have with my recently updated and tested v1 Nintendo Switch. My current setup is FW 20.3.0, Atmosphère 1.9.3, SD card formatted as FAT32 with everything updated, tested and working perfectly, except for what I describe below.

To test this, I removed all SysModules from the SD\atmosphere\contents folder, used all configuration files without modifications in SD\atmosphere\config, SD\config and others, making sure this is not caused by a bad configuration or a faulty or incompatible SysModule. All games work fine and I use Impeeza’s SysPatch SysModule without any issues.

The problem is the following: after navigating through the Switch menu, HBMenu, playing games and so on, the SD\atmosphere\erpt_reports folder gets filled with error logs every 10 or 15 minutes.

I have tried the following but the error generation still occurs:

1. In SD\exosphere.ini, setting to 0 or 1 and testing all combinations of the following parameters: debugmode=1 and debugmode_user=0
2. In SD\atmosphere\config\system_settings.ini, setting to 0 or 1 and testing all combinations of the following parameters: enable_am_debug_mode = u8!0x0 and enable_dns_mitm = u8!0x1
3. In SD\config\sys-patch\config.ini (SysPatch SysModule, both Impeeza and Tomvita’s builds), setting the following parameter: [erpt] disable_erpt_sigpatch=1
4. Using Linkalho to link and unlink selected accounts (I do not want to leave it unlinked as I play games that require this feature/setting).
5. I am not going to use Airplane Mode or similar alternatives, as I have a very stable internet connection and everything internet related works perfectly within my EMUNAND.

It is clear that Atmosphere automatically cleans that directory when it reaches 1000 files, and this can be disabled with “disable_automatic_report_cleanup = u8!0x0” within SD\atmosphere\config\system_settings.ini.

The thing I wanted to ask or request is: does anyone know how to truly deactivate the processes that trigger the lookup for the Nintendo Account connection? The error generation is only the tip of the iceberg, because the real problem is, in my opinion, the waste of resources. This includes CPU usage to manage all of this, attempts to connect to the internet using the Wi-Fi module, and the read and write operations on the SD card. If these processes were not executed, it could help reduce the Switch’s power consumption, improve loading times and extend battery life.

Many thanks in advance.

PS: Here are some interpretations of the errors generated within SD\atmosphere\erpt_reports:

2123-0011
Type: communication failure with Nintendo servers.
Triggered by: nn.account.EventHandler (account module).
Active app: Retroarch (running from SD).
Meaning: the console tries to talk to Nintendo, and since it is blocked, unlinked or DNS broken, it fails and logs the event.

2123-0011
Type: communication error with Nintendo services.
Triggered by: nn.account.EventHandler (account module trying to contact Nintendo).
App in foreground: Retroarch (from SD card).
Power states: Previous=6 → Destination=3 → Current=3 (going to sleep, typical background refresh attempt).
Meaning: the console keeps trying to contact Nintendo and fails, which makes sense if you have DNSMiTM, hosts, 90DNS or Incognito. If you want zero attempts or logs, cut the trigger by unlinking accounts with Linkalho on that NAND or keeping airplane mode enabled so there are no attempts or new reports.

2123-0011
Meaning: communication failure with Nintendo servers (blocked network, DNS or server issue).
Triggered by: nn.account.EventHandler (account module trying to contact Nintendo).
When and context: running Retroarch from SD card, Wi-Fi history present and WlanCommandEventHistory block detected, so the attempt happened during active gameplay.
Power states: Previous=6 → Destination=3 → Current=3 (transition to sleep), which matches account refresh attempts in the background.

 

[thesjaakspoiler]

The whole point of modules like MITM is to prevent you from connecting to Nintendo's server so that your Switch doesn't get banned.
By doing so, you can keep on playing online with your OFW.

Afaik, if you set up things by default, you should not get such errors in CFW and everything connecting to nintendo will just be blocked.
So it sounds like you enabled some debug feature somewhere.
Are all the config files in the right location?
If the article/youtube video you followed is a bit old, things might have changed.
Also note that Hekate and Atmosphere do not share 1 config file.

 

[masagrator]

1. Don't use fake linking
2. Don't use ctest patches
3. Don't blank prodinfo

That should be enough to fix it.

Dunno if "unlinking" will help here after you already did fake linking once.

That issue happens because you did something that should be done online connected to Nintendo servers, so some data is lacking and it constantly tries to connect to Nintendo servers which are blocked.

 

[josete2k]

That issue happens because you did something that should be done online connected to Nintendo servers, so some data is lacking and it constantly tries to connect to Nintendo servers which are blocked.

The 20 firmware itself... It requires to connect to Nintendo servers once.

 

[masagrator]

The 20 firmware itself... It requires to connect to Nintendo servers once.

It doesn't require, only if you want to utilize some part of system functions without using any workarounds.

Pirates are still playing games like nothing happened while legal users are forced into this "virtual gamecard or always online choice" stuff.

 

[Willsito_GG]

Thank you very much masagrator, josete2k and thesjaakspoiler for your answers!

I asnwer you in the following manner:

The whole point of modules like MITM is to prevent you from connecting to Nintendo's server so that your Switch doesn't get banned.
By doing so, you can keep on playing online with your OFW.

Afaik, if you set up things by default, you should not get such errors in CFW and everything connecting to nintendo will just be blocked.
So it sounds like you enabled some debug feature somewhere.
Are all the config files in the right location?
If the article/youtube video you followed is a bit old, things might have changed.
Also note that Hekate and Atmosphere do not share 1 config file.

Regarding the config files:
I have them exactly as they come by default, in the following paths, without changing anything. You can see them attached to this reply.
The only one that is different is /hosts/sysmmc.txt, which does not block the addresses.

• /sdmc/exosphere.ini
• /sdmc/atmosphere/config/System_settings.ini
• /sdmc/atmosphere/hosts/emummc.txt
• /sdmc/atmosphere/hosts/sysmmc.txt
• /sdmc/emuMMC/emummc.ini
  

1. Don't use fake linking
2. Don't use ctest patches
3. Don't blank prodinfo

That should be enough to fix it.

Dunno if "unlinking" will help here after you already did fake linking once.

That issue happens because you did something that should be done online connected to Nintendo servers, so some data is lacking and it constantly tries to connect to Nintendo servers which are blocked.

It doesn't require, only if you want to utilize some part of system functions without using any workarounds.

Pirates are still playing games like nothing happened while legal users are forced into this "virtual gamecard or always online choice" stuff.

Regarding the advice:

• I have restored the profile I had, which was already logged in from the SYSNAND.
• I have disabled the CTEST patches.
• I do not have blank prodinfo enabled.

However, the errors about connection attempts to Nintendo servers are still being generated.

The 20 firmware itself... It requires to connect to Nintendo servers once.

That is what it seems: It generates several files at the begining but eventually it stops generating files while a long time playing.

Thank you very much again!

Best regards

Willsito

 

[masagrator]

However, the errors about connection attempts to Nintendo servers are still being generated.

It's not a big deal. A big deal is when it's created every second - and I was talking about such case.

 

[Willsito_GG]

It's not a big deal. A big deal is when it's created every second - and I was talking about such case.

Agree with that.

The point is why some people is not having this behavior under the same circumstances?

 

[Bigdrago]

Enable flight mode?

 

[Andre63]

Hi all

I can't find the original thread to credit the authors, but adding the lines below to the end of system_settings.ini worked for me.

[ns.notification]
enable_download_task_list = u8!0x0
enable_download_ticket = u8!0x0
enable_network_update = u8!0x0
enable_random_wait = u8!0x0
enable_request_on_cold_boot = u8!0x0
enable_send_rights_usage_status_request = u8!0x0
enable_sync_elicense_request = u8!0x0
enable_version_list = u8!0x0
retry_interval_min = u32!0x7FFFFFFF
retry_interval_max = u32!0x7FFFFFFF
version_list_waiting_limit_bias = u32!0x7FFFFFFF
version_list_waiting_limit_min = u32!0x7FFFFFFF
[npns]
sleep_periodic_interval = u32!0x7FFFFFFF
sleep_processing_timeout = u32!0x0

 

[Willsito_GG]

Hi all

I can't find the original thread to credit the authors, but adding the lines below to the end of system_settings.ini worked for me.

[ns.notification]
enable_download_task_list = u8!0x0
enable_download_ticket = u8!0x0
enable_network_update = u8!0x0
enable_random_wait = u8!0x0
enable_request_on_cold_boot = u8!0x0
enable_send_rights_usage_status_request = u8!0x0
enable_sync_elicense_request = u8!0x0
enable_version_list = u8!0x0
retry_interval_min = u32!0x7FFFFFFF
retry_interval_max = u32!0x7FFFFFFF
version_list_waiting_limit_bias = u32!0x7FFFFFFF
version_list_waiting_limit_min = u32!0x7FFFFFFF
[npns]
sleep_periodic_interval = u32!0x7FFFFFFF
sleep_processing_timeout = u32!0x0

Good one Andre63, thank you very very much!

About that, I googled it and I found this post https://github.com/hanai3Bi/Switch-OC-Suite/blob/master/system_settings.md which has these parameters + other ones.

The thing is that this would be perfect if the SYSNAND would't be used with Atmosphere (as some people use SYSNAND with Atmosphere), as it is not possible to have different system_settings.ini, one for the SYSNAND and one for the EMUNAND...

Anyway, thanks a lot for this useful info! I will test it and will let you know!

Best regards

Willsito

 

[martinlvm]

Good one Andre63, thank you very very much!

About that, I googled it and I found this post https://github.com/hanai3Bi/Switch-OC-Suite/blob/master/system_settings.md which has these parameters + other ones.

The thing is that this would be perfect if the SYSNAND would't be used with Atmosphere (as some people use SYSNAND with Atmosphere), as it is not possible to have different system_settings.ini, one for the SYSNAND and one for the EMUNAND...

Anyway, thanks a lot for this useful info! I will test it and will let you know!

Best regards

Willsito

You can copy another instance of atmosphere to the sd card in another folder like "atmosphere ofw" or something like that. Modify the system_settings.ini from this new instance of atmosphere and in the hekate.ini modify the path of package3 to the new path:

[Stock - sysMMC]
fss0=atmosphere ofw/package3
emummc_force_disable=1
stock=1

something like that.

The atmosphere folder shouldn't be larger than 10mb so it shouldn't a be a issue from a storage point of view.

 

[Earthshine]

For the record, the erpt logs clear themselves after they reach a limit since Atmosphere 1.3.1.

• A mechanism for automatically cleaning up erpt_reports was added.
  • When booting, if the console has more than 1000 reports inside /atmosphere/erpt_reports, the folder will be cleaned to empty.
  • This behavior can be disabled by setting erpt!disable_automatic_report_cleanup = u8!0x1 in system_settings.ini.

But yes, I do also understand that some people don't want ANY logs to be written to begin with.

 

[Willsito_GG]

You can copy another instance of atmosphere to the sd card in another folder like "atmosphere ofw" or something like that. Modify the system_settings.ini from this new instance of atmosphere and in the hekate.ini modify the path of package3 to the new path:

[Stock - sysMMC]
fss0=atmosphere ofw/package3
emummc_force_disable=1
stock=1

something like that.

The atmosphere folder shouldn't be larger than 10mb so it shouldn't a be a issue from a storage point of view.

Hi martinlvm,

Thanks for your message!

I think that is a good idea to be tested. The thing is that, in my case, as I have another method, different from Hekate use, to go from EMUNAND to SYSNAND and viceversa (https://gbatemp.net/threads/request...d-functioning-payloads-creation.659706/page-2), wouldn't work in my case, as fusee.bin always "look" into the official Atmosphere folder.

Anyway, I will give a try and will let you know!

For the record, the erpt logs clear themselves after they reach a limit since Atmosphere 1.3.1.

• A mechanism for automatically cleaning up erpt_reports was added.
  • When booting, if the console has more than 1000 reports inside /atmosphere/erpt_reports, the folder will be cleaned to empty.
  • This behavior can be disabled by setting erpt!disable_automatic_report_cleanup = u8!0x1 in system_settings.ini.

But yes, I do also understand that some people don't want ANY logs to be written to begin with.

Hi Earthshine,

Thanks for your message as well!

Exactly, it is what you say at the end of your message: "some people don't want ANY logs to be written", as the trigger behind is really the problem, and logs are the symptom.

Best regards!

PS: I will be soon doing a full format to my Switch, to start from scratch, and will let you know the results

 

[Willsito_GG]

Hello Team,

Just wanted to share with you guys that I have recently made a full format and a start from scratch with my Nintendo Switch and I come with some news regarding my findings.

About his particular issue, ERPT logs generation in EMUNAND, it has been solved by "installing" josete2k build of Sys-Patch Sysmodule, that you can find here: https://gbatemp.net/threads/updated...pletes-faster-on-standby.674288/post-10709303

I have been doing a quite exhaustive regression testing, after the full format and fresh install of everything (FW 20.4.0, Atmosphère 1.9.4, SD card formatted as FAT32), testing many different menus, homebrew, games and emulation and I can say that, except the NS Services issue that causes slowdown in loading the images of the games in the "all programs" within the main menu + some DBI tools (not anymore with JKSV, many thanks JK ), everything works like a charm.

Plus, the battery drain problem has been solved as well

I desestimate the adding of in the \atmosphere\config\system_settings.ini because I sometimes use the sysnand with Atmosphere and I do not want to impact anything with this system_settings file:

[ns.notification]
enable_download_task_list = u8!0x0
enable_download_ticket = u8!0x0
enable_network_update = u8!0x0
enable_random_wait = u8!0x0
enable_request_on_cold_boot = u8!0x0
enable_send_rights_usage_status_request = u8!0x0
enable_sync_elicense_request = u8!0x0
enable_version_list = u8!0x0
retry_interval_min = u32!0x7FFFFFFF
retry_interval_max = u32!0x7FFFFFFF
version_list_waiting_limit_bias = u32!0x7FFFFFFF
version_list_waiting_limit_min = u32!0x7FFFFFFF
[npns]
sleep_periodic_interval = u32!0x7FFFFFFF
sleep_processing_timeout = u32!0x0

Hope this helps!

Thank you very much,

Best regards

Willsito