3DS not connecting to pretendo-docker server

[SpringtrapISZ]

I have pretendo-docker running on an AMD desktop computer (the one I'm using right now to complete this issue report), and I'm using an older wireless internet router to act as a LAN connection for all my stuff.

I have a 3DS and a Wii U that I'm using with the server... the Wii U seems to be doing just fine, however when using the FriendsAccountSwicther script on the 3DS, and the manual_override app to reset the Friends environment, it does not connect to the server. The newly created friend code is not displayed, but instead there are a bunch of question marks on my friend card, and when checking the logs in mitmproxy, I don't notice anything evident of an error. This is what the mitmproxy log is giving me:

POST http://nasc.pretendo.cc/ac/ HTTP/1.1
Host: nasc.pretendo.cc
X-GameId: 00003200
User-Agent: CTR FPD/0010
Content-Type: application/x-www-form-urlencoded
Content-Type: application/x-www-form-urlencoded
Content-Length: 838
gameid=MDAwMDMyMDA%2A&sdkver=MDAwMDAw&titleid=MDAwNDAxMzAwMDAwMzIwMg%2A%2A&gamecd=LS0tLQ%2A%2A&gamever=MDAxNQ%2A%2A&mediatype=MA%2A%2A&makercd=MDA%2A&unitcd=Mg%2A%2A&macadr=[REMOVED]&bssid=[REMOVED]&apinfo=[REMOVED]&fcdcert=[REMOVED]&servertype=TDE%2A&fpdver=MDAxMA%2A%2A&devtime=MjQxMDExMDAwMzQw&lang=MDE%2A&region=MDE%2A&csnum=Tlc0MDI2OTYyMA%2A%2A&passwd=[REMOVED]&action=TE9HSU4%2A&ingamesn=

Maintainer note: I have removed some of the provided console data for privacy reasons.

I am given an error code of 001-0502 on my 3DS when I load the friends list, and even when I reboot the system nothing changes. I cannot find anything online about this, so it may be a unique issue, but even still I don't know how to fix it. I also noticed there was no image for my mii on the web interface, when creating a PNID. I can provide screenshots, logs, and images, if necessary.

Thank you in advance for any help you may give.

[MatthewL246]

Can you provide the logs from the account server?

docker compose logs account

[SpringtrapISZ]

It is telling me there is no configuration file provided/not found

Also, thank you for removing data compromising information. I wasn't aware there was any in it ._.

[SpringtrapISZ]

Now it generated a new friend code, and seems to connect to the server, but returns error code 002-0102 upon opening friends list. I also just had to move the current directory to the docker clone directory, here is what the logs returned to me:

account-1  | [0:59:58] [INFO]: Loading config
account-1  | [0:59:58] [INFO]: Config loaded, checking integrity
account-1  | [0:59:58] [WARN]: Failed to find captcha secret config. Disabling feature. To enable feature set the PN_ACT_CONFIG_HCAPTCHA_SECRET environment variable
account-1  | [0:59:58] [WARN]: Failed to find Stripe api key! If a PNID is deleted with an active subscription, the subscription will *NOT* be canceled! Set the PN_ACT_CONFIG_STRIPE_SECRET_KEY environment variable to enable
account-1  | [0:59:58] [INFO]: [conntest] Applying imported routes
account-1  | [0:59:58] [INFO]: [conntest] Creating 'conntest' subdomain
account-1  | [0:59:58] [INFO]: [cbvc] Applying imported routes
account-1  | [0:59:58] [INFO]: [cbvc] Creating 'cbvc' subdomain
account-1  | [0:59:58] [INFO]: [NNAS] Applying imported routes
account-1  | [0:59:58] [INFO]: [NNAS] Importing middleware
account-1  | [0:59:58] [INFO]: [NNAS] Creating 'account' subdomain
account-1  | [0:59:58] [INFO]: [NNAS] Creating 'c.account' subdomain
account-1  | [0:59:58] [INFO]: [NASC] Importing middleware
account-1  | [0:59:58] [INFO]: [NASC] Applying imported routes
account-1  | [0:59:58] [INFO]: [NASC] Creating 'nasc' subdomain
account-1  | [0:59:58] [INFO]: [DATASTORE] Applying imported routes
account-1  | [0:59:58] [INFO]: [DATASTORE] Creating 'datastore' subdomain
account-1  | [0:59:58] [INFO]: [USER API] Importing middleware
account-1  | [0:59:58] [INFO]: [USER API] Applying imported routes
account-1  | [0:59:58] [INFO]: [USER API] Creating 'api' subdomain
account-1  | [0:59:58] [INFO]: [LOCAL-CDN] s3 enabled, skipping local CDN
account-1  | [0:59:58] [INFO]: [assets] Setting up public folder
account-1  | [0:59:58] [INFO]: [conntest] Creating 'assets' subdomain
account-1  | [0:59:58] [INFO]: Setting up Middleware
account-1  | [0:59:58] [INFO]: Creating 404 status handler
account-1  | [0:59:58] [INFO]: Creating non-404 status handler
account-1  | [0:59:58] [INFO]: Starting server
account-1  | (node:1) NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023.
account-1  |
account-1  | Please migrate your code to use AWS SDK for JavaScript (v3).
account-1  | For more information, check the migration guide at https://a.co/7PzMCcy
account-1  | (Use `node --trace-warnings ...` to show where the warning was created)
account-1  | [0:59:59] [SUCCESS]: Database connected
account-1  | [0:59:59] [SUCCESS]: Cache enabled
account-1  | [0:59:59] [SUCCESS]: gRPC server started on port 5000
account-1  | [0:59:59] [SUCCESS]: HTTP server started on port 8080
account-1  | GET / 200 4.067 ms - 240
account-1  | GET / 200 0.497 ms - 240
account-1  | POST /v1/api/oauth20/access_token/generate 400 44.539 ms - 137
account-1  | POST /v1/api/oauth20/access_token/generate 400 6.936 ms - 137
account-1  | GET / 200 0.330 ms - 240
account-1  | GET / 200 0.314 ms - 240
account-1  | POST /ac/ 200 10.542 ms - 54
account-1  | POST /ac/ 200 3.523 ms - 54
account-1  | POST /ac/ 200 3.356 ms - 54
account-1  | POST /v1/register 200 1868.621 ms - 222
account-1  | GET /v1/user 200 3.384 ms - 581
account-1  | GET /v1/user 200 2.690 ms - 581
account-1  | GET /v1/user 200 2.300 ms - 581
account-1  | GET /v1/user 200 3.528 ms - 581
account-1  | GET /v1/user 200 2.931 ms - 581
account-1  | GET /v1/user 200 2.414 ms - 581
account-1  | POST /ac/ 200 3.128 ms - 54
account-1  | GET /v1/user 200 3.100 ms - 581
account-1  | GET /v1/user 200 3.384 ms - 581
account-1  | GET /v1/user 200 2.368 ms - 581
account-1  | GET /v1/user 200 2.951 ms - 581
account-1  | GET /v1/user 200 2.690 ms - 581
account-1  | POST /v1/api/oauth20/access_token/generate 400 50.929 ms - 137
account-1  | POST /v1/api/oauth20/access_token/generate 400 50.087 ms - 137
account-1  | GET / 200 0.244 ms - 240
account-1  | GET /v1/api/admin/mapped_ids?input_type=user_id&output_type=pid&input=%20%2C 200 3.776 ms - 94
account-1  | GET / 200 0.284 ms - 240
account-1  | POST /ac/ 200 20.060 ms - 142
account-1  | POST /ac/ 200 15.434 ms - 142
account-1  | POST /ac/ 200 13.482 ms - 142
account-1  | GET /v1/user 200 2.296 ms - 581
account-1  | GET / 200 0.307 ms - 240
account-1  | GET /v1/api/admin/mapped_ids?input_type=user_id&output_type=pid&input=%20%2C 200 3.339 ms - 94
account-1  | GET /v1/api/people/@me/devices/owner 200 49.807 ms - 1180
account-1  | POST /v1/api/people/@me/devices/ 200 68.798 ms - 1180
account-1  | POST /v1/api/oauth20/access_token/generate 200 53.334 ms - 208
account-1  | PUT /v1/api/people/@me/miis/@primary 200 1633.516 ms - 0
account-1  | GET /v1/api/people/@me/profile 200 4.690 ms - 1200
account-1  | GET /v1/api/people/@me/profile 200 4.846 ms - 1200
account-1  | GET / 200 0.265 ms - 240
account-1  | POST /ac/ 200 14.213 ms - 142
account-1  | POST /ac/ 200 15.831 ms - 142
account-1  | POST /ac/ 200 12.465 ms - 142
account-1  | GET / 200 0.281 ms - 240
account-1  | POST /ac/ 200 14.207 ms - 142
account-1  | POST /ac/ 200 15.816 ms - 142
account-1  | POST /ac/ 200 13.487 ms - 142
account-1  | POST /ac/ 200 12.997 ms - 142
account-1  | POST /ac/ 200 13.361 ms - 142
account-1  | POST /ac/ 200 12.548 ms - 142
account-1  | POST /ac/ 200 16.089 ms - 142
account-1  | POST /ac/ 200 15.471 ms - 142
account-1  | POST /ac/ 200 13.224 ms - 142
account-1  | GET / 200 0.398 ms - 240
account-1  | GET /v1/user 400 4.434 ms - 68
account-1  | POST /v1/login 400 2.620 ms - 69
account-1  | POST /v1/login 200 43.674 ms - 222
account-1  | GET /v1/user 200 2.938 ms - 585
account-1  | Debugger listening on ws://0.0.0.0:9229/9b60c73b-5e93-4c73-8ed5-dcb692988016
account-1  | For help, see: https://nodejs.org/en/docs/inspector
account-1  | [18:14:6] [INFO]: Loading config
account-1  | [18:14:6] [INFO]: Config loaded, checking integrity
account-1  | [18:14:6] [WARN]: Failed to find captcha secret config. Disabling feature. To enable feature set the PN_ACT_CONFIG_HCAPTCHA_SECRET environment variable
account-1  | [18:14:6] [WARN]: Failed to find Stripe api key! If a PNID is deleted with an active subscription, the subscription will *NOT* be canceled! Set the PN_ACT_CONFIG_STRIPE_SECRET_KEY environment variable to enable
account-1  | [18:14:7] [INFO]: [conntest] Applying imported routes
account-1  | [18:14:7] [INFO]: [conntest] Creating 'conntest' subdomain
account-1  | [18:14:7] [INFO]: [cbvc] Applying imported routes
account-1  | [18:14:7] [INFO]: [cbvc] Creating 'cbvc' subdomain
account-1  | [18:14:7] [INFO]: [NNAS] Applying imported routes
account-1  | [18:14:7] [INFO]: [NNAS] Importing middleware
account-1  | [18:14:7] [INFO]: [NNAS] Creating 'account' subdomain
account-1  | [18:14:7] [INFO]: [NNAS] Creating 'c.account' subdomain
account-1  | [18:14:7] [INFO]: [NASC] Importing middleware
account-1  | [18:14:7] [INFO]: [NASC] Applying imported routes
account-1  | [18:14:7] [INFO]: [NASC] Creating 'nasc' subdomain
account-1  | [18:14:7] [INFO]: [DATASTORE] Applying imported routes
account-1  | [18:14:7] [INFO]: [DATASTORE] Creating 'datastore' subdomain
account-1  | [18:14:7] [INFO]: [USER API] Importing middleware
account-1  | [18:14:7] [INFO]: [USER API] Applying imported routes
account-1  | [18:14:7] [INFO]: [USER API] Creating 'api' subdomain
account-1  | [18:14:7] [INFO]: [LOCAL-CDN] s3 enabled, skipping local CDN
account-1  | [18:14:7] [INFO]: [assets] Setting up public folder
account-1  | [18:14:7] [INFO]: [conntest] Creating 'assets' subdomain
account-1  | [18:14:7] [INFO]: Setting up Middleware
account-1  | [18:14:7] [INFO]: Creating 404 status handler
account-1  | [18:14:7] [INFO]: Creating non-404 status handler
account-1  | [18:14:7] [INFO]: Starting server
account-1  | (node:1) NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023.
account-1  |
account-1  | Please migrate your code to use AWS SDK for JavaScript (v3).
account-1  | For more information, check the migration guide at https://a.co/7PzMCcy
account-1  | (Use `node --trace-warnings ...` to show where the warning was created)
account-1  | [18:14:8] [SUCCESS]: Database connected
account-1  | [18:14:8] [SUCCESS]: Cache enabled
account-1  | [18:14:8] [SUCCESS]: gRPC server started on port 5000
account-1  | [18:14:8] [SUCCESS]: HTTP server started on port 8080
account-1  | GET / 200 4.161 ms - 240
account-1  | POST /ac/ 200 28.158 ms - 54
account-1  | POST /ac/ 200 3.677 ms - 54
account-1  | POST /ac/ 200 3.054 ms - 54
account-1  | POST /ac/ 200 2.978 ms - 54

(I am sorry in advance if I missed something and didn't remove it, I don't know what embedded data may or may not be safe to share. Please forgive me.)

[MatthewL246]

(I am sorry in advance if I missed something and didn't remove it, I don't know what embedded data may or may not be safe to share. Please forgive me.)

No worries, there are no issues with the logs there. The issue with your first post is that the 3DS sends some base64-encoded private/console-specific information like the MAC address, WiFi info, and fcdcert. The one that's particularly risky is the fcdcert: this is the certificate that Pretendo uses to enforce console bans. Be careful not to send that publicly in the future, as someone could potentially copy it and use it to evade bans on Pretendo's official servers while appearing to be your console.

Now it generated a new friend code, and seems to connect to the server, but returns error code 002-0102 upon opening friends list.

That error will appear when the console attempts to log in with a NEX account (essentially, the internal account that the friend code is generated from) that doesn't exist on the server. For example, trying to log into your local server with a Pretendo NEX account or vice versa.

I'd suggest that you make sure that Nimbus is set to Pretendo and then try re-running the reset friends test account app.

[SpringtrapISZ]

No worries, there are no issues with the logs there. The issue with your first post is that the 3DS sends some base64-encoded private/console-specific information like the MAC address, WiFi info, and fcdcert. The one that's particularly risky is the fcdcert: this is the certificate that Pretendo uses to enforce console bans. Be careful not to send that publicly in the future, as someone could potentially copy it and use it to evade bans on Pretendo's official servers while appearing to be your console.

Ah okay... now that I know what information is sensitive, I'll be sure to exclude it. Thank you.

That error will appear when the console attempts to log in with a NEX account (essentially, the internal account that the friend code is generated from) that doesn't exist on the server. For example, trying to log into your local server with a Pretendo NEX account or vice versa.

That's what I had thought, although resetting the friends code environment once again, like you suggested below, did nothing before. I'll be sure to try that again here momentarily, and I'll report back when I recieve something in return.

I'd suggest that you make sure that Nimbus is set to Pretendo and then try re-running the reset friends test account app.

I triple checked to make sure that was correctly set before I began troubleshooting. Thank you for your help, I greatly appreciate it.

[SpringtrapISZ]

Tried resetting the friend code again, friend card has no code now and I get an error of 001-0502 when I open the friends list. Tried restarting it three or four times, nothing changed.

[MatthewL246]

Thanks for trying, and I'm sorry that didn't work.

Error code 001-0502 is a common generic error code that unfortunately only says that the console failed to connect to the friends server. Let's try to narrow this down:

1. Is the console successfully sending requests through mitmproxy?
2. Is the account server successfully receiving and responding to the requests?
3. On the console, has the NEX account been created yet?
   • Look at the most recent POST http://nasc.pretendo.cc/ac/ request in mitmproxy, and check whether the request data contains either the passwd or the userid parameter. For example, the original request you submitted in the issue body does contain it.
   • If it contains passwd, then the account has not been created yet and this is the initial account creation request.
   • If it contains userid, then the account has already been created.
   • Sidenote: Yes, it's a little weird: when creating a new NEX account, the console generates the account's password locally and sends that password to the server. Then, the server generates a PID (principal ID, basically the account's username), stores the new account in the database, and responds with the PID. The console then stores the PID and password, and at this point, your new friend code shows up.
4. Is the console connecting to the friends server at all?
   • Check docker compose logs friends.

[SpringtrapISZ]

Thanks for trying, and I'm sorry that didn't work.

Not a problem, I really appreciate you helping... this continues to be an active problem for me.

Error code 001-0502 is a common generic error code that unfortunately only says that the console failed to connect to the friends server. Let's try to narrow this down:

1. Is the console successfully sending requests through mitmproxy?

2. Is the account server successfully receiving and responding to the requests?

3. On the console, has the NEX account been created yet?

   • Look at the most recent POST http://nasc.pretendo.cc/ac/ request in mitmproxy, and check whether the request data contains either the passwd or the userid parameter. For example, the original request you submitted in the issue body does contain it.
   • If it contains passwd, then the account has not been created yet and this is the initial account creation request.
   • If it contains userid, then the account has already been created.
   • Sidenote: Yes, it's a little weird: when creating a new NEX account, the console generates the account's password locally and sends that password to the server. Then, the server generates a PID (principal ID, basically the account's username), stores the new account in the database, and responds with the PID. The console then stores the PID and password, and at this point, your new friend code shows up.

I'm checking this ^ right now, and it seems that every time I make a PNID with my local server, it stays on the 3DS until I reboot it. Then it gets wiped. I noticed that both after I linked the ID made through the web interface, and after I rebooted the 3DS, it contained the passwd parameter. I have noticed, however, while accidentally letting my 3DS connect to legitimate Pretendo services, it instantly creates a friend code, and I appear as online in the friends list, with this newly generated friend code.

4. Is the console connecting to the friends server at all?

   • Check docker compose logs friends.

I'll be checking this momentarily ^

[SpringtrapISZ]

I have tried three different times to check the friends list logs, and each time returns basically nothing, and says that the execution has paused because the program is panicking. I'm finding it rather odd that linking my PNID to my 3DS resets after a reboot... it may be my problem, but I don't know what would be causing it to not save it. I do work a job, so typically I am quite busy, however I will respond as soon as I can.

[MatthewL246]

Sorry for the late response, I've been very busy with college work.

I'm finding it rather odd that linking my PNID to my 3DS resets after a reboot

That is odd. I would guess that the fact that it can't successfully connect to the Friends server causes it to "forget" the PNID?

I have tried three different times to check the friends list logs, and each time returns basically nothing, and says that the execution has paused because the program is panicking.

That does sound like a problem. Do you have any way to try connecting to the Go debugger? I have a launch configuration for vscode.

[SpringtrapISZ]

I do appreciate the help, I also apologize for my late response, I have been busy with work. I am away from my computer for the weekend, but I should be able to report back with more information on Monday or Tuesday.

[SpringtrapISZ]

I didn't have a whole lot of time at the moment to work on it, however I did get it to start running. It returned with an error though, so it did not debug. Here is the log:

 *  Executing task: npm install && npm run build 

npm warn deprecated sourcemap-codec@1.4.8: Please use @jridgewell/sourcemap-codec instead
npm warn deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm warn deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm warn deprecated har-validator@5.1.5: this library is no longer supported
npm warn deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.

added 715 packages, and audited 716 packages in 9s

73 packages are looking for funding
  run `npm fund` for details

19 vulnerabilities (2 low, 9 moderate, 7 high, 1 critical)

To address issues that do not require attention, run:
  npm audit fix

To address all issues possible (including breaking changes), run:
  npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.
npm notice
npm notice New minor version of npm available! 10.8.2 -> 10.9.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.9.0
npm notice To update run: npm install -g npm@10.9.0
npm notice

> account@2.0.0 build
> npm run lint && npm run clean && npx tsc && npx tsc-alias && npm run copy-static


> account@2.0.0 lint
> npx eslint .


C:\[hidden]\pretendo-docker\repos\account\src\database.ts
  118:18  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any

C:\[hidden]\pretendo-docker\repos\account\src\middleware\api.ts
  16:3  warning  Possible race condition: `request.pnid` might be assigned based on an outdated state of `request`  require-atomic-updates        

C:\[hidden]\pretendo-docker\repos\account\src\middleware\nasc.ts
  190:24  warning  Forbidden non-null assertion                                                                             @typescript-eslint/no-non-null-assertion
  230:2   warning  Possible race condition: `request.nexAccount` might be assigned based on an outdated state of `request`  require-atomic-updates

C:\[hidden]\pretendo-docker\repos\account\src\middleware\pnid.ts
  82:2  warning  Possible race condition: `request.pnid` might be assigned based on an outdated state of `request`  require-atomic-updates        

C:\[hidden]\pretendo-docker\repos\account\src\server.ts
  85:17  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any

C:\[hidden]\pretendo-docker\repos\account\src\services\api\routes\v1\user.ts
  166:35  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any

C:\[hidden]\pretendo-docker\repos\account\src\services\grpc\api\get-user-data.ts
  9:15  warning  Forbidden non-null assertion  @typescript-eslint/no-non-null-assertion

C:\[hidden]\pretendo-docker\repos\account\src\services\grpc\api\login.ts
  34:34  warning  Forbidden non-null assertion  @typescript-eslint/no-non-null-assertion
  40:47  warning  Forbidden non-null assertion  @typescript-eslint/no-non-null-assertion
  46:35  warning  Forbidden non-null assertion  @typescript-eslint/no-non-null-assertion

C:\[hidden]\pretendo-docker\repos\account\src\services\grpc\api\set-discord-connection-data.ts
  8:15  warning  Forbidden non-null assertion  @typescript-eslint/no-non-null-assertion

C:\[hidden]\pretendo-docker\repos\account\src\services\grpc\api\set-stripe-connection-data.ts
  20:15  warning  Forbidden non-null assertion  @typescript-eslint/no-non-null-assertion

C:\[hidden]\pretendo-docker\repos\account\src\services\grpc\api\update-user-data.ts
  9:15  warning  Forbidden non-null assertion  @typescript-eslint/no-non-null-assertion

C:\[hidden]\pretendo-docker\repos\account\src\services\nnas\routes\account-settings.ts
   84:18  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
  110:18  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
  221:18  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any

C:\[hidden]\pretendo-docker\repos\account\src\types\express-subdomain.d.ts
  14:57  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any

C:\[hidden]\pretendo-docker\repos\account\src\types\express.d.ts
  12:27  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any

C:\[hidden]\pretendo-docker\repos\account\src\types\mongoose\device-attribute.ts
   9:18  warning  An empty interface is equivalent to `{}`                          @typescript-eslint/no-empty-interface
  11:11  warning  An empty interface is equivalent to `{}`                          @typescript-eslint/no-empty-interface
  13:18  warning  An interface declaring no members is equivalent to its supertype  @typescript-eslint/no-empty-interface

C:\[hidden]\pretendo-docker\repos\account\src\types\mongoose\device.ts
  27:18  warning  An empty interface is equivalent to `{}`                          @typescript-eslint/no-empty-interface
  29:11  warning  An empty interface is equivalent to `{}`                          @typescript-eslint/no-empty-interface
  31:18  warning  An interface declaring no members is equivalent to its supertype  @typescript-eslint/no-empty-interface

C:\[hidden]\pretendo-docker\repos\account\src\types\mongoose\nex-account.ts
  26:11  warning  An empty interface is equivalent to `{}`                          @typescript-eslint/no-empty-interface
  28:18  warning  An interface declaring no members is equivalent to its supertype  @typescript-eslint/no-empty-interface

C:\[hidden]\pretendo-docker\repos\account\src\types\mongoose\pnid.ts
  90:11  warning  An empty interface is equivalent to `{}`                          @typescript-eslint/no-empty-interface
  92:18  warning  An interface declaring no members is equivalent to its supertype  @typescript-eslint/no-empty-interface

C:\[hidden]\pretendo-docker\repos\account\src\types\mongoose\server.ts
  17:18  warning  An empty interface is equivalent to `{}`                          @typescript-eslint/no-empty-interface
  19:11  warning  An empty interface is equivalent to `{}`                          @typescript-eslint/no-empty-interface
  21:18  warning  An interface declaring no members is equivalent to its supertype  @typescript-eslint/no-empty-interface

C:\[hidden]\pretendo-docker\repos\account\src\util.ts
  318:38  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
  318:43  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any

✖ 34 problems (0 errors, 34 warnings)
  0 errors and 5 warnings potentially fixable with the `--fix` option.


> account@2.0.0 clean
> rimraf ./dist

npm error code ENOENT
npm error syscall lstat
npm error path C:\[hidden]\npm
npm error errno -4058
npm error enoent ENOENT: no such file or directory, lstat 'C:\[hidden]\npm'
npm error enoent This is related to npm not being able to find a file.
npm error enoent
npm error A complete log of this run can be found in: C:\[hidden]\_logs\2024-10-29T17_32_54_114Z-debug-0.log

 *  The terminal process "C:\Windows\System32\cmd.exe /d /c npm install && npm run build" terminated with exit code: -4058. 
 *  Terminal will be reused by tasks, press any key to close it. 

I had replaced the paths given by the log with "[hidden]", but any path that was referenced to was the users folder. I will see about returning to this once I get off of work later. Thanks in advance.

[MatthewL246]

Something is definitely wrong there - why is the build process running on Windows? It should be running in the Linux-based Node.js Docker container.

[SpringtrapISZ]

I had not realized there was a console/debugger through Docker... I am rather unfamiliar with Docker, please forgive me D:
Here are the logs from the Docker console. From connecting 3DS, without PNID linked, and without resetting friend code environment:

2024-10-30 02:08:05 mitmproxy-pretendo-1        | [06:08:05.118][172.18.0.1:41642] server connect nginx:80 (172.18.0.3:80)
2024-10-30 02:08:05 nginx-1                     | 2024/10/30 06:08:05 [info] 22#22: *52 client sent invalid header line: "HTTP_X_GAMEID: 00002400" while reading client request headers, client: 172.18.0.2, server: account.pretendo.cc, request: "GET / HTTP/1.1", host: "conntest.pretendo.cc"
2024-10-30 02:08:05 nginx-1                     | 2024/10/30 06:08:05 [info] 22#22: *52 client sent invalid header line: "HTTP_X_GAMEID: 00002400" while reading client request headers, client: 172.18.0.2, server: account.pretendo.cc, request: "GET / HTTP/1.1", host: "conntest.pretendo.cc"
2024-10-30 02:08:05 account-1                   | GET / 200 0.502 ms - 240
2024-10-30 02:08:05 nginx-1                     | 172.18.0.2 - - [30/Oct/2024:06:08:05 +0000] conntest.pretendo.cc "GET / HTTP/1.1" 200 240 "-" "CTR AC/02" "-" 0.002
2024-10-30 02:08:05 nginx-1                     | 172.18.0.2 - - [30/Oct/2024:06:08:05 +0000] conntest.pretendo.cc "GET / HTTP/1.1" 200 240 "-" "CTR AC/02" "-" 0.002
2024-10-30 02:08:05 mitmproxy-pretendo-1        | [06:08:05.121][172.18.0.1:41642] server disconnect nginx:80 (172.18.0.3:80)
2024-10-30 02:08:05 mitmproxy-pretendo-1        | [06:08:05.122][172.18.0.1:41642] client disconnect
2024-10-30 02:08:05 mitmproxy-pretendo-1        | [06:08:05.152][172.18.0.1:41652] client connect
2024-10-30 02:08:05 mitmproxy-pretendo-1        | [06:08:05.276][172.18.0.1:41652] server connect l-npns.app.pretendo.cc:443 (143.198.126.113:443)
2024-10-30 02:08:05 mitmproxy-pretendo-1        | [06:08:05.440][172.18.0.1:41652] server connect nginx:80 (172.18.0.3:80)
2024-10-30 02:08:05 nginx-1                     | 172.18.0.2 - - [30/Oct/2024:06:08:05 +0000] l-npns.app.pretendo.cc "GET /api/v1/notifications.json?maxlength=4 HTTP/1.1" 404 153 "-" "CTR/P/1.0.0/r62419" "-" 0.000
2024-10-30 02:08:05 nginx-1                     | 172.18.0.2 - - [30/Oct/2024:06:08:05 +0000] l-npns.app.pretendo.cc "GET /api/v1/notifications.json?maxlength=4 HTTP/1.1" 404 153 "-" "CTR/P/1.0.0/r62419" "-" 0.000
2024-10-30 02:08:05 mitmproxy-pretendo-1        | [06:08:05.470][172.18.0.1:41666] client connect
2024-10-30 02:08:05 mitmproxy-pretendo-1        | [06:08:05.503][172.18.0.1:41666] server connect nppl.c.app.pretendo.cc:443 (104.25.1.76:443)
2024-10-30 02:08:05 mitmproxy-pretendo-1        | [06:08:05.654][172.18.0.1:41666] server connect nginx:80 (172.18.0.3:80)
2024-10-30 02:08:05 boss-1                      | GET /p01/policylist/3/US 200 0.980 ms - 1318
2024-10-30 02:08:05 nginx-1                     | 172.18.0.2 - - [30/Oct/2024:06:08:05 +0000] nppl.c.app.pretendo.cc "GET /p01/policylist/3/US HTTP/1.1" 200 1318 "-" "PBOS-8.0/0000000203d0b22b-0000003d4c596c36/11.16.0-49U/62452/5" "-" 0.003
2024-10-30 02:08:05 nginx-1                     | 172.18.0.2 - - [30/Oct/2024:06:08:05 +0000] nppl.c.app.pretendo.cc "GET /p01/policylist/3/US HTTP/1.1" 200 1318 "-" "PBOS-8.0/0000000203d0b22b-0000003d4c596c36/11.16.0-49U/62452/5" "-" 0.003
2024-10-30 02:08:07 mitmproxy-pretendo-1        | [06:08:07.252][172.18.0.1:41674] client connect
2024-10-30 02:08:07 mitmproxy-pretendo-1        | [06:08:07.936][172.18.0.1:33566] server disconnect l-npns.app.pretendo.cc:443 (143.198.126.113:443)
2024-10-30 02:08:08 mitmproxy-pretendo-1        | [06:08:08.249][172.18.0.1:33566] client disconnect
2024-10-30 02:08:08 mitmproxy-pretendo-1        | [06:08:08.249][172.18.0.1:33566] server disconnect nginx:80 (172.18.0.3:80)
2024-10-30 02:08:08 nginx-1                     | 2024/10/30 06:08:08 [info] 22#22: *51 client 172.18.0.2 closed keepalive connection
2024-10-30 02:08:08 nginx-1                     | 2024/10/30 06:08:08 [info] 22#22: *51 client 172.18.0.2 closed keepalive connection
2024-10-30 02:08:10 mongodb-1                   | {"t":{"$date":"2024-10-30T06:08:10.724+00:00"},"s":"I",  "c":"WTCHKPT",  "id":22430,   "ctx":"Checkpointer","msg":"WiredTiger message","attr":{"message":{"ts_sec":1730268490,"ts_usec":724218,"thread":"1:0x7f1f9f3e16c0","session_name":"WT_SESSION.checkpoint","category":"WT_VERB_CHECKPOINT_PROGRESS","category_id":7,"verbose_level":"DEBUG_1","verbose_level_id":1,"msg":"saving checkpoint snapshot min: 1045, snapshot max: 1045 snapshot count: 0, oldest timestamp: (1730268190, 1) , meta checkpoint timestamp: (1730268490, 1) base write gen: 4741"}}}
2024-10-30 02:08:15 mitmproxy-pretendo-1        | [06:08:15.256][172.18.0.1:41674] error establishing server connection: [Errno -3] Temporary failure in name resolution
2024-10-30 02:08:15 mitmproxy-pretendo-1        | [06:08:15.306][172.18.0.1:41674] client disconnect
2024-10-30 02:08:17 mitmproxy-pretendo-1        | [06:08:17.258][172.18.0.1:36350] client connect
2024-10-30 02:08:17 mitmproxy-pretendo-1        | [06:08:17.402][172.18.0.1:36350] server connect nasc.pretendo.cc:443 (104.25.1.76:443)
2024-10-30 02:08:17 mitmproxy-pretendo-1        | [06:08:17.522][172.18.0.1:36350] server connect nginx:80 (172.18.0.3:80)
2024-10-30 02:08:17 account-1                   | POST /ac/ 200 81.244 ms - 54
2024-10-30 02:08:17 nginx-1                     | 172.18.0.2 - - [30/Oct/2024:06:08:17 +0000] nasc.pretendo.cc "POST /ac/ HTTP/1.1" 200 54 "-" "CTR FPD/0010" "-" 0.082
2024-10-30 02:08:17 nginx-1                     | 172.18.0.2 - - [30/Oct/2024:06:08:17 +0000] nasc.pretendo.cc "POST /ac/ HTTP/1.1" 200 54 "-" "CTR FPD/0010" "-" 0.082
2024-10-30 02:08:20 mitmproxy-pretendo-1        | [06:08:20.533][172.18.0.1:41666] server disconnect nppl.c.app.pretendo.cc:443 (104.25.1.76:443)
2024-10-30 02:08:32 mitmproxy-pretendo-1        | [06:08:32.430][172.18.0.1:36350] server disconnect nasc.pretendo.cc:443 (104.25.1.76:443)
2024-10-30 02:09:05 mitmproxy-pretendo-1        | [06:09:05.320][172.18.0.1:41652] server disconnect l-npns.app.pretendo.cc:443 (143.198.126.113:443)
2024-10-30 02:09:10 mitmproxy-pretendo-1        | [06:09:10.465][172.18.0.1:41652] server disconnect nginx:80 (172.18.0.3:80)
2024-10-30 02:09:10 mitmproxy-pretendo-1        | [06:09:10.655][172.18.0.1:41666] server disconnect nginx:80 (172.18.0.3:80)
2024-10-30 02:09:10 mongodb-1                   | {"t":{"$date":"2024-10-30T06:09:10.733+00:00"},"s":"I",  "c":"WTCHKPT",  "id":22430,   "ctx":"Checkpointer","msg":"WiredTiger message","attr":{"message":{"ts_sec":1730268550,"ts_usec":732977,"thread":"1:0x7f1f9f3e16c0","session_name":"WT_SESSION.checkpoint","category":"WT_VERB_CHECKPOINT_PROGRESS","category_id":7,"verbose_level":"DEBUG_1","verbose_level_id":1,"msg":"saving checkpoint snapshot min: 1059, snapshot max: 1059 snapshot count: 0, oldest timestamp: (1730268250, 1) , meta checkpoint timestamp: (1730268550, 1) base write gen: 4741"}}}
2024-10-30 02:09:22 mitmproxy-pretendo-1        | [06:09:22.616][172.18.0.1:36350] server disc ```

I'll see about testing more tomorrow afternoon before work.