Window is Blank/Never Loads

[Shadowmech88]

Expected Behavior

To see something in the DCEF window.

Actual Behavior

DCEF window is just solid white.

Steps to reproduce the problem

1. Download latest release.
2. Run dcef.exe.
3. See nothing.

Specifications

Environment

• Operating system: Windows 10 version 1809 build 17763.4131
• CPU Architecture: x86_64 (PC)
• Flavor: Windows binary release

DiscordChatExporter-frontend

• Release version or commit hash: v2.1.0
• Can the issue be reproduced in the demo?: No

DiscordChatExporter

• Version (CLI --version): v2.39.1

How did you export the data?

• Irrelevant, this issue happens even when the only guild in the exports folder is the example guild.

Logs

Is there any relevant information in logs? If so, please provide them:

dcef/logs.txt: logs.txt The backend error log was empty.

I don't really know what the problem could be. I read through the logs; nothing stuck out to me.

[slatinsky]

Hello,

Thanks for the repport

I haven't found a way to reproduce this issue, but 3 different people have reported it to me so far.

Till I find a way to reproduce this issue, you can use an older release, before the code was rewritten almost from scratch: Release v1.13.2

[Shadowmech88]

Will the older release work with exports generated by newer versions of Discord Chat Exporter?

[slatinsky]

The JSON export format didn't change at all*. It will work.

*The only new feature that was added to DCE exporter is to export in non-processed format --markdown false. It didn't exist in that time, so emojis in that older release will be rendered too large if exported this way.

[Shadowmech88]

When using the old version, how do I shut down the program? I notice that even after closing the browser and nginx window, I can then reopen the browser and go to the same URL and the frontend is still running. Is there some process I have to kill, or will it quit after a while of receiving no requests, or what?

[slatinsky]

In the v1 release, is is just nginx that is "hosting" static files - everything is precomputed into static json files. All you need it is to kill nginx.exe

[Shadowmech88]

How is it that I can still access the page after killing nginx, though? Edit: Nevermind, I had to manually kill the process as well as the application.

[slatinsky]

True, you need to close nginx manually in the latest v1 release. But just closing the console window named "nginx" should be enough.

[slatinsky]

According to your logs, nginx reverse proxy didn't start at all. That confirms why your backend error log was empty. The same issue as #7.

[Shadowmech88]

Anything else I could try on my end that would help you diagnose the root cause?

[Glitch3dPenguin]

I thought I was running into this same issue. However, while I was looking for this the export just suddenly worked. It takes FOREVER to load and the all of a sudden it just fired right up. If there is any information from somewhere I can provide to help I will.