Mapset Verifier refuses to establish connection on localhost:5000

[p0s0]

When I try to use Mapset Verifier (prior to choosing a song folder,) nothing works. This persists after choosing a song folder, and I cannot run any checks.

I have no clue what's going on. I've restarted my PC, which did not help. I've tried running as administrator, and that also didn't help.

Any ideas?

Thanks.

[Naxesss]

I'm guessing it's either something to do with:

• Strange network configurations
  • Could potentially try restarting your router
  • Maybe check if your firewall is being overly strict (most easily done by temporarily disabling it)
• Or the frontend not having access to establish a connection to the backend
  • Perhaps being shut down / restricted preemptively somehow, e.g. because of some antivirus false positive
  • Maybe also worth checking if the backend is actually running by looking at what takes up port 5000 (iirc this blog describes how)

Could also be because of CORS settings in the backend, but given that you're the first person I've seen with this error I doubt it.

[p0s0]

I've tried everything you've mentioned that could be an issue.

• Netstat only returns one line when running:

netstat -aon | findstr '5000'

• Firewall has been disabled, did not work.
• Disabled antivirus and tried to use, still did not work.
• Router was restarted, still didn't work.

I've also went into signalr.js and modified the port to use (although probably done incorrectly with my luck,) and it still wouldn't work.

I have no clue what's going on.

[Naxesss]

If I open powershell and run:

• netstat -aon | findstr '5000'
• Get-Process -Id {process ids from above} | Select ProcessName,Id | Format-Table

I get the following:

Judging from your screenshot, it looks like MapsetVerifierBackend failed to start or got shut down somehow. The SYN_SENT message you're seeing means the frontend is actively trying to establish a connection, but isn't getting an answer.

Open up /Mapset Verifier/resources/app/api/win-x86 and make sure MapsetVerifierBackend.exe exists. If not, you need to:

1. Uninstall (simply running the installer again doesn't work)
2. Install again
3. Before running, whitelist the folder in your antivirus (so it doesn't try to remove the executable)

If it didn't get removed, I have no idea what could be wrong.

[p0s0]

This is so weird. I don't know if the file hash will help, but here you go:

Here's what Get-Process returns:

Seems like the backend may be crashing?