(tracking) Remote MCDU Known issues and (some) fixes

[Earthsam12]

The remote MCDU was merged into dev recently, and while it's working fine for most, there are many users experiencing issues with it. This issue will keep track of the issues raised in the support channel and the remote MCDU thread. I'll be adding more issues/fixes here as they appear in the discord.

Hopefully, the fixes to these issues can be found and can be added to the docs.

---

MCDU shows up, but only shows a black screen (Discord issue 1; Discord issue 2)

When does the issue show up: When connecting either by remote (ip) or via localhost

Fix: Open the port 8080 via the Windows firewall as per the docs.

Links: Discord issue 1; Discord issue 2; Docs; Github Issue

---

Port is in use (Discord issue)

When does the issue show up: When running server.exe. It can show in 2 ways:

1. Either with an error message like: Error: listen EACCES: permission denied 0.0.0.0:8080 or Error: listen EADDRINUSE: address already in use :::8125
2. server.exe gets stuck on waiting for simulator (Discord issue)

Fix: Change the port in the EFB and in server.exe to an unused port (the EFB setting and the server.exe port must be the same). See the docs

Links: Discord issue 1; Discord issue 2;

---

Strange text with no resemblence of the MCDU (Discord issue)

Image:

When does the issue show up: When connecting remotely. Works on localhost.

Fix: Under investigation...

---

Node spits an error when starting server.exe (Discord issue)

When does it happen: when starting server.exe

Fix: Make sure the Print Spooler service is running.

Links: Discord issue; Discord issue resolution