I upgraded from MeshCentral v0.4.8-e to v0.4.9-a earlier today and noticed that when I visit the /player.htm path on my domain, the browser returns a 404: Not Found page instead of the expected Session Player. The same path worked fine prior to the upgrade.
I did change how the player is served to make translatable to different languages and made it a .handlebar since I am working on better integration. Weird... Can you enable "WebRequest" tracing and request the player.htm and let me know what you see?

By the way, I am working on having the player be able to "seek" anywhere inside a .mcrec file now. It requires that the .mcrec file be "indexed" by making a run thru the file and setting up time stamps, etc. Once that is done, the player should be able to move anywhere thru the file.
Looks like an issue with the redirect from http to https.
Oh right... there is no redirection from HTTP. I can add it. Will wait for @whalehub to confirm that is the problem.
Same for me after updating from 0.4.8-e to 0.4.9-a,
server tracking doesn't show anything relevant.

and the page produced is just this

I'm using meshcentral with nginx, and https.
Are you using a "meshcentral-web" folder?
no, just default install
Thanks. I will investigate.
the bug is in webserver.js line 2091
if ((domain == null) || (domain.redirects == null)) { res.sendStatus(404); return; }
domain.redirects is undefined and the function returns a simple 404 status error
Thanks you. It's so much better when I get the answer :) Published MeshCentral v0.4.9-c with the fix. Let me know if it works.
@Ylianst I can confirm that the problem has been fixed in the latest version.
Most helpful comment
the bug is in webserver.js line 2091
if ((domain == null) || (domain.redirects == null)) { res.sendStatus(404); return; }domain.redirects is undefined and the function returns a simple 404 status error