Skip to main content

Seq - ERR_SSL_PROTOCOL_ERROR

Structured logging is the future and tools like ElasticSearch and Seq can help you manage and search through this structured log data.

While testing Seq, a colleague told me that he couldn’t access Seq. Instead his browser returned the following error:

ERR_SSL_PROTOCOL_ERROR

The problem was that he tried to access the Seq server using HTTPS although this was not activated. By default Seq runs as a windows service and listens only on HTTP.

To enable HTTPS some extra work needs to be done:

  • First make sure you have a valid SSL certificate installed in either the Local Machine or Personal certificate store of your Seq server.
  • Open the certificate manager on the server, browse to the certificate and read out the thumbprint value.
  • Now open a command prompt on the server and execute the following commands:
    • seq bind-ssl --thumbprint="THUMBPRINT HERE --port=9001
    • seq config -k api.listenUris -v https://YOURSERVER:9001
    • seq restart

Remark: The ‘--port’ parameter is only necessary when you are not listening on the standard HTTPS port(443).

More information: https://docs.datalust.co/docs/ssl

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more