Disable TLSv1.0 and TLSv1.1 about docker-swag

[github-actions]

Thanks for opening your first issue here! Be sure to follow the bug or feature issue templates!

[nemchik]

You seem to be using CloudFlare's DNS proxy which applies a different set of ssl protocols based on configurations in their dashboard. In your CloudFlare dashboard under SSL/TLS > Edge Certificates > Minimum TLS Version you can set 1.2. I've had issues with CF not applying those settings correctly and have had to go toggle other options until it resolved the issue, so keep that in mind, you may have to do that. In the end I set everything back the way I wanted, but turning something off and then on again seemed to fix the issue.

Further evidence would be to run curl -I -v --tlsv1 --tls-max 1.0 https://your_wan_ip using your WAN IP rather than your domain will show an error due to TLS 1.0 not being available.

$ curl -I -v --tlsv1 --tls-max 1.0 https://my.domain.com
*   Trying my_wan_ip:443...
* TCP_NODELAY set
* Connected to my.domain.com (my_wan_ip) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS alert, internal error (592):
* error:141E70BF:SSL routines:tls_construct_client_hello:no protocols available
* Closing connection 0
curl: (35) error:141E70BF:SSL routines:tls_construct_client_hello:no protocols available