I’m trying to wire up an IoT device to reach the APIs of one of my sites (https://zooey.club / https://zooey-club.netlify.app), and it can’t establish a connection. I’m using CircuitPython/MicroPython so it has some limitations, but I’m hoping to get some pointers before I just wander the potential depths of this problem (I’m relatively new to playing around with embedded code like this as opposed to my web day job). I don’t get a ton of info about the failure, simply getting
Sending request failed at what seems to be during TLS negotiation?
Things I’ve tried:
- I’ve tried connecting to neither my custom domain nor my apps underlying netlify domain works.
- I’m trying to POST to an API route, but even trying to GET the index page fails.
- This problem appears to happen for all Netlify apps, not just mine. I tried reaching any of my other apps and also https://hawk.dance / https://hawk-dance.netlify.app (from the dusty.domains showcase) and they all fail as well.
- I can access my sites on other similar providers without issue: eg *.web.app for Firebase and *.herokuapp.com for Heroku
- I can access other non-Heroku domains I have through my same registrar.
So with all of the above, I’m pretty confident that Netlify is doing something different as the root cause since it is the only commonality breaking my CircuitPython requests library. I was hoping to get some hints about how Netlify’s setup might be causing this issue (I vaguely recall reading something about Netlify doing something tricky w/r/t to request resolution or something a few months back?). I tried seaching to no avail, but I assume other people must be trying to do something similar. Ultimately I can set up a proxy at one of the other providers as a last resort, but I want to make this work.