No servers or messages load, not even the example provided

[Sethycakes]

Expected Behavior

Servers appearing on the side

Actual Behavior

There are only the HOME and Settings buttons in the app

Steps to reproduce the problem

1. Downloaded the Windows version
2. Ran dcef.exe

Specifications

Environment

• Operating system: Windows 10
• CPU Architecture: x86_64 (PC)
• Flavor: Windows binary release

DiscordChatExporter-frontend

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

DiscordChatExporter

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

How did you export the data?

• Export format (CLI --format): Json
• Downloaded assets (CLI --media): Yes
• Markdown processing (CLI --markdown): Yes
• Other CLI options (optional):

Logs

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

2024/03/08 13:51:27 [error] 44848#43784: *6 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: 127.0.0.1, server: localhost, request: "GET /api/guilds HTTP/1.1", upstream: "http://127.0.0.1:58000/guilds", host: "127.0.0.1:21011", referrer: "http://127.0.0.1:21011/"

[fuzzy-bit]

Having the same issue. Sometimes it just magically works, though.

[slatinsky]

Hello @fuzzy-bit,

Did you follow troubleshooting steps in FAQ section of the readme? https://github.com/slatinsky/DiscordChatExporter-frontend?tab=readme-ov-file#faq. Is there anything interesting in the logs?

[fuzzy-bit]

I looked in the logs after opening the program on Windows again, and I got this error: 2024-06-25 17:20:44.894772 fastapi: ERROR: [Errno 13] error while attempting to bind on address ('0.0.0.0', 58000): tentativo di accesso al socket con modalità non consentite dalle rispettive autorizzazioni di accesso

It seems like it can't use the port due to some privilege issue.

[slatinsky]

Something else is listening on that port 58000. Does that happen after you restart your computer?

[fuzzy-bit]

Still happens after restarting. Resource Monitor does not report anything listening on port 58000.

[slatinsky]

Based on your error message, 58000 port may be excluded on your system. To list excluded post, you can run netsh int ipv4 show excludedportrange protocol=tcp in the windows terminal

related so question

[fuzzy-bit]

Sorry for never replying, but this fixed my issue! Thank you very much.

[slatinsky]

Thank you for the response <3. Keeping this issue up, because I should change that port to be more uncommon