several TLS records
See original GitHub issueI’m getting the following message in log for every domain I try:
The MASK_HOST $host returned several TLS records, this is not supported
What am I doing wrong? What domain can I use that is supported?
Even my own domains with TLS1.3 only do not fit.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:13 (6 by maintainers)
Top Results From Across the Web
2 TLS record layers in the same packet - Server Fault
I am analyzing some packets from a smart cam, and I found that a single IP packet includes 2 TLS records as shown...
Read more >Networking 101: Transport Layer Security (TLS)
The TLS Record protocol is responsible for identifying different types of messages (handshake, alert, or data via the "Content Type" field), as well...
Read more >TLS Record Layer - Web Security, Privacy & Commerce, 2nd ...
Each TLS record contains the following information: Content type. Protocol version number. Length. Data payload (optionally compressed and encrypted).
Read more >TLS Record Protocol - Win32 apps - Microsoft Learn
The Transport Layer Security (TLS) Record protocol secures application data using the keys created during the Handshake.
Read more >Transport Layer Security - Wikipedia
It runs in the presentation layer and is itself composed of two layers: the TLS record and the TLS handshake protocols. The closely...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Не понятно как решить данную проблему, если использовать собственный домен. В моем случае схема следующая: haproxy -> mtproto -> caddy. До 1.0.8 эта схема работала корректно, сейчас я также получаю данную ошибку.
OK, so there are 2 issues.
So far I found that google.com and cloudflare.com are good enough, but making Fake-TLS with my actual domain would be much better in terms of obscurity.