If something goes wrong, every request will end up on the same screen. That screen specifies what went wrong, the address requested, the time in UTC and a request ID. Using that request ID, the notification can be found on the ‘Fouten’ screen of the console. Where a notification belongs is specified at Fout Melden.
Under ‘Context’ is the version that caused the error, from version 1.3.58 onwards. Without that version, an error means very little, as the code changes with every release. There is no footer on this page, so the version could not be seen there.
Anyone logged in to the console can see more: in addition to the version, they can also see the messages the code generated along the way, the full stack trace and, if the service failed to start, the relevant error message. A visitor who is not logged in cannot see this. That is a deliberate choice. A stack trace lists filenames and internal details, and the request ID is sufficient to report an error.
The ‘Copy as Markdown’ button copies the entire notification to the clipboard as Markdown, including from version 1.3.58 onwards. This text is intended for analysis and can be pasted into an email, an issue or a conversation with an assistant. The button captures whatever is displayed on the screen: including the stack and instructions for a logged-in administrator, but excluding those for any other visitor. The version number is always included.
The text on the clipboard contains no IP address, no browser identifier and no username. These three do not help when reading a stack, and they would be carried along to wherever the text is pasted. The Fouten screen does record them, however, as they are needed there to determine whether an error originates from a particular source.