I took another look at MicroDot and it appears to be creating its security context here -
https://github.com/miguelgrinberg/micro ... llo.py#L35Which seems reflected in what I have -That 'context.verify_mode = ssl.CERT_NONE' appears to be setting to the default so that's redundant but shouldn't affect things.
I still haven't found exactly where and how MicroDot applies that context to the connection - If anyone does know that would be a great help.
But it made me realise that it might be the type or nature of the certificate or key which is a part of the issue.
I settled on what I have after encountering failures and chasing down "that doesn't work, but this does" posts. Now I have it working it would be worth revisiting that and seeing if other means of certificate and key creation deliver a better result.
i guess it's also worth trying "GB" as the correct two-letter country code for the UK.
https://github.com/miguelgrinberg/micro ... llo.py#L35
Code:
ext = 'der' if sys.implementation.name == 'micropython' else 'pem'sslctx = ssl.SSLContext(ssl.PROTOCOL_TLS_SERVER)sslctx.load_cert_chain('cert.' + ext, 'key.' + ext)Code:
context = ssl.SSLContext(ssl.PROTOCOL_TLS_SERVER)context.verify_mode = ssl.CERT_NONEcontext.load_cert_chain("ec_cert.der", "ec_key.der")I still haven't found exactly where and how MicroDot applies that context to the connection - If anyone does know that would be a great help.
But it made me realise that it might be the type or nature of the certificate or key which is a part of the issue.
I settled on what I have after encountering failures and chasing down "that doesn't work, but this does" posts. Now I have it working it would be worth revisiting that and seeing if other means of certificate and key creation deliver a better result.
i guess it's also worth trying "GB" as the correct two-letter country code for the UK.
Statistics: Posted by hippy — Sat Jun 07, 2025 2:32 pm