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

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

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

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...
Read more