Jump to content
Как правильно добавить self-test и прочую отладку в тему
Где взять тестовые сборки
Официальное хранилище ПО в виде файлов
  • 0

https-dns-proxy: xxxx: curl error message:

r777ay

Asked by r777ay,

 Share

Question

r777ay Honored Flooder

r777ay

Posted
Posted (edited)

Передёрнул перекл. "Разрешать имена при помощи DNS-серверов подключений в интернет". Пропал доступ в интернет, в жур. до ∞  

[W] Dec 24 14:55:23 https-dns-proxy: 9A8C: curl error message: Operation timed out after 10000 milliseconds with 0 bytes received 
[W] Dec 24 14:55:24 https-dns-proxy: 84F6: curl request failed with 0: No error 
[W] Dec 24 14:55:24 https-dns-proxy: 84F6: curl error message: Operation timed out after 10002 milliseconds with 0 bytes received 
[W] Dec 24 14:55:24 https-dns-proxy: 40AF: curl request failed with 0: No error 
[W] Dec 24 14:55:24 https-dns-proxy: 40AF: curl error message: Operation timed out after 10000 milliseconds with 0 bytes received 
[W] Dec 24 14:55:24 https-dns-proxy: B383: curl request failed with 0: No error 
[W] Dec 24 14:55:24 https-dns-proxy: B383: curl error message: Operation timed out after 10000 milliseconds with 0 bytes received 
[W] Dec 24 14:55:24 https-dns-proxy: 2787: curl request failed with 0: No error 
[W] Dec 24 14:55:24 https-dns-proxy: 2787: curl error message: Operation timed out after 10001 milliseconds with 0 bytes received 
[W] Dec 24 14:55:25 https-dns-proxy: 0D6D: curl request failed with 0: No error 
[W] Dec 24 14:55:25 https-dns-proxy: 0D6D: curl error message: Operation timed out after 10000 milliseconds with 0 bytes received

Откл. L2TP & Port - нет реакции, пока не удалил DoH serv CF, доступ не восстановился. Жур. до этого почистил, был весь забит: 

[I] Dec 25 00:13:31 ndm: Dns::Secure::DohConfigurator: fallback to built-in DNS to resolve "cloudflare-dns.com". 
[I] Dec 25 00:15:26 ndhcpc: GigabitEthernet1: received ACK for 100.103.241.37 from 100.103.241.1 lease 600 sec. 
[I] Dec 25 00:15:32 ndm: Dns::Secure::DohConfigurator: fallback to built-in DNS to resolve "cloudflare-dns.com". 
[I] Dec 25 00:20:26 ndhcpc: GigabitEthernet1: received ACK for 100.103.241.37 from 100.103.241.1 lease 600 sec. 
[I] Dec 25 00:20:32 ndm: Dns::Secure::DohConfigurator: fallback to built-in DNS to resolve "cloudflare-dns.com".

огрызок self-test прилагаю.

Edited by r777ay
Link to comment
Share on other sites

4 answers to this question

Recommended Posts

  • 0
vasek00 Honored Flooder

vasek00

Posted
Posted

Посмотрите полный лог, и саму роботу каналов.

 

Ниже при проблемах на канале Интернета, роутер на прямом/проводе без всяких PPP

Скрытый текст 
Канал Интернета пропал
[I] Dec 24 06:24:45 ndm: Network::Interface::Ethernet: "GigabitEthernet1": link down. 
[I] Dec 24 06:24:45 ndm: Network::InternetChecker: Internet access lost (status: 0x0000). 
[W] Dec 24 06:24:46 https-dns-proxy: F588: curl request failed with 0: No error 
[W] Dec 24 06:24:47 https-dns-proxy: 5319: curl request failed with 0: No error 
[W] Dec 24 06:24:47 https-dns-proxy: 5319: curl error message: Failed to connect to dns.google port 443 after 7503 ms: Operation timed out 
[W] Dec 24 06:24:48 https-dns-proxy: 324F: curl request failed with 0: No error 
[W] Dec 24 06:24:48 https-dns-proxy: F00D: curl request failed with 0: No error 
[W] Dec 24 06:24:49 https-dns-proxy: 6103: curl request failed with 0: No error 
[W] Dec 24 06:24:49 https-dns-proxy: 6103: curl error message: Operation timed out after 10000 milliseconds with 0 bytes received 
[I] Dec 24 06:24:49 ndm: Core::Session: client disconnected. 
[W] Dec 24 06:24:50 https-dns-proxy: 5E07: curl request failed with 0: No error 
[W] Dec 24 06:24:51 https-dns-proxy: 9E11: curl request failed with 0: No error 
[I] Dec 24 06:24:51 ndm: Dns::Secure::DohConfigurator: fallback to built-in DNS to resolve "dns.google". 

Канал Интернета появился
[I] Dec 24 06:25:10 ndm: Network::InternetChecker: Internet access detected. 
[I] Dec 24 06:25:11 ndm: NextDns::Client: NextDNS DNS-over-HTTPS is available. 
[I] Dec 24 06:25:11 ndm: Dns::Secure::DohConfigurator: fallback to built-in DNS to resolve "dns.google". 
[I] Dec 24 06:25:11 ndm: Dns::Secure::DohConfigurator: fallback to built-in DNS to resolve "cloudflare-dns.com".


Канал Интернета пропал
[W] Dec 25 06:02:28 https-dns-proxy: BAAB: curl request failed with 0: No error 
[W] Dec 25 06:02:28 https-dns-proxy: BAAB: curl error message: Operation timed out after 10008 milliseconds with 0 bytes received 
[W] Dec 25 06:02:28 https-dns-proxy: 0684: curl request failed with 0: No error 
[W] Dec 25 06:02:28 https-dns-proxy: 0684: curl error message: Operation timed out after 10005 milliseconds with 0 bytes received 
[I] Dec 25 06:02:30 ndm: Network::Interface::Ethernet: "GigabitEthernet1": link down. 
[I] Dec 25 06:02:30 ndm: Network::InternetChecker: Internet access lost (status: 0x0000). 
...
[I] Dec 25 06:02:36 ndm: Dns::Secure::DohConfigurator: fallback to built-in DNS to resolve "dns.google". 
[I] Dec 25 06:02:38 ndm: Dns::Secure::DohConfigurator: unable to obtain addresses for "dns.google". 
[I] Dec 25 06:02:38 ndm: Dns::Secure::DohConfigurator: fallback to built-in DNS to resolve "cloudflare-dns.com". 
[W] Dec 25 06:02:40 https-dns-proxy: 7261: curl request failed with 0: No error 
[W] Dec 25 06:02:40 https-dns-proxy: 7261: curl error message: Operation timed out after 10000 milliseconds with 0 bytes received 
[W] Dec 25 06:02:40 https-dns-proxy: EC2B: curl request failed with 0: No error 
[W] Dec 25 06:02:40 https-dns-proxy: EC2B: curl error message: Operation timed out after 10000 milliseconds with 0 bytes received 
[I] Dec 25 06:02:40 ndm: Dns::Secure::DohConfigurator: unable to obtain addresses for "cloudflare-dns.com". 
[I] Dec 25 06:02:40 ndm: Dns::Manager: rescheduling DNS-over-HTTPS bootstrap. 
[W] Dec 25 06:02:40 https-dns-proxy: 1271: curl request failed with 0: No error 
[W] Dec 25 06:02:40 https-dns-proxy: 1271: curl error message: Operation timed out after 10000 milliseconds with 0 bytes received 
[W] Dec 25 06:02:41 https-dns-proxy: C790: curl request failed with 0: No error 
[W] Dec 25 06:02:41 https-dns-proxy: C790: curl error message: Operation timed out after 10000 milliseconds with 0 bytes received 
[W] Dec 25 06:02:42 https-dns-proxy: 68FE: curl request failed with 0: No error 
[W] Dec 25 06:02:42 https-dns-proxy: 68FE: curl error message: Operation timed out after 10000 milliseconds with 0 bytes received 
[W] Dec 25 06:02:43 https-dns-proxy: EA57: curl request failed with 0: No error 
...
[I] Dec 25 06:02:56 ndm: Dns::Secure::DohConfigurator: fallback to built-in DNS to resolve "dns.google". 
[I] Dec 25 06:02:56 ndm: Dns::Secure::DohConfigurator: fallback to built-in DNS to resolve "cloudflare-dns.com". 
[W] Dec 25 06:02:57 https-dns-proxy: 0CAF: curl request failed with 0: No error 
[W] Dec 25 06:02:57 https-dns-proxy: 0CAF: curl error message: Operation timed out after 10000 milliseconds with 0 bytes received 
[W] Dec 25 06:02:57 https-dns-proxy: A2D5: curl request failed with 0: No error 
[W] Dec 25 06:02:57 https-dns-proxy: A2D5: curl error message: Operation timed out after 10000 milliseconds with 0 bytes received 
[W] Dec 25 06:03:00 https-dns-proxy: 9256: curl request failed with 0: No error 
...
[W] Dec 25 06:03:18 https-dns-proxy: 1A31: curl error message: Operation timed out after 10000 milliseconds with 0 bytes received 

Канал Интернета появился
[I] Dec 25 06:03:19 ndm: Network::InternetChecker: Internet access detected. 

[I] Dec 25 18:02:57 ndm: Dns::Secure::DohConfigurator: fallback to built-in DNS to resolve "dns.google". 
[I] Dec 25 18:02:57 ndm: Dns::Secure::DohConfigurator: fallback to built-in DNS to resolve "cloudflare-dns.com". 

Канал Интернета пропал
[I] Dec 26 06:02:52 ndm: Network::Interface::Ethernet: "GigabitEthernet1": link down. 
[I] Dec 26 06:02:52 ndm: Network::InternetChecker: Internet access lost (status: 0x0000). 
[W] Dec 26 06:02:52 https-dns-proxy: 7774: curl request failed with 0: No error 
[W] Dec 26 06:02:52 https-dns-proxy: 7774: curl error message: Operation timed out after 10001 milliseconds with 0 bytes received 
[W] Dec 26 06:02:53 https-dns-proxy: 46AA: curl request failed with 0: No error 
[W] Dec 26 06:02:53 https-dns-proxy: 68AC: curl request failed with 0: No error 
[W] Dec 26 06:02:54 https-dns-proxy: FC12: curl request failed with 0: No error 
[W] Dec 26 06:02:54 https-dns-proxy: FC12: curl error message: Failed to connect to dns.google port 443 after 4084 ms: Host is unreachable 
[W] Dec 26 06:02:55 https-dns-proxy: 055B: curl request failed with 0: No error 
[W] Dec 26 06:02:56 https-dns-proxy: 913F: curl request failed with 0: No error 
...
[I] Dec 26 06:02:57 ndm: Dns::Secure::DohConfigurator: fallback to built-in DNS to resolve "dns.google". 
[W] Dec 26 06:02:57 https-dns-proxy: 2341: curl request failed with 0: No error 
[I] Dec 26 06:02:59 ndm: Dns::Secure::DohConfigurator: unable to obtain addresses for "dns.google". 
[I] Dec 26 06:02:59 ndm: Dns::Secure::DohConfigurator: fallback to built-in DNS to resolve "cloudflare-dns.com". 
[W] Dec 26 06:02:59 https-dns-proxy: 8833: curl request failed with 0: No error 
[W] Dec 26 06:02:59 https-dns-proxy: 8833: curl error message: Operation timed out after 10002 milliseconds with 0 bytes received 
[W] Dec 26 06:03:00 https-dns-proxy: 81C3: curl request failed with 0: No error 
[I] Dec 26 06:03:01 ndm: Dns::Secure::DohConfigurator: unable to obtain addresses for "cloudflare-dns.com". 
[I] Dec 26 06:03:01 ndm: Dns::Manager: rescheduling DNS-over-HTTPS bootstrap. 
[W] Dec 26 06:03:02 https-dns-proxy: 8CF2: curl request failed with 0: No error 
[W] Dec 26 06:03:02 https-dns-proxy: 8CF2: curl error message: Operation timed out after 10000 milliseconds with 0 bytes received 
[W] Dec 26 06:03:03 https-dns-proxy: F286: curl request failed with 0: No error 
...
Канал появился
[I] Dec 26 06:03:12 ndm: Network::Interface::Ethernet: "GigabitEthernet1": link up (100FD/AN). 
[W] Dec 26 06:03:14 https-dns-proxy: EEAA: curl request failed with 0: No error 
[W] Dec 26 06:03:14 https-dns-proxy: 583A: curl request failed with 0: No error 
[W] Dec 26 06:03:14 https-dns-proxy: 583A: curl error message: Operation timed out after 10000 milliseconds with 0 bytes received 
[W] Dec 26 06:03:14 https-dns-proxy: 5B9F: curl request failed with 0: No error 
[W] Dec 26 06:03:15 https-dns-proxy: 8AD7: curl request failed with 0: No error 
[W] Dec 26 06:03:15 https-dns-proxy: 8AD7: curl error message: Operation timed out after 10001 milliseconds with 0 bytes received 
[I] Dec 26 06:03:16 ndm: Network::InternetChecker: Internet access detected. 
[I] Dec 26 06:03:16 ndm: NextDns::Client: NextDNS DNS-over-HTTPS is available. 
[I] Dec 26 06:03:17 ndm: Dns::Secure::DohConfigurator: fallback to built-in DNS to resolve "dns.google". 
[I] Dec 26 06:03:17 ndm: Dns::Secure::DohConfigurator: fallback to built-in DNS to resolve "cloudflare-dns.com".

 

 

Link to comment
Share on other sites
  • 0
Дядька Слаука Advanced Member

Дядька Слаука

Posted
Posted

3.8.1 Beta

Вчера были какие то проблемы с интернетом на телефонах, уважаемые люди донесли до меня эту информацию только сегодня.Проверил время в логе, примерно обозначенное уважаемыми людьми. И обнаружил вот такие "матные слова": 

Скрытый текст 


[W] Apr 29 21:44:35 https-dns-proxy: 76AA: curl request failed with 0: No error 
[W] Apr 29 21:44:35 https-dns-proxy: 76AA: curl error message: Operation timed out after 981 milliseconds with 0 bytes received 
[W] Apr 29 21:44:35 https-dns-proxy: Resolver may not support current HTTP/1.0 protocol version 
[W] Apr 29 21:44:35 https-dns-proxy: 7FD3: curl request failed with 0: No error 
[W] Apr 29 21:44:35 https-dns-proxy: 7FD3: curl error message: Operation timed out after 3204 milliseconds with 0 bytes received 
[W] Apr 29 21:44:35 https-dns-proxy: Resolver may not support current HTTP/1.0 protocol version 
[W] Apr 29 21:45:15 https-dns-proxy: 6B50: curl request failed with 0: No error 
[W] Apr 29 21:45:15 https-dns-proxy: 6B50: curl error message: Failed to connect to dns.nextdns.io port 443 after 2250 ms: Operation timed out 
[W] Apr 29 21:45:51 https-dns-proxy: 3CBF: curl request failed with 0: No error 
[W] Apr 29 21:45:51 https-dns-proxy: 3CBF: curl error message: Operation timed out after 3001 milliseconds with 0 bytes received 
[W] Apr 29 21:45:51 https-dns-proxy: 3CBF: CURLINFO_SSL_VERIFYRESULT: Error 
[W] Apr 29 21:46:38 https-dns-proxy: 567F: curl request failed with 0: No error 
[W] Apr 29 21:46:38 https-dns-proxy: 567F: curl error message: Operation timed out after 3000 milliseconds with 0 bytes received 
[W] Apr 29 21:46:38 https-dns-proxy: Resolver may not support current HTTP/1.0 protocol version 
[W] Apr 29 21:46:38 https-dns-proxy: 44ED: curl request failed with 0: No error 
[W] Apr 29 21:46:38 https-dns-proxy: 44ED: curl error message: Operation timed out after 3000 milliseconds with 0 bytes received 
[W] Apr 29 21:46:38 https-dns-proxy: Resolver may not support current HTTP/1.0 protocol version 
[W] Apr 29 21:46:39 https-dns-proxy: 55C3: curl request failed with 0: No error 
[W] Apr 29 21:46:39 https-dns-proxy: 55C3: curl error message: Operation timed out after 3000 milliseconds with 0 bytes received 
[W] Apr 29 21:46:39 https-dns-proxy: 55C3: CURLINFO_SSL_VERIFYRESULT: Error 
[W] Apr 29 21:47:06 https-dns-proxy: A32B: curl request failed with 0: No error 
[W] Apr 29 21:47:06 https-dns-proxy: A32B: curl error message: Failed to connect to dns.nextdns.io port 443 after 2252 ms: Operation timed out 
[W] Apr 29 21:47:09 https-dns-proxy: A9E3: curl request failed with 0: No error 
[W] Apr 29 21:47:09 https-dns-proxy: A9E3: curl error message: Operation timed out after 3000 milliseconds with 0 bytes received 
[W] Apr 29 21:47:09 https-dns-proxy: Resolver may not support current HTTP/1.0 protocol version 
[W] Apr 29 21:47:11 https-dns-proxy: 0658: curl request failed with 0: No error 
[W] Apr 29 21:47:11 https-dns-proxy: 0658: curl error message: Operation timed out after 3006 milliseconds with 0 bytes received 
[W] Apr 29 21:47:11 https-dns-proxy: 0658: CURLINFO_SSL_VERIFYRESULT: Error 
[W] Apr 29 21:47:11 https-dns-proxy: 8B2F: curl request failed with 0: No error 
[W] Apr 29 21:47:11 https-dns-proxy: 8B2F: curl error message: Failed to connect to dns.nextdns.io port 443 after 2409 ms: Operation timed out 
[W] Apr 29 21:47:47 https-dns-proxy: A239: curl request failed with 0: No error 
[W] Apr 29 21:47:47 https-dns-proxy: A239: curl error message: Failed to connect to dns.nextdns.io port 443 after 2251 ms: Operation timed out 
[W] Apr 29 21:47:51 https-dns-proxy: DE25: curl request failed with 0: No error 
[W] Apr 29 21:47:51 https-dns-proxy: DE25: curl error message: Operation timed out after 3000 milliseconds with 0 bytes received 
[W] Apr 29 21:47:51 https-dns-proxy: DE25: CURLINFO_SSL_VERIFYRESULT: Error 
[W] Apr 29 21:47:56 https-dns-proxy: E42E: curl request failed with 0: No error 
[W] Apr 29 21:47:56 https-dns-proxy: E42E: curl error message: Operation timed out after 3000 milliseconds with 0 bytes received 
[W] Apr 29 21:47:56 https-dns-proxy: Resolver may not support current HTTP/1.0 protocol version 
[W] Apr 29 21:48:21 https-dns-proxy: E2BA: curl request failed with 0: No error 
[W] Apr 29 21:48:21 https-dns-proxy: E2BA: curl error message: Operation timed out after 3000 milliseconds with 0 bytes received 
[W] Apr 29 21:48:21 https-dns-proxy: Resolver may not support current HTTP/1.0 protocol version 
[W] Apr 29 21:48:29 https-dns-proxy: A3A3: curl request failed with 0: No error 
[W] Apr 29 21:48:29 https-dns-proxy: A3A3: curl error message: Operation timed out after 3000 milliseconds with 0 bytes received 
[W] Apr 29 21:48:29 https-dns-proxy: Resolver may not support current HTTP/1.0 protocol version 
[W] Apr 29 21:49:07 https-dns-proxy: 0DF9: curl request failed with 0: No error 
[W] Apr 29 21:49:07 https-dns-proxy: 0DF9: curl error message: Operation timed out after 3000 milliseconds with 0 bytes received 
[W] Apr 29 21:49:07 https-dns-proxy: Resolver may not support current HTTP/1.0 protocol version 
[W] Apr 29 21:49:19 https-dns-proxy: 6502: curl request failed with 0: No error 
[W] Apr 29 21:49:19 https-dns-proxy: 6502: curl error message: Operation timed out after 3186 milliseconds with 0 bytes received 
[W] Apr 29 21:49:19 https-dns-proxy: Resolver may not support current HTTP/1.0 protocol version 
[W] Apr 29 21:49:25 https-dns-proxy: E646: curl request failed with 0: No error 
[W] Apr 29 21:49:25 https-dns-proxy: E646: curl error message: Operation timed out after 3001 milliseconds with 0 bytes received 
[W] Apr 29 21:49:25 https-dns-proxy: Resolver may not support current HTTP/1.0 protocol version

Это ругань на DoH (NextDNS)?

Немного позже, снова ругань. Жалоб на неё не поступало. 

[W] Apr 29 23:15:40 https-dns-proxy: C72C: curl request failed with 0: No error 
[W] Apr 29 23:15:40 https-dns-proxy: C72C: curl error message: Operation timed out after 3000 milliseconds with 0 bytes received 
[W] Apr 29 23:15:40 https-dns-proxy: Resolver may not support current HTTP/1.0 protocol version 
[W] Apr 29 23:15:41 https-dns-proxy: 7C8C: curl request failed with 0: No error 
[W] Apr 29 23:15:41 https-dns-proxy: 7C8C: curl error message: Operation timed out after 3253 milliseconds with 0 bytes received 
[W] Apr 29 23:15:41 https-dns-proxy: Resolver may not support current HTTP/1.0 protocol version 
[W] Apr 29 23:15:41 https-dns-proxy: 049E: curl request failed with 0: No error 
[W] Apr 29 23:15:41 https-dns-proxy: 049E: curl error message: Failed to connect to dns.nextdns.io port 443 after 2255 ms: Operation timed out


 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to question listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...