---
title: "Germany Website Go-Live: Unusual Technical Issues Encountered in Production Deployment"
description: "A record of four unusual technical issues encountered in the two weeks before the German e-commerce site went live: an outdated WSL kernel, an oversized Strapi image, Docker DNS failures, and a SQL Server TLS version incompatibility."
canonical_url: "https://blog.markkulab.net/en/post/germany-website-go-live-encountered-special-technical-problems"
author: "Mark Ku"
author_url: "https://blog.markkulab.net/en/author/mark-ku"
site: "Mark Ku's Tech Notes"
date_published: "2024-07-06 01:01:35 +0800"
category: "DevOps"
tags: ["devops", "docker", "dns", "sql server", "tls", "windows server", "deployment", "troubleshooting"]
language: "en"
license: "CC BY 4.0"
license_url: "https://creativecommons.org/licenses/by/4.0/"
attribution: "when reusing or quoting, credit the author and link back to the original"
---

# Germany Website Go-Live: Unusual Technical Issues Encountered in Production Deployment

## Background

These problems surfaced during the two weeks before the German website's production go-live, as we were setting up the live environment. I'm writing this down as a record.

### Windows Subsystem for Linux Kernel Too Old

While building the CI/CD pipeline for the German production environment two weeks before launch, Docker builds kept failing. After investigation and research I couldn't find a clear answer online — probably because running Docker on Windows servers is uncommon enough that there isn't much community experience to draw from.

After comparing environments, I realized our Taiwan development machines were all running Docker on Windows 11, while the Windows Server 2019 production host maps to a Windows 10 kernel. The outdated Linux kernel inside WSL caused Docker builds to fail. After multiple reinstallations and attempts on different machines the issue persisted: everything worked fine in the Taiwan dev environment, but the build consistently failed in production.

My hypothesis was that this was tied to the Windows version: Windows Server 2019 corresponds to Windows 10, while Windows Server 2022 corresponds to Windows 11. In the end we provisioned a Windows 11 host, ran the build there, and pushed the image to production.

Because the US data center lacked a Windows 11-equivalent server build, we borrowed a server from the US production line, spun up a Windows 11 VM on it, ran CI/CD from there, and pushed the image to the US data center.

### Strapi Iterates Too Fast — Build Errors and Oversized Image

Our CMS is Strapi, but its rapid release cadence caused dependency resolution issues when using Yarn — certain plugins couldn't be recognized correctly. Switching from Yarn to npm resolved that.

As mentioned, we were using a borrowed Windows 11 VM in the US for CI/CD. Pushing images from the US office to the IDC production environment added noticeable latency even within California. To improve transfer speed, we switched to a lightweight Node base image (`node:18.17.0-alpine3.18`), compressing the image size from 3.8 GB down to 1.5 GB.

![image](https://blog.markkulab.net/content/markku/posts/germany-website-go-live-encountered-special-technical-problems/images/after-image-resize.png)

### Docker Container DNS Resolution Failure

After all environments were deployed, DNS queries from inside Docker containers started failing. The error looked like this:

```
Error fetch multi lang data, fallback to local file, environment: production, error: {"cause":{"errno":-3001,"code":"EAI_AGAIN","syscall":"getaddrinfo","hostname":"e645f404c07e0ac86.ibuypower.com"}}
```

Docker isolates the OS and network stack from the host — it does not inherit the host's DNS settings by default. We resolved the container DNS issue by explicitly adding DNS servers to the Docker daemon configuration:

```
  "dns": [
    "8.8.8.8",
    "1.1.1.1"
  ],
```

![Docker DNS setting](https://blog.markkulab.net/content/markku/posts/germany-website-go-live-encountered-special-technical-problems/images/docker-dns-setting.png)

### SQL Server Version Too Old — Works in Staging, Breaks in Production

```
Error: Client network socket disconnected before secure TLS connection was established 
```

On deployment day, after the application was deployed, TLS-related errors kept appearing. Comparing environments revealed that staging used SQL Server 2017, while the German production database was SQL Server 2016. SQL Server 2016 uses the deprecated TLS 1.0, which newer application stacks refuse to negotiate with. The fix was to upgrade the production database to SQL Server 2017 — adding three hours to the deployment window.

### Page Rendering Hanging

After the site went live, some pages occasionally hung. As you'd expect with Next.js server-side rendering, if any API call is slow or never returns, the page render stalls. After adding logs and analyzing the behavior, we traced the root cause to the multi-language API being called too frequently, which caused SharePoint to start throttling requests. The solution was to cache the Office 365 multi-language data in Redis. This not only resolved the throttling issue but also significantly improved page load speed and stability.

## Summary

Technical problems always look simple in retrospect, but diagnosing the root cause under pressure and still shipping on time is never easy. Just dealing with these DevOps issues alone had me working overtime for over two weeks. In the end, despite all the obstacles, the Germany site launched on July 1st. The key lesson: when running Windows Server environments, keep the OS and all components up to date to avoid this class of technical issues.

---

## About this article and its author

Originally published on [Mark Ku's Tech Notes](https://blog.markkulab.net/en/post/germany-website-go-live-encountered-special-technical-problems)

License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/) — when reusing or quoting, credit the author and link back to the original

### About the author

**[Mark Ku](https://blog.markkulab.net/en/author/mark-ku)** — Software Solution Provider

- 10+ years senior software engineer, now an AI Builder
- Focused on large-platform architecture — North-American e-commerce, AI SaaS subscription billing
- Combining AI Agents and automation to build evolvable product foundations

### Free tools built by the author

All of these are free to use:

- [Free PDF Sign Tool](https://blog.markkulab.net/en/tools/pdf-sign): Online PDF sign tool — draw, type, or upload a signature, then drag, resize, and download. Everything runs in your browser; nothing is uploaded.
- [VS Code Refactory](https://blog.markkulab.net/en/tools/refactory): Refactory is a VS Code refactoring extension: 34 actions plus a 37-rule code-smell inspection layer with a Code Health dashboard, across 18 languages, backed by 534 tests. It learns your repo's conventions: where interfaces live, where DI is registered, whether 'use client' belongs. It ranks files by git churn × complexity so you know what to fix first, and hands any smell to the Claude Code already on your machine. Free to use, and your source never leaves your computer.
- [DB-Kit Database Manager](https://blog.markkulab.net/en/tools/db-kit): DB-Kit is a lightweight, cross-platform database manager built with Tauri + Rust + React. Manage MySQL, MariaDB, PostgreSQL, SQL Server, Oracle, SQLite, MongoDB, Redis, Kafka, Elasticsearch and RabbitMQ from one consistent interface: passwords encrypted in the OS keychain, SSH tunnels, full CRUD, a visual query builder, stacked multi-statement result sets, cross-connection data transfer and compare/sync, Excel / CSV import & export, visualized execution plans, ER diagrams, scheduled backups, SQL stress testing with p50–p99 latency percentiles, a 15-rule SQL review engine, Kafka message browsing with monitoring & alerts, a bilingual UI (Traditional Chinese / English), a built-in AI assistant (natural-language SQL, AI review and tuning advice) and the dbk CLI. Free and open source (MIT), with installers for Windows, macOS and Linux.
- [VS Code Super Mermaid](https://blog.markkulab.net/en/tools/super-mermaid): Super Mermaid is a VS Code extension for beautiful Mermaid diagrams out of the box: auto-colored live preview, mouse pan & zoom, high-res PNG / SVG export, 21 templates and multiple themes. Free and open source (MIT).
- [React Super Mermaid](https://blog.markkulab.net/en/tools/react-super-mermaid): react-super-mermaid is an open-source React component library: render beautiful Mermaid diagrams with a single <MermaidViewer>, with built-in colorful / sketch themes, pan & zoom, in-diagram search, and high-res SVG / PNG export. Lightweight, SSR-safe, fully typed. Free and open source (MIT).
- [Jira / Confluence Super Mermaid](https://blog.markkulab.net/en/tools/jira-super-mermaid): An Atlassian Forge app: write Mermaid syntax directly inside a Jira issue or a Confluence page and get flowcharts, sequence diagrams, state machines and Gantt charts. 11 diagram types, SVG / PNG export, light and dark themes, full CJK support. Runs on Atlassian: your diagrams live in your own site and the app calls no third-party service. Free, coming soon to the Atlassian Marketplace.
- [Mermaid Live Preview](https://blog.markkulab.net/en/tools/mermaid-preview): Write Mermaid in your browser, see it render instantly, and share the whole diagram as a single link. No sign-up, nothing uploaded to a server, and mermaid.live share links work as-is.
- [React Intl Phone Number](https://blog.markkulab.net/en/tools/react-intl-phone-number): react-intl-phone-number is an open-source React component: framework-agnostic and antd-free, with E.164 in/out, a searchable flag / country-code dropdown, configurable validation levels (strict / mobile-strict / loose), themeable CSS, and i18n — phone logic powered by google-libphonenumber. Lightweight and fully typed. Free and open source (MIT).
- [Uptime Kuma Cluster](https://blog.markkulab.net/en/tools/uptime-kuma-cluster): Turn single-node Uptime Kuma into a highly available cluster: OpenResty + Lua smart load balancing, shared MariaDB state, health checks and automatic failover, plus cluster-management REST APIs. One Docker Compose command to start. Free and open source (MIT).
- [Special Education](https://blog.markkulab.net/en/education): Learning materials crafted for special education students

### Daily podcasts

- [Mark's Tech Insights — Daily AI News](https://blog.markkulab.net/en/category/tech-news): Daily curated AI and tech trends. Catch the latest developments via audio summaries — covering AI applications, software architecture, DevOps, and engineering practice. — RSS: https://blog.markkulab.net/feed.xml
- [AI股市蝦聊](https://blog.markkulab.net/en/category/ai-stock-chat): Every trading day, an AI-analyzed take on the Taiwan stock market, delivered as a two-host conversation covering the session and the next-day outlook. — RSS: https://blog.markkulab.net/ai-stock-chat/feed.xml
- [開源好物週報](https://blog.markkulab.net/en/category/open-source-weekly): A weekly two-host pick of free open-source tools surfaced from real Hacker News, GitHub, and Reddit buzz — what pain they solve and the fastest way to get started. — RSS: https://blog.markkulab.net/open-source-weekly/feed.xml

### Newsletter

[Subscribe to the newsletter](https://blog.markkulab.net/en/subscribe) — Be the first to know about new posts. No spam, unsubscribe anytime.