From 2768c3a33624fb6cc92f3876b072fb9cdba48614 Mon Sep 17 00:00:00 2001
From: Girish Ramakrishnan <girish@cloudron.io>
Date: Mon, 23 May 2016 09:48:17 -0700
Subject: [PATCH] acme: configure prod based on caas or acme

---
 src/certificates.js | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/certificates.js b/src/certificates.js
index afe143da2..833e12db3 100644
--- a/src/certificates.js
+++ b/src/certificates.js
@@ -69,7 +69,8 @@ function getApi(app, callback) {
         var api = !app.altDomain && tlsConfig.provider === 'caas' ? caas : acme;
 
         var options = { };
-        options.prod = tlsConfig.provider.match(/.*-prod/) !== null;
+        // used by acme backend to determine the LE origin.
+        options.prod = (api === caas) ? !config.isDev() : tlsConfig.provider.match(/.*-prod/) !== null;
 
         // registering user with an email requires A or MX record (https://github.com/letsencrypt/boulder/issues/1197)
         // we cannot use admin@fqdn because the user might not have set it up.