Can't send crash reports 500 (internal server Error)

Bug Reports
1

I frequently can’t send a crash report. I then get the following message:

“The crash report could not be sent due to the following error: The server returned status code 500 (internal Server Error)”

I get this problem on Ubuntu and on Windows, but it seems like it happens more often on Ubuntu.

Additional problem: I can’t mark and copy the error message, which makes it even more annoying to google around it or post it here. Which is why I ignored it since several versions.

PS: Same when there is the “Upload images responsible for the crash” dialog. I can’t copy the path, so I manually need to search for the picture to check if I am fine with uploading it. Most likely I will say no, since that would require extra effort of me.

2

I’ve improved the crash reporting for next release – adding the possibility to directly view the images in the file system was on my TODO list for a while, I just didn’t get around to implement it so far. The error message is now also more detailed and is displayed in a text box so that it’s possible to copy it to the clipboard.

Unfortunately I don’t have a record of the 500 error, so we need to postpone the investigation to next time this happens with the next release.

3

thank you!

4

PS: Just had a crash report window, that got to big so the confirm buttons are outside my screen:

Screenshot 2026-06-09 151729
Screenshot 2026-06-09 1517291875×1080 169 KB

(I still could close it with my “ESC” button, but nevertheless you might want to fix this to.)

5

Thanks, will fix!

1 Like
6

hope this helps:

The server returned status code 500 (Internal Server Error):
{"statusMessage":"buf error","statusDebugMessage":"std.zlib.ZlibException@std/zlib.d(98): buf error\n----------------\n??:? [0xaaaae07dbf03]\n??:? [0xaaaae07dbb47]\n??:? [0xaaaae08025af]\n??:? [0xaaaae07e51cf]\n??:? [0xaaaae07d6f17]\n/var/www/shepherd/activation-server/source/app.d:439 [0xaaaae046257f]\n/var/www/shepherd/activation-server/source/app.d:442 [0xaaaae0461baf]\nhome/devops/.dub/packages/vibe-d/0.10.3/vibe-d/web/vibe/web/rest.d:1666 [0xaaaae049ccd3]\nhome/devops/.dub/packages/vibe-http/1.3.3/vibe-http/source/vibe/http/router.d:239 [0xaaaae05ab8af]\nhome/devops/.dub/packages/vibe-http/1.3.3/vibe-http/source/vibe/http/router.d:764 [0xaaaae05aea0f]\nhome/devops/.dub/packages/vibe-http/1.3.3/vibe-http/source/vibe/http/router.d:697 [0xaaaae05ab5cf]\nhome/devops/.dub/packages/vibe-http/1.3.3/vibe-http/source/vibe/http/router.d:230 [0xaaaae05ab38b]\nhome/devops/.dub/packages/vibe-http/1.3.3/vibe-http/source/vibe/http/internal/http1/server.d:301 [0xaaaae0677b43]\nhome/devops/.dub/packages/vibe-http/1.3.3/vibe-http/source/vibe/http/internal/http1/server.d:55 [0xaaaae0675f63]\nhome/devops/.dub/packages/vibe-http/1.3.3/vibe-http/source/vibe/http/internal/http1/server.d:51 [0xaaaae0675c67]\nhome/devops/.dub/packages/vibe-http/1.3.3/vibe-http/source/vibe/http/server.d:259 [0xaaaae05b4307]\nhome/devops/.dub/packages/vibe-http/1.3.3/vibe-http/source/vibe/http/server.d:1928 [0xaaaae05b99cf]\nhome/devops/.dub/packages/vibe-core/2.13.4/vibe-core/source/vibe/core/task.d:818 [0xaaaae0760373]\nhome/devops/.dub/packages/vibe-core/2.13.4/vibe-core/source/vibe/core/task.d:837 [0xaaaae075c803]\nhome/devops/.dub/packages/vibe-core/2.13.4/vibe-core/source/vibe/core/task.d:504 [0xaaaae075bf83]\nhome/devops/.dub/packages/vibe-core/2.13.4/vibe-core/source/vibe/core/task.d:413 [0xaaaae075b84b]\n??:? [0xaaaae07dca23]\n??:? [0xaaaae07ed65f]"}

Crash log file:
7

Although the root cause of the issue is still unclear, I’ve now changed the server code to accept the log file regardless of whether it has been compressed correctly (the log is sent as a gzip compressed file). So the next time this occurs, the crash report should go through successfully and I can take a look at what was actually being sent.

1 Like
8

Addition: When you successfully send a crash report, the program waits until you confirm this. It would be great if the program would already load the library in the background while waiting for me to click “Continue”.

9

Sounds like a good idea, I’ll change that for 1.0.0-rc.56.

1 Like