From 647630ff19edafc9584a6aefabac573dd062e39c Mon Sep 17 00:00:00 2001
From: twothatit <s.lustenberger@x26.ch>
Date: Sun, 8 Feb 2026 22:45:36 +0100
Subject: [PATCH] Fix LE cert creation: use empty meta for NPM API
 compatibility

NPM's certificate creation endpoint rejects letsencrypt_agree and
letsencrypt_email in the meta field (schema validation error). The
LE email is configured globally in NPM settings. Empty meta works.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---
 app/services/npm_service.py | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/app/services/npm_service.py b/app/services/npm_service.py
index 6c390d4..f32ab42 100644
--- a/app/services/npm_service.py
+++ b/app/services/npm_service.py
@@ -343,10 +343,7 @@ async def _request_ssl(
     ssl_payload = {
         "domain_names": [domain],
         "provider": "letsencrypt",
-        "meta": {
-            "letsencrypt_agree": True,
-            "letsencrypt_email": admin_email,
-        },
+        "meta": {},
     }
     try:
         logger.info("Requesting Let's Encrypt certificate for %s (email: %s) ...", domain, admin_email)