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

Popular posts from this blog

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Color B

Help! I accidently enabled HSTS–on localhost

I ran into an issue after accidently enabling HSTS for a website on localhost. This was not an issue for the original website that was running in IIS and had a certificate configured. But when I tried to run an Angular app a little bit later on http://localhost:4200 the browser redirected me immediately to https://localhost . Whoops! That was not what I wanted in this case. To fix it, you need to go the network settings of your browser, there are available at: chrome://net-internals/#hsts edge://net-internals/#hsts brave://net-internals/#hsts Enter ‘localhost’ in the domain textbox under the Delete domain security policies section and hit Delete . That should do the trick…

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.