Internal error in install proxy 2 как исправить

4/7/2020] [6:55:06 PM] [Nginx    ] › ℹ  info      Reloading Nginx,
[4/7/2020] [6:55:07 PM] [Express  ] › ⚠  warning   Command failed: /usr/bin/certbot certonly --non-interactive --config "/etc/letsencrypt.ini" --cert-name "npm-2" --agree-tos --email "example@email.com" --preferred-challenges "dns,http" --webroot --domains "unifi.ophiuchus.fr" ,
Saving debug log to /var/log/letsencrypt/letsencrypt.log,
Plugins selected: Authenticator webroot, Installer None,
Obtaining a new certificate,
Performing the following challenges:,
http-01 challenge for unifi.ophiuchus.fr,
Using the webroot path /data/letsencrypt-acme-challenge for all unmatched domains.,
Waiting for verification...,
Challenge failed for domain unifi.ophiuchus.fr,
http-01 challenge for unifi.ophiuchus.fr,
Cleaning up challenges,
Some challenges have failed.,
,
[4/7/2020] [7:03:09 PM] [Nginx    ] › ℹ  info      Reloading Nginx,
[4/7/2020] [7:03:24 PM] [Nginx    ] › ℹ  info      Reloading Nginx,
[4/7/2020] [7:03:32 PM] [Nginx    ] › ℹ  info      Reloading Nginx,
[4/7/2020] [7:03:42 PM] [SSL      ] › ℹ  info      Renewing Let'sEncrypt certificates for Cert #2: unifi.ophiuchus.fr,
[4/7/2020] [7:03:43 PM] [Express  ] › ⚠  warning   Command failed: /usr/bin/certbot renew --non-interactive --config "/etc/letsencrypt.ini" --cert-name "npm-2" --preferred-challenges "dns,http" --disable-hook-validation ,
Saving debug log to /var/log/letsencrypt/letsencrypt.log,
No certificate found with name npm-2 (expected /etc/letsencrypt/renewal/npm-2.conf).,
,
[4/7/2020] [7:03:46 PM] [SSL      ] › ℹ  info      Renewing Let'sEncrypt certificates for Cert #1: jeedom.ophiuchus.fr,
[4/7/2020] [7:03:48 PM] [Express  ] › ⚠  warning   Command failed: /usr/bin/certbot renew --non-interactive --config "/etc/letsencrypt.ini" --cert-name "npm-1" --preferred-challenges "dns,http" --disable-hook-validation ,
Saving debug log to /var/log/letsencrypt/letsencrypt.log,
No certificate found with name npm-1 (expected /etc/letsencrypt/renewal/npm-1.conf).,
,
[4/7/2020] [7:05:41 PM] [SSL      ] › ℹ  info      Renewing Let'sEncrypt certificates for Cert #1: jeedom.ophiuchus.fr,
[4/7/2020] [7:05:43 PM] [Express  ] › ⚠  warning   Command failed: /usr/bin/certbot renew --non-interactive --config "/etc/letsencrypt.ini" --cert-name "npm-1" --preferred-challenges "dns,http" --disable-hook-validation ,
Saving debug log to /var/log/letsencrypt/letsencrypt.log,
No certificate found with name npm-1 (expected /etc/letsencrypt/renewal/npm-1.conf).,
,
Connection Error: Error: read ECONNRESET,
[4/7/2020] [7:22:47 PM] [SSL      ] › ℹ  info      Renewing Let'sEncrypt certificates for Cert #1: jeedom.ophiuchus.fr,
[4/7/2020] [7:22:48 PM] [Express  ] › ⚠  warning   Command failed: /usr/bin/certbot renew --non-interactive --config "/etc/letsencrypt.ini" --cert-name "npm-1" --preferred-challenges "dns,http" --disable-hook-validation ,
Saving debug log to /var/log/letsencrypt/letsencrypt.log,
No certificate found with name npm-1 (expected /etc/letsencrypt/renewal/npm-1.conf).,
,
[4/7/2020] [7:23:19 PM] [Nginx    ] › ℹ  info      Reloading Nginx,
[4/7/2020] [7:23:23 PM] [Nginx    ] › ℹ  info      Reloading Nginx,
[4/7/2020] [7:23:53 PM] [Nginx    ] › ℹ  info      Reloading Nginx,
[4/7/2020] [7:24:08 PM] [SSL      ] › ℹ  info      Renewing Let'sEncrypt certificates for Cert #1: jeedom.ophiuchus.fr,
[4/7/2020] [7:24:09 PM] [Express  ] › ⚠  warning   Command failed: /usr/bin/certbot renew --non-interactive --config "/etc/letsencrypt.ini" --cert-name "npm-1" --preferred-challenges "dns,http" --disable-hook-validation ,
Saving debug log to /var/log/letsencrypt/letsencrypt.log,
No certificate found with name npm-1 (expected /etc/letsencrypt/renewal/npm-1.conf).,
,
[4/7/2020] [7:24:14 PM] [SSL      ] › ℹ  info      Revoking Let'sEncrypt certificates for Cert #1: jeedom.ophiuchus.fr,
[4/7/2020] [7:24:22 PM] [SSL      ] › ℹ  info      Revoking Let'sEncrypt certificates for Cert #2: unifi.ophiuchus.fr,
[4/7/2020] [7:25:17 PM] [Nginx    ] › ℹ  info      Reloading Nginx,
[4/7/2020] [7:25:51 PM] [Nginx    ] › ℹ  info      Reloading Nginx,
[4/7/2020] [7:25:51 PM] [SSL      ] › ℹ  info      Requesting Let'sEncrypt certificates for Cert #3: unifi.ophiuchus.fr,
[4/7/2020] [7:25:56 PM] [Nginx    ] › ℹ  info      Reloading Nginx,
[4/7/2020] [7:25:56 PM] [Express  ] › ⚠  warning   Command failed: /usr/bin/certbot certonly --non-interactive --config "/etc/letsencrypt.ini" --cert-name "npm-3" --agree-tos --email "example@email.com" --preferred-challenges "dns,http" --webroot --domains "unifi.ophiuchus.fr" ,
Saving debug log to /var/log/letsencrypt/letsencrypt.log,
Plugins selected: Authenticator webroot, Installer None,
Obtaining a new certificate,
Performing the following challenges:,
http-01 challenge for unifi.ophiuchus.fr,
Using the webroot path /data/letsencrypt-acme-challenge for all unmatched domains.,
Waiting for verification...,
Challenge failed for domain unifi.ophiuchus.fr,
http-01 challenge for unifi.ophiuchus.fr,
Cleaning up challenges,
Some challenges have failed.,
,
[4/7/2020] [7:26:25 PM] [Access   ] › ℹ  info      Building Access file #1 for: ophiuchus,
[4/7/2020] [7:26:25 PM] [Access   ] › ℹ  info      Adding: rodolphe,
[4/7/2020] [7:26:26 PM] [Access   ] › ✔  success   Built Access file #1 for: ophiuchus,
[4/7/2020] [7:33:08 PM] [Nginx    ] › ℹ  info      Reloading Nginx,
[4/7/2020] [7:33:08 PM] [SSL      ] › ℹ  info      Requesting Let'sEncrypt certificates for Cert #4: jeedom.ophiuchus.fr,
[4/7/2020] [7:33:13 PM] [Nginx    ] › ℹ  info      Reloading Nginx,
[4/7/2020] [7:33:13 PM] [Express  ] › ⚠  warning   Command failed: /usr/bin/certbot certonly --non-interactive --config "/etc/letsencrypt.ini" --cert-name "npm-4" --agree-tos --email "example@email.com" --preferred-challenges "dns,http" --webroot --domains "jeedom.ophiuchus.fr" ,
Saving debug log to /var/log/letsencrypt/letsencrypt.log,
Plugins selected: Authenticator webroot, Installer None,
Obtaining a new certificate,
Performing the following challenges:,
http-01 challenge for jeedom.ophiuchus.fr,
Using the webroot path /data/letsencrypt-acme-challenge for all unmatched domains.,
Waiting for verification...,
Challenge failed for domain jeedom.ophiuchus.fr,
http-01 challenge for jeedom.ophiuchus.fr,
Cleaning up challenges,
Some challenges have failed.,
,
[4/7/2020] [7:33:15 PM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...,
[4/7/2020] [7:33:17 PM] [Nginx    ] › ℹ  info      Reloading Nginx,
[4/7/2020] [7:33:17 PM] [SSL      ] › ℹ  info      Renew Complete,
[4/7/2020] [7:33:17 PM] [SSL      ] › ✖  error     Certificate is not valid (Command failed: openssl x509 -in /etc/letsencrypt/live/npm-3/fullchain.pem -subject -noout,
Can't open /etc/letsencrypt/live/npm-3/fullchain.pem for reading, No such file or directory,
140650706484552:error:02001002:system library:fopen:No such file or directory:crypto/bio/bss_file.c:69:fopen('/etc/letsencrypt/live/npm-3/fullchain.pem','r'),
140650706484552:error:2006D080:BIO routines:BIO_new_file:no such file:crypto/bio/bss_file.c:76:,
unable to load certificate,
),
[4/7/2020] [7:33:17 PM] [SSL      ] › ✖  error     Certificate is not valid (Command failed: openssl x509 -in /etc/letsencrypt/live/npm-4/fullchain.pem -subject -noout,
Can't open /etc/letsencrypt/live/npm-4/fullchain.pem for reading, No such file or directory,
140360297569608:error:02001002:system library:fopen:No such file or directory:crypto/bio/bss_file.c:69:fopen('/etc/letsencrypt/live/npm-4/fullchain.pem','r'),
140360297569608:error:2006D080:BIO routines:BIO_new_file:no such file:crypto/bio/bss_file.c:76:,
unable to load certificate,
),
[4/7/2020] [7:33:41 PM] [Nginx    ] › ℹ  info      Reloading Nginx,
  • Remove From My Forums
  • Question

  • Deployed CfgMgr CB 1602 including Hotfix 3155482. (Standalone Site) Primary Site Server is installed in Forest A with two MP’s and we want to enable IBCM using a separate Forest B (DMZ) using site server connection account and MP Connection
    Account. Certificate is deployed on the Site Server that is going to be MP. Used the PowerShell Script Install-ConfigMgrPrereqsGUI_1.4.2 to install all Windows Features required for MP and DP. Site Server Role DP is running without any errors on
    the site server in Forest B (DMZ)

    When I add the role MP to the server in Forest B (DMZ) everything is going well until the installation of Notification Server (SMSBGB). This component fails to install with error message BGB http proxy — Internal Error 25001. 80070057. BITS component
    are installed including IIS BITS Server extensions. WMI Namespace CCM is not visible using WBEMtest.

    Also tried installing MP using HTTP (test) fails. Installing MP role on a fresh server fails also. Ports between MP and Site Server (RPC Endpoint mapper 135, RPC (dynamic) and SMB 445 are open.

    Any suggestions are welcome.
    Best regards
    Tom


    Tom Klaver

Уровень сложности
Простой

Время на прочтение
3 мин

Количество просмотров 2.5K

Одна из самых популярных и при этом не всегда логирующаяся ошибка apache2 — «Internal Server Error». В этой статье разберу возможные причины и решения из интернета и личного опыта. Иногда эта ошибка весьма не очевидна.

Все ситуации описаны для операционной системы Ubuntu Linux 22.10.

Ну и, конечно, первое, что вы должны сделать это попробовать перезапустить службу.

sudo systemctl restart apache2

Если это не помогло, то двигаемся дальше.

1. Конфигурация

1.1. Ошибка конфигурации веб-приложения

Прежде всего рекомендую сделать запрос к вашему сайту локально, прямо с сервера.

curl localhost:80

Если вы не видите «Internal Server Error», а видите html страницу, то 99% проблема в файлах конфигурации и настройках доступа.

Проверьте файл: /etc/apache2/sites-available/your_app.conf
где your_app.conf — название вашего файла конфирурации, либо стандартный conf файл — «000-default.conf»

Как он выглядит:

/etc/apache2/sites-available/your_app.conf

/etc/apache2/sites-available/your_app.conf

Строка «Require ip 127.0.0.1» говорит, о том, что разрешено подключение только с локального хоста.

Решение: замените строку «Require ip 127.0.0.1» на «Require all granted»
Так же «Require all granted» должна быть в /etc/apache2/apache2.conf

/etc/apache2/apache2.conf

/etc/apache2/apache2.conf

1.2. Старый конфигурационный файл

Возможно, создавая новый файл конфигурации веб-приложения он не был выбрал или включен.

Решение:
1. Выключаем стандартный файл конфигурации
2. Включаем свой
3. Перезагружаем apache2

a2dissite 000-default.conf 
a2ensite your_app.conf 
systemctl restart apache2 

2. Права доступа

Проблема возникает тогда, когда права файлов вашего проекта не соответствуют ожидаемым.

2.1. Владелец файлов

Файлы вашего проекта не принадлежат пользователю www-data.

Папка проекта (your_project) не принадлежит пользователю www-data

Папка проекта (your_project) не принадлежит пользователю www-data

Решение:

sudo chown -R www-data:www-data your_project/

P.S. Случается так, что apache2 при установке не создаёт пользователя www-data, в этом нет ничего страшного, можно обойтись и без его создания. Права отлично функционируют и сайт работает.

2.2. Права файлов

Ошибка так же может возникать когда владелец установлен верно, но всё равно не имеет доступа к файлам из-за настроек прав доступа.

Решение:

sudo chmod -R 755 your_project/

2.3. Веб-приложение работает с файлами системы

«Internal Server Error» возникает, когда ваше веб-приложение взаимодействует с файлами системы у которых нет прав на исполнение. Звучит также странно как есть на самом деле, почему я не могу читать файлы у которых есть право на чтение? До сих пор не понимаю. Но проблема эта решается, если выдать файлам право на исполнение.

Решение:

sudo chmod -R 777 your_project/files/

3. Ошибка в коде вашего веб-приложения

Также частая ситуация, когда apache2 настроен правильно, но всё равно возникает эта нелогирующаяся ошибка «Internal Server Error», тогда следует проследить отрабатывает ли вообще ваше приложение.

Например, если оно не может подключиться к базе данных, то вы, всё равно, увидите «Internal Server Error». Стоит проверить верный ли пароль и есть ли доступ к базе данных. А возможно, что просто веб-приложение запустилось раньше базы данных, в этом случае поможет простая перезагрузка apache2.

Если ваше приложение взаимодействует с внешним ресурсом, и он оказывается не доступен или привышен лимит ожидания ответа, то вы снова увидите «Internal Server Error».

4. Переустановка apache2

Если вам не помогли все вышеуказаные действия, то возможно проблема с самим apache2, тогда нужно попробовать его переустановить:

sudo apt update
sudo apt install --reinstall apache2

Если вы не решили свою проблему, то вот еще возможные причины и направления для дальнейшего поиска.

  • Ошибка синтаксиса .htaccess. Если вы используете Apache в качестве веб-сервера, то, скорее всего, у вас есть .htaccess файл в корневом каталоге вашего сайта. Неверный синтаксис или несуществующая директива модуля может привести к ошибке 500.

  • Проблемы с плагинами и темами. Если вы используете WordPress или аналогичную CMS, ошибка 500 может появиться после обновления или изменения плагина или темы.

  • Проблемы с сервером. Поврежденная файловая система или исчерпанная память могут привести к ошибке 500.

  • Модули Node.js. Если у вас есть сайт на основе Node.js, обновление модулей может вызвать внутреннюю ошибку сервера 500.

  • Довольно часто вредоносный код, внедряемый на ваш сайт, приводит к ошибке 500.

  • Несовместимый модуль. Загрузка несовместимого модуля PHP или Apache вызывает ошибку 500.

P.S. Надеюсь, кому-то помог. Удачи.

Hi

I have setup Nginx proxy manager on docker which is running on ubuntu 20.04 server. The ubuntu server is a vm running on my esxi host.

When i try to create a lets encrypt cert for one of my proxy hosts it throws an «internal error» message.

My setup:

  • Domain purchased from godaddy eg — mydomain.co.uk

  • Go daddy name servers pointing to Cloudflare

  • A record pointing to my external ip which is updated using the cloudflare DDNS container

  • Cloudflare SSL set to Full(Strict) — created an origin cert and added this to NPM as a custom cert

  • ports 80 and 443 forwarded to the ubuntu vm which runs docker

1 NUC 9 running ESXi 7.02

  • 1 ubuntu vm

    • Plex

    • Docker

      • Sabnzbd

      • sonarr

      • radarr

      • cloudflareDDNS

      • Nginx proxy manager

  • Windows Server 2019 Domain controller

I get the following errors in the logs on the NPM (nginx proxy manager) container

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -,
[7/5/2021] [9:15:59 AM] [Nginx    ] › ℹ  info      Reloading Nginx,
[7/5/2021] [9:19:53 AM] [Nginx    ] › ℹ  info      Reloading Nginx,
[7/5/2021] [9:21:41 AM] [Nginx    ] › ℹ  info      Reloading Nginx,
[7/5/2021] [9:21:41 AM] [SSL      ] › ℹ  info      Requesting Let'sEncrypt certificates for Cert #17: portainer.mydomain.co.uk,
[7/5/2021] [9:21:44 AM] [Nginx    ] › ℹ  info      Reloading Nginx,
[7/5/2021] [9:21:44 AM] [Express  ] › ⚠  warning   Command failed: certbot certonly --non-interactive --config "/etc/letsencrypt.ini" --cert-name "npm-17" --agree-tos --email "myemailaddress.co.uk" --preferred-challenges "dns,http" --domains "portainer.mydomain.co.uk" ,
Saving debug log to /var/log/letsencrypt/letsencrypt.log,
Some challenges have failed.,
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.,

When i go into the /var/log/letsencrypt/letsencrypt.log on the NPM container i see these logs.

2021-07-05 09:21:42,287:DEBUG:certbot._internal.main:certbot version: 1.16.0
2021-07-05 09:21:42,287:DEBUG:certbot._internal.main:Location of certbot entry point: /opt/certbot/bin/certbot
2021-07-05 09:21:42,287:DEBUG:certbot._internal.main:Arguments: ['--non-interactive', '--config', '/etc/letsencrypt.ini', '--cert-name', 'npm-17', '--agree-tos', '--email', 'myemail.co.uk', '--preferred-challenges', 'dns,http', '--domains', 'portainer.mydomanin.co.uk']
2021-07-05 09:21:42,287:DEBUG:certbot._internal.main:Discovered plugins: PluginsRegistry(PluginEntryPoint#manual,PluginEntryPoint#null,PluginEntryPoint#standalone,PluginEntryPoint#webroot)
2021-07-05 09:21:42,297:DEBUG:certbot._internal.log:Root logging level set at 30
2021-07-05 09:21:42,297:DEBUG:certbot._internal.plugins.selection:Requested authenticator webroot and installer None
2021-07-05 09:21:42,299:DEBUG:certbot._internal.plugins.selection:Single candidate plugin: * webroot
Description: Place files in webroot directory
Interfaces: IAuthenticator, IPlugin
Entry point: webroot = certbot._internal.plugins.webroot:Authenticator
Initialized: <certbot._internal.plugins.webroot.Authenticator object at 0x7f3b3eebb3c8> Prep: True 2021-07-05 09:21:42,299:DEBUG:certbot._internal.plugins.selection:Selected authenticator
<certbot._internal.plugins.webroot.Authenticator object at 0x7f3b3eebb3c8> and installer None 2021-07-05 09:21:42,299:INFO:certbot._internal.plugins.selection:Plugins selected: Authenticator webroot, Installer None 2021-07-05 09:21:42,308:DEBUG:certbot._internal.main:Picked account:
<Account(RegistrationResource(body=Registration(key=None, contact=(), agreement=None, status=None, terms_of_service_agreed=None, only_return_existing=None, external_account_binding=None), uri='https://acme-v02.api.letsencrypt.org/acme/acct/129228927' , new_authzr_uri=None, terms_of_service=None), 13997c237baa938606b3bd8115a8a164, Meta(creation_dt=datetime.datetime(2021, 7, 3, 21, 58, 2, tzinfo=
<UTC>), creation_host='aba0e9a553e2', register_to_eff=None))>
2021-07-05 09:21:42,309:DEBUG:acme.client:Sending GET request to https://acme-v02.api.letsencrypt.org/directory.
2021-07-05 09:21:42,310:DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org:443
2021-07-05 09:21:42,884:DEBUG:urllib3.connectionpool:https://acme-v02.api.letsencrypt.org:443 "GET /directory HTTP/1.1" 200 658
2021-07-05 09:21:42,884:DEBUG:acme.client:Received response:
HTTP 200
Server: nginx
Date: Mon, 05 Jul 2021 09:21:42 GMT
Content-Type: application/json
Content-Length: 658
Connection: keep-alive
Cache-Control: public, max-age=0, no-cache
X-Frame-Options: DENY
Strict-Transport-Security: max-age=604800

{
  "keyChange": "https://acme-v02.api.letsencrypt.org/acme/key-change",
  "lnUGLQZsPUU": "https://community.letsencrypt.org/t/adding-random-entries-to-the-directory/33417",
  "meta": {
    "caaIdentities": [
      "letsencrypt.org"
    ],
    "termsOfService": "https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf",
    "website": "https://letsencrypt.org"
  },
  "newAccount": "https://acme-v02.api.letsencrypt.org/acme/new-acct",
  "newNonce": "https://acme-v02.api.letsencrypt.org/acme/new-nonce",
  "newOrder": "https://acme-v02.api.letsencrypt.org/acme/new-order",
  "revokeCert": "https://acme-v02.api.letsencrypt.org/acme/revoke-cert"
}
2021-07-05 09:21:42,885:DEBUG:certbot.display.util:Notifying user: Requesting a certificate for portainer.mydomain.co.uk
2021-07-05 09:21:43,037:DEBUG:certbot.crypto_util:Generating RSA key (2048 bits): /etc/letsencrypt/keys/0012_key-certbot.pem
2021-07-05 09:21:43,039:DEBUG:certbot.crypto_util:Creating CSR: /etc/letsencrypt/csr/0012_csr-certbot.pem
2021-07-05 09:21:43,039:DEBUG:acme.client:Requesting fresh nonce
2021-07-05 09:21:43,039:DEBUG:acme.client:Sending HEAD request to https://acme-v02.api.letsencrypt.org/acme/new-nonce.
2021-07-05 09:21:43,176:DEBUG:urllib3.connectionpool:https://acme-v02.api.letsencrypt.org:443 "HEAD /acme/new-nonce HTTP/1.1" 200 0
2021-07-05 09:21:43,177:DEBUG:acme.client:Received response:
HTTP 200
Server: nginx
Date: Mon, 05 Jul 2021 09:21:43 GMT
Connection: keep-alive
Cache-Control: public, max-age=0, no-cache
Link: <https: acme-v02.api.letsencrypt.orgdirectory>;rel="index" Replay-Nonce: 0002NfR_sdBNBEy2G2mxHgyaI5i6EjqYa-f1fjqiCaImZuU X-Frame-Options: DENY Strict-Transport-Security: max-age=604800 2021-07-05 09:21:43,177:DEBUG:acme.client:Storing nonce: 0002NfR_sdBNBEy2G2mxHgyaI5i6EjqYa-f1fjqiCaImZuU 2021-07-05 09:21:43,177:DEBUG:acme.client:JWS payload: b'{n"identifiers" : [n {n"type" :"dns" ,n"value" :"portainer.mydomain.co.uk" n }n ]n}' 2021-07-05 09:21:43,178:DEBUG:acme.client:Sending POST request to https: acme-v02.api.letsencrypt.org acme new-order: {"protected" :"eyJhbGciOiAiUlMyNTYiLCAia2lkIjogImh0dHBzOi8vYWNtZS12MDIuYXBpLmxldHNlbmNyeXB0Lm9yZy9hY21lL2FjY3QvMTI5MjI4OTI3IiwgIm5vbmNlIjogIjAwMDJOZlJfc2RCTkJFeTJHMm14SGd5YUk1aTZFanFZYS1mMWZqcWlDYUltWnVVIiwgInVybCI6ICJodHRwczovL2FjbWUtdjAyLmFwaS5sZXRzZW5jcnlwdC5vcmcvYWNtZS9uZXctb3JkZXIifQ" ,"signature" :"JXtuleY2sqKgwLQYu1xelN-NpDFebmVP_m6OFMJ2Fhb73nyr9Nd0OgmFrKltB9kddZVOBoFhk1K8wc6eyaCB847uNAakCBgPOiB8QbKQDy98KBPl6JcgnA-t0kUB5uoA6X0de-EGZnYus8qq0TgW6Shb-cNxuWykDbLeEgJFwAVURxCdZNVyJ56ZQit1pLFhj4RebvtfHYhQt3S0qXc5XIk_HohjX9mrsLeVk9Xstk8vbwPV5LvUPtz_Q_DONh8oJgRjq4ZvpdU-NU_Q7sWHG-wNwwdJ2EUDFc5eZrGF1m0WcuLzCaVKkET9BH_IRVlgHEKsw0W2p07efGF_U7IMTQ" ,"payload" :"ewogICJpZGVudGlmaWVycyI6IFsKICAgIHsKICAgICAgInR5cGUiOiAiZG5zIiwKICAgICAgInZhbHVlIjogInBvcnRhaW5lci5zYWpqYW5zb2x1dGlvbnMuY28udWsiCiAgICB9CiAgXQp9" } 2021-07-05 09:21:43,351:DEBUG:urllib3.connectionpool:https: acme-v02.api.letsencrypt.org:443"POST /acme/new-order HTTP/1.1" 201 354 2021-07-05 09:21:43,351:DEBUG:acme.client:Received response: HTTP 201 Server: nginx Date: Mon, 05 Jul 2021 09:21:43 GMT Content-Type: application json Content-Length: 354 Connection: keep-alive Boulder-Requester: 129228927 Cache-Control: public, max-age=0, no-cache Link:
	<https: acme-v02.api.letsencrypt.org directory>;rel="index" Location: https: acme-v02.api.letsencrypt.org acme order 129228927 10861843866 Replay-Nonce: 0001L0f0o8zb0-DL7eHOnEY7bdgRWM1IfycZtlsoEmZg1aQ X-Frame-Options: DENY Strict-Transport-Security: max-age=604800 {"status" :"pending" ,"expires" :"2021-07-12T09:21:43Z" ,"identifiers" : [ {"type" :"dns" ,"value" :"portainer.mydomain.co.uk" } ],"authorizations" : ["https://acme-v02.api.letsencrypt.org/acme/authz-v3/14553634828" ],"finalize" :"https://acme-v02.api.letsencrypt.org/acme/finalize/129228927/10861843866" } 2021-07-05 09:21:43,351:DEBUG:acme.client:Storing nonce: 0001L0f0o8zb0-DL7eHOnEY7bdgRWM1IfycZtlsoEmZg1aQ 2021-07-05 09:21:43,351:DEBUG:acme.client:JWS payload: b'' 2021-07-05 09:21:43,352:DEBUG:acme.client:Sending POST request to https: acme-v02.api.letsencrypt.org acme authz-v3 14553634828: {"protected" :"eyJhbGciOiAiUlMyNTYiLCAia2lkIjogImh0dHBzOi8vYWNtZS12MDIuYXBpLmxldHNlbmNyeXB0Lm9yZy9hY21lL2FjY3QvMTI5MjI4OTI3IiwgIm5vbmNlIjogIjAwMDFMMGYwbzh6YjAtREw3ZUhPbkVZN2JkZ1JXTTFJZnljWnRsc29FbVpnMWFRIiwgInVybCI6ICJodHRwczovL2FjbWUtdjAyLmFwaS5sZXRzZW5jcnlwdC5vcmcvYWNtZS9hdXRoei12My8xNDU1MzYzNDgyOCJ9" ,"signature" :"vx3V0T0-h9-XQ6ha76NVLZSA6Hl3ZKdZRjXIEo6tsura6J3SbibwPHeSKBZxXpYBdvotC-NIuCpMBwfDatz3PatyQ4xhpa7smnayRiT81CIxtk3STXR7RHz63c4P6m0EVyipgCw_Aw-tU7o4o6KPJoAeybnHjvsxCgUATkZooKCbLmI-xkz8gR4c23txhMCdGrBa01d9P4uXTSk2HKJ510JeW9SXZH2FNjMU3RIjtyRr6Cigv5gyiA3WS1O02gJfb6OloG49jLVChzXFaou8_Ja65ttjTH7N3TYV_EMFSTx4f9O3sX4rgfsIzN0yjwIKNsDtGqkxmN4MbhnxtVrErA" ,"payload" :"" } 2021-07-05 09:21:43,493:DEBUG:urllib3.connectionpool:https: acme-v02.api.letsencrypt.org:443"POST /acme/authz-v3/14553634828 HTTP/1.1" 200 812 2021-07-05 09:21:43,493:DEBUG:acme.client:Received response: HTTP 200 Server: nginx Date: Mon, 05 Jul 2021 09:21:43 GMT Content-Type: application json Content-Length: 812 Connection: keep-alive Boulder-Requester: 129228927 Cache-Control: public, max-age=0, no-cache Link:
	<https: acme-v02.api.letsencrypt.org directory>;rel="index" Replay-Nonce: 0002tHSrzFwv0NzdsxEEJw46yk7Nb_M03ccLv8MLdeHaB5U X-Frame-Options: DENY Strict-Transport-Security: max-age=604800 {"identifier" : {"type" :"dns" ,"value" :"portainer.mydomain.co.uk" },"status" :"pending" ,"expires" :"2021-07-12T09:21:43Z" ,"challenges" : [ {"type" :"http-01" ,"status" :"pending" ,"url" :"https://acme-v02.api.letsencrypt.org/acme/chall-v3/14553634828/q5agHA" ,"token" :"xjwt0sAvlZow3m0hs19hIFuogOO9o_PvCdyh6xntdpg" }, {"type" :"dns-01" ,"status" :"pending" ,"url" :"https://acme-v02.api.letsencrypt.org/acme/chall-v3/14553634828/TDLZiA" ,"token" :"xjwt0sAvlZow3m0hs19hIFuogOO9o_PvCdyh6xntdpg" }, {"type" :"tls-alpn-01" ,"status" :"pending" ,"url" :"https://acme-v02.api.letsencrypt.org/acme/chall-v3/14553634828/u7xg3Q" ,"token" :"xjwt0sAvlZow3m0hs19hIFuogOO9o_PvCdyh6xntdpg" } ] } 2021-07-05 09:21:43,494:DEBUG:acme.client:Storing nonce: 0002tHSrzFwv0NzdsxEEJw46yk7Nb_M03ccLv8MLdeHaB5U 2021-07-05 09:21:43,494:INFO:certbot._internal.auth_handler:Performing the following challenges: 2021-07-05 09:21:43,494:INFO:certbot._internal.auth_handler:http-01 challenge for portainer.mydomain.co.uk 2021-07-05 09:21:43,494:INFO:certbot._internal.plugins.webroot:Using the webroot path data letsencrypt-acme-challenge for all unmatched domains. 2021-07-05 09:21:43,494:DEBUG:certbot._internal.plugins.webroot:Creating root challenges validation dir at data letsencrypt-acme-challenge .well-known acme-challenge 2021-07-05 09:21:43,495:DEBUG:certbot._internal.plugins.webroot:Attempting to save validation to data letsencrypt-acme-challenge .well-known acme-challenge xjwt0sAvlZow3m0hs19hIFuogOO9o_PvCdyh6xntdpg 2021-07-05 09:21:43,496:DEBUG:acme.client:JWS payload: b'{}' 2021-07-05 09:21:43,497:DEBUG:acme.client:Sending POST request to https: acme-v02.api.letsencrypt.org acme chall-v3 14553634828 q5agHA: {"protected" :"eyJhbGciOiAiUlMyNTYiLCAia2lkIjogImh0dHBzOi8vYWNtZS12MDIuYXBpLmxldHNlbmNyeXB0Lm9yZy9hY21lL2FjY3QvMTI5MjI4OTI3IiwgIm5vbmNlIjogIjAwMDJ0SFNyekZ3djBOemRzeEVFSnc0NnlrN05iX00wM2NjTHY4TUxkZUhhQjVVIiwgInVybCI6ICJodHRwczovL2FjbWUtdjAyLmFwaS5sZXRzZW5jcnlwdC5vcmcvYWNtZS9jaGFsbC12My8xNDU1MzYzNDgyOC9xNWFnSEEifQ" ,"signature" :"uma6GPuPJirPOUDpaMZrR7PAgTLHhpWXoMbqCerrSXOv022dDNaUTa5bzTCSMX3Rfu-18WrIBtWAHFW7N4qxZSMfXmJbfk-EgVdZF3w42dQeo1yAJgNED09WfdeLGZd4cYUqhRYSZn9au9lQ_g_URnrWN9QKuhdRFleNJHR2dG6ViXsIdE_GGdDiOH90vaYWTJkEqblxgYoCfbSee5Wv2nVRh7ALnUBLCEBo6iPaYAtBSce0Q_yzb2SpvgTKRjxrewvY7ZJqTY87Wp0S9dbRDe09MIFmna58zr3R7iwRjBmcwC6WMZVkAdgr0aU15fn-Woocom_IF7evmfWxnWM5oA" ,"payload" :"e30" } 2021-07-05 09:21:43,641:DEBUG:urllib3.connectionpool:https: acme-v02.api.letsencrypt.org:443"POST /acme/chall-v3/14553634828/q5agHA HTTP/1.1" 200 186 2021-07-05 09:21:43,641:DEBUG:acme.client:Received response: HTTP 200 Server: nginx Date: Mon, 05 Jul 2021 09:21:43 GMT Content-Type: application json Content-Length: 186 Connection: keep-alive Boulder-Requester: 129228927 Cache-Control: public, max-age=0, no-cache Link:
	<https: acme-v02.api.letsencrypt.org directory>;rel="index" ,
	<https: acme-v02.api.letsencrypt.org acme authz-v3 14553634828>;rel="up" Location: https: acme-v02.api.letsencrypt.org acme chall-v3 14553634828 q5agHA Replay-Nonce: 0002uo0Af5TJgPg0e6yj-nYpzFgQBf4ZWbNBwf6h9Oh24JI X-Frame-Options: DENY Strict-Transport-Security: max-age=604800 {"type" :"http-01" ,"status" :"pending" ,"url" :"https://acme-v02.api.letsencrypt.org/acme/chall-v3/14553634828/q5agHA" ,"token" :"xjwt0sAvlZow3m0hs19hIFuogOO9o_PvCdyh6xntdpg" } 2021-07-05 09:21:43,641:DEBUG:acme.client:Storing nonce: 0002uo0Af5TJgPg0e6yj-nYpzFgQBf4ZWbNBwf6h9Oh24JI 2021-07-05 09:21:43,641:INFO:certbot._internal.auth_handler:Waiting for verification... 2021-07-05 09:21:44,643:DEBUG:acme.client:JWS payload: b'' 2021-07-05 09:21:44,644:DEBUG:acme.client:Sending POST request to https: acme-v02.api.letsencrypt.org acme authz-v3 14553634828: {"protected" :"eyJhbGciOiAiUlMyNTYiLCAia2lkIjogImh0dHBzOi8vYWNtZS12MDIuYXBpLmxldHNlbmNyeXB0Lm9yZy9hY21lL2FjY3QvMTI5MjI4OTI3IiwgIm5vbmNlIjogIjAwMDJ1bzBBZjVUSmdQZzBlNnlqLW5ZcHpGZ1FCZjRaV2JOQndmNmg5T2gyNEpJIiwgInVybCI6ICJodHRwczovL2FjbWUtdjAyLmFwaS5sZXRzZW5jcnlwdC5vcmcvYWNtZS9hdXRoei12My8xNDU1MzYzNDgyOCJ9" ,"signature" :"gLAMuWWgCYapxUWlujiigZh0fZc6yzqIgtjnFK-0UXERkt-RZCjUWyVaz0D60lJ6YWj3-QM0gdrB7OjP_zUNAZV3Iv8gPCbX-F_0dvv3V_phT3t37WPKCMZ40FLSmDTnV5vUkFm_zvlADrvhD2iD0KhcFIsx00WTEXSul9Zpmyd98M8jOAlNtVvfzoHmiH93Myj8UyW4lKxB1GVWTLoZLvce5CKVgIHPTHyS7fNkAt7i0MtJZmoRHG_Ds7fTQ7yww6Gb9chkiKHlxMiaiLOQaIYf_Wmgf4oM8r5nRLUC8cxP_pdCkDudCAJz-xx3ZZ_1sMj_BnzNrleLXoU0AkqhfQ" ,"payload" :"" } 2021-07-05 09:21:44,787:DEBUG:urllib3.connectionpool:https: acme-v02.api.letsencrypt.org:443"POST /acme/authz-v3/14553634828 HTTP/1.1" 200 1903 2021-07-05 09:21:44,787:DEBUG:acme.client:Received response: HTTP 200 Server: nginx Date: Mon, 05 Jul 2021 09:21:44 GMT Content-Type: application json Content-Length: 1903 Connection: keep-alive Boulder-Requester: 129228927 Cache-Control: public, max-age=0, no-cache Link:
	<https: acme-v02.api.letsencrypt.org directory>;rel="index" Replay-Nonce: 00028AfZ9b3nRaCndCgotkEcjfssokheQm8HhX98j7wyHbM X-Frame-Options: DENY Strict-Transport-Security: max-age=604800 {"identifier" : {"type" :"dns" ,"value" :"portainer.mydomain.co.uk" },"status" :"invalid" ,"expires" :"2021-07-12T09:21:43Z" ,"challenges" : [ {"type" :"http-01" ,"status" :"invalid" ,"error" : {"type" :"urn:ietf:params:acme:error:unauthorized" ,"detail" :"Invalid response from https://portainer.mydomain.co.uk/.well-known/acme-challenge/xjwt0sAvlZow3m0hs19hIFuogOO9o_PvCdyh6xntdpg [2606:4700:3037::6815:3efc]: " u003c!DOCTYPE htmlu003e\nu003c!--[if lt IE 7]u003e u003chtml class=\"no-js ie6 oldie\" lang=\"en-US\" u003e u003c![endif]--u003e\nu003c!--[if IE 7]u003e u003chtml class=\"no-js " ","status" : 403 },"url" :"https://acme-v02.api.letsencrypt.org/acme/chall-v3/14553634828/q5agHA" ,"token" :"xjwt0sAvlZow3m0hs19hIFuogOO9o_PvCdyh6xntdpg" ,"validationRecord" : [ {"url" :"http://portainer.mydomain.co.uk/.well-known/acme-challenge/xjwt0sAvlZow3m0hs19hIFuogOO9o_PvCdyh6xntdpg" ,"hostname" :"portainer.mydomain.co.uk" ,"port" :"80" ,"addressesResolved" : ["172.67.141.61" ,"104.21.62.252" ,"2606:4700:3035::ac43:8d3d" ,"2606:4700:3037::6815:3efc" ],"addressUsed" :"2606:4700:3035::ac43:8d3d" }, {"url" :"https://portainer.mydomain.co.uk/.well-known/acme-challenge/xjwt0sAvlZow3m0hs19hIFuogOO9o_PvCdyh6xntdpg" ,"hostname" :"portainer.mydomain.co.uk" ,"port" :"443" ,"addressesResolved" : ["172.67.141.61" ,"104.21.62.252" ,"2606:4700:3037::6815:3efc" ,"2606:4700:3035::ac43:8d3d" ],"addressUsed" :"2606:4700:3037::6815:3efc" } ],"validated" :"2021-07-05T09:21:43Z" } ] } 2021-07-05 09:21:44,787:DEBUG:acme.client:Storing nonce: 00028AfZ9b3nRaCndCgotkEcjfssokheQm8HhX98j7wyHbM 2021-07-05 09:21:44,788:INFO:certbot._internal.auth_handler:Challenge failed for domain portainer.mydomain.co.uk 2021-07-05 09:21:44,788:INFO:certbot._internal.auth_handler:http-01 challenge for portainer.mydomain.co.uk 2021-07-05 09:21:44,788:DEBUG:certbot.display.util:Notifying user: Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems: Domain: portainer.mydomain.co.uk Type: unauthorized Detail: Invalid response from https: portainer.mydomain.co.uk .well-known acme-challenge xjwt0sAvlZow3m0hs19hIFuogOO9o_PvCdyh6xntdpg [2606:4700:3037::6815:3efc]:"<!DOCTYPE html>n<!--[if lt IE 7]> <html class=" no-js ie6 oldie" lang="en-US">
		<![endif]-->n<!--[if IE 7]>    <html class="no-js "

Hint: The Certificate Authority failed to download the temporary challenge files created by Certbot. Ensure that the listed domains serve their content from the provided --webroot-path/-w and that files created there can be downloaded from the internet.

2021-07-05 09:21:44,789:DEBUG:certbot._internal.error_handler:Encountered exception:
Traceback (most recent call last):
  File "/opt/certbot/lib/python3.7/site-packages/certbot/_internal/auth_handler.py", line 93, in handle_authorizations
    self._poll_authorizations(authzrs, max_retries, best_effort)
  File "/opt/certbot/lib/python3.7/site-packages/certbot/_internal/auth_handler.py", line 181, in _poll_authorizations
    raise errors.AuthorizationError('Some challenges have failed.')
certbot.errors.AuthorizationError: Some challenges have failed.

2021-07-05 09:21:44,789:DEBUG:certbot._internal.error_handler:Calling registered functions
2021-07-05 09:21:44,789:INFO:certbot._internal.auth_handler:Cleaning up challenges
2021-07-05 09:21:44,789:DEBUG:certbot._internal.plugins.webroot:Removing /data/letsencrypt-acme-challenge/.well-known/acme-challenge/xjwt0sAvlZow3m0hs19hIFuogOO9o_PvCdyh6xntdpg
2021-07-05 09:21:44,789:DEBUG:certbot._internal.plugins.webroot:All challenges cleaned up
2021-07-05 09:21:44,789:DEBUG:certbot._internal.log:Exiting abnormally:
Traceback (most recent call last):
  File "/opt/certbot/bin/certbot", line 8, in <module>
    sys.exit(main())
  File "/opt/certbot/lib/python3.7/site-packages/certbot/main.py", line 15, in main
    return internal_main.main(cli_args)
  File "/opt/certbot/lib/python3.7/site-packages/certbot/_internal/main.py", line 1552, in main
    return config.func(config, plugins)
  File "/opt/certbot/lib/python3.7/site-packages/certbot/_internal/main.py", line 1414, in certonly
    lineage = _get_and_save_cert(le_client, config, domains, certname, lineage)
  File "/opt/certbot/lib/python3.7/site-packages/certbot/_internal/main.py", line 128, in _get_and_save_cert
    lineage = le_client.obtain_and_enroll_certificate(domains, certname)
  File "/opt/certbot/lib/python3.7/site-packages/certbot/_internal/client.py", line 445, in obtain_and_enroll_certificate
    cert, chain, key, _ = self.obtain_certificate(domains)
  File "/opt/certbot/lib/python3.7/site-packages/certbot/_internal/client.py", line 375, in obtain_certificate
    orderr = self._get_order_and_authorizations(csr.data, self.config.allow_subset_of_names)
  File "/opt/certbot/lib/python3.7/site-packages/certbot/_internal/client.py", line 425, in _get_order_and_authorizations
    authzr = self.auth_handler.handle_authorizations(orderr, self.config, best_effort)
  File "/opt/certbot/lib/python3.7/site-packages/certbot/_internal/auth_handler.py", line 93, in handle_authorizations
    self._poll_authorizations(authzrs, max_retries, best_effort)
  File "/opt/certbot/lib/python3.7/site-packages/certbot/_internal/auth_handler.py", line 181, in _poll_authorizations
    raise errors.AuthorizationError('Some challenges have failed.')
certbot.errors.AuthorizationError: Some challenges have failed.
2021-07-05 09:21:44,791:ERROR:certbot._internal.log:Some challenges have failed.

I have changed my email and domain name to the variables — myemail.co.uk and mydomain.co.uk

During a Distribution point and Management point installation on a ConfigMgr site server, I received the following errors in BgbisapiMSI.log and BgbSetup.log
-BGB http proxy — Installation operation failed
-Installation success or error status: 1603
-BGB http proxy — Internal Error 25001, 80070057
-Internal Error 25001, 80070057
-CustomAction CcmRegisterPerfCounters returned actual error code 1603
-Fatal MSI Error — bgbisapi.msi could not be installed

Trick is, you need to have Background Intelligent Transfer Service (BITS) installed on the site server. It is required, otherwise you will see those 25001 errors. After installing BITS and restart SMS_SITE_COMPONENT_MANAGER installation went fine after all. Next time, make sure BITS is installed before starting :-)



Hope it helps!


Source: Microsoft Technet Forums

Понравилась статья? Поделить с друзьями:
  • Как правильно составить репортаж
  • Как найти свой цвет рыжего
  • Как составить полный адрес
  • Как найти валентность po4
  • Как найти неопределенный интеграл с подробным решением