Jump to content

Geont

Forum Members
  • Content count

    76
  • Joined

  • Last visited

Community Reputation

4 Neutral

About Geont

  • Rank
    Advanced Member

Equipment

  • Keenetic
    Ultra II, Ultra, Giga III
  1. 2.12.A.5.0-10, Ultra Проблема с получением сертификата .keenetic.io по-прежнему актуальна May 11 07:50:10 ndm Acme::Client: perform HTTP sanity checks for domain "a42b8dcd3244b6f1xxxxxxxx.keenetic.io". May 11 07:50:10 ndm Io::TcpSocket: connected to 46.105.148.92:80. May 11 04:50:11 acme-client generating RSA domain key May 11 04:50:16 acme-client acme-v01.api.letsencrypt.org: resolving May 11 07:50:16 acme-client acme-v01.api.letsencrypt.org: DNS: 184.86.59.247 May 11 04:50:16 acme-client https://acme-v01.api.letsencrypt.org/directory: directories May 11 04:50:16 acme-client https://acme-v01.api.letsencrypt.org/directory: perform request May 11 04:50:16 acme-client https://acme-v01.api.letsencrypt.org/acme/new-authz: req-auth: a42b8dcd3244b6f1dc97d7f5.keenetic.io May 11 04:50:18 acme-client https://acme-v01.api.letsencrypt.org/acme/challenge/0j_f8otaWe8HZO9XBRB042tYi2qNdzjZ1Qa7B0Vr3d4/4591872095: challenge May 11 04:50:24 acme-client https://acme-v01.api.letsencrypt.org/acme/challenge/0j_f8otaWe8HZO9XBRB042tYi2qNdzjZ1Qa7B0Vr3d4/4591872095: status May 11 04:50:24 acme-client https://acme-v01.api.letsencrypt.org/acme/challenge/0j_f8otaWe8HZO9XBRB042tYi2qNdzjZ1Qa7B0Vr3d4/4591872095: perform request May 11 04:50:24 acme-client https://acme-v01.api.letsencrypt.org/acme/new-cert: certificate May 11 04:50:26 acme-client https://acme-v01.api.letsencrypt.org/acme/new-cert: bad HTTP: 403 May 11 04:50:26 acme-client transfer buffer: [{ "type": "urn:acme:error:unauthorized", "detail": "Error creating new cert :: authorizations for these names not found or expired: a42b8dcd3244b6f1dc97d7f5.keenetic.io", "status": 403 }] (192 bytes) May 11 04:50:26 acme-client bad exit: netproc(651): 1 May 11 07:50:26 ndm Http::Manager: security level unchanged. May 11 07:50:26 ndm Acme::Client: retry after 15 s, retry 1. May 11 07:50:41 ndm Http::Manager: security level unchanged. May 11 07:50:41 ndm Acme::Client: obtaining certificate for domain "a42b8dcd3244b6f1xxxxxxxx.keenetic.io" is started. May 11 07:50:43 ndm Acme::Client: perform HTTP sanity checks for domain "a42b8dcd3244b6f1xxxxxxxx.keenetic.io". May 11 07:50:43 ndm Io::TcpSocket: connected to 46.105.148.92:80. May 11 04:50:44 acme-client generating RSA domain key May 11 07:50:44 ndm Cifs::ServerNQ: service started. May 11 04:50:47 acme-client acme-v01.api.letsencrypt.org: resolving May 11 07:50:47 acme-client acme-v01.api.letsencrypt.org: DNS: 184.86.59.247 May 11 04:50:47 acme-client https://acme-v01.api.letsencrypt.org/directory: directories May 11 04:50:47 acme-client https://acme-v01.api.letsencrypt.org/directory: perform request May 11 04:50:48 acme-client https://acme-v01.api.letsencrypt.org/acme/new-authz: req-auth: a42b8dcd3244b6f1dc97d7f5.keenetic.io May 11 04:50:49 acme-client https://acme-v01.api.letsencrypt.org/acme/challenge/0j_f8otaWe8HZO9XBRB042tYi2qNdzjZ1Qa7B0Vr3d4/4591872095: challenge May 11 04:50:56 acme-client https://acme-v01.api.letsencrypt.org/acme/challenge/0j_f8otaWe8HZO9XBRB042tYi2qNdzjZ1Qa7B0Vr3d4/4591872095: status May 11 04:50:56 acme-client https://acme-v01.api.letsencrypt.org/acme/challenge/0j_f8otaWe8HZO9XBRB042tYi2qNdzjZ1Qa7B0Vr3d4/4591872095: perform request May 11 04:50:56 acme-client https://acme-v01.api.letsencrypt.org/acme/new-cert: certificate May 11 04:50:57 acme-client https://acme-v01.api.letsencrypt.org/acme/new-cert: bad HTTP: 403 May 11 04:50:57 acme-client transfer buffer: [{ "type": "urn:acme:error:unauthorized", "detail": "Error creating new cert :: authorizations for these names not found or expired: a42b8dcd3244b6f1xxxxxxxx.keenetic.io", "status": 403 }] (192 bytes) May 11 04:50:57 acme-client bad exit: netproc(685): 1 May 11 07:50:57 ndm Http::Manager: security level unchanged. May 11 07:50:57 ndm Acme::Client: retry after 30 s, retry 2. May 11 07:51:28 ndm Http::Manager: security level unchanged. May 11 07:51:28 ndm Acme::Client: obtaining certificate for domain "a42b8dcd3244b6f1xxxxxxxx.keenetic.io" is started. May 11 07:51:31 ndm Acme::Client: perform HTTP sanity checks for domain "a42b8dcd3244b6f1xxxxxxxx.keenetic.io". May 11 07:51:31 ndm Io::TcpSocket: connected to 46.105.148.92:80. May 11 07:51:36 ndm Io::Http::Client: [470] unable to receive headers: operation timeout. May 11 07:51:36 ndm Acme::Client: check failed for domain "a42b8dcd3244b6f1xxxxxxxx.keenetic.io". May 11 07:51:36 ndm Http::Manager: security level unchanged. May 11 07:51:36 ndm Acme::Client: retry after 64 s, retry 3. Self на месте.
  2. Сегодня еще высыпалось: Mar 14 16:27:33 ndm Core::Scgi::Session: unsupported method "POST" for "/ivr/VAD_Deploy.aspx?projectname=ab_ab". Mar 14 16:27:33 giga_iii nginx 2018/03/14 16:27:33 [error] 804#0: *24141 readv() failed (131: Unknown error) while reading upstream, client: 195.154.52.168, server: my.keenetic.net, request: "POST /ivr/VAD_Deploy.aspx?projectname=ab_ab HTTP/1.1", upstream: "scgi://unix:/var/run/ndm.scgi.socket:", host: "xx.xx.xx.xxx" Это очень страшно?
  3. Core::Scgi::Session: unsupported method "POST" for "/". А за такие тоже?
  4. Self-test с debug прикрепил.
  5. self-test.txt
  6. Уже. Заявка у них есть, но self вечером сделаю, гляньте, мож какие вопросы правильные подскажете.
  7. Рязанский westcall еще осенью слился в экстазе с Dom.ru В ЛК все включено, они мне вчера даже рассказывали, как startup-config надо править) Да, self получился без debug, вечером все сделаю.
  8. Self-test прикрепил. После interface PPPoE0 debug в логе появилось еще и это: Mar 02 07:34:13 pppd[26612] sent [IPV6CP ConfReq id=0x1 <addr fe80::28af:df8a:3a15:993b>] Mar 02 07:34:16 pppd[26612] sent [IPV6CP ConfReq id=0x1 <addr fe80::28af:df8a:3a15:993b>] Mar 02 07:34:16 pppd[26612] sent [IPV6CP ConfReq id=0x1 <addr fe80::28af:df8a:3a15:993b>] Mar 02 07:34:19 pppd[26612] IPV6CP: timeout sending Config-Requests
  9. self-test(2).txt
  10. Бодаюсь с провом, который де юре предоставляет адресацию ipv6. Cоединение по PPPoE. Галки стоят. Адресации нет. В логе Mar 01 22:54:11pppd[2453] IPV6CP: timeout sending Config-Requests Есть мысли?
  11. Хотя нет. От PPPoE вряд ли зависит. Опять весь лог загадило. Self-test ниже.
  12. Я тоже но сейчас и правда все работает. А тогда не работало
  13. Чуть больше чем обычно подтормаживает старый интерфейс Giga III. В остальном, вроде бы, все работает. Указанные записи пропадают после того, как провайдер раз в сутки разрывает сессию PPPoE. Однако, таких записей не наблюдалось вовсе ранее 2.12.A.3.0-4
×