Sorry to say, I know what the issue is and I have reported it to Funnelish team - but they don’t seem to be prioritising this.
The issue wasn’t with Funnelish itself — it’s a network-level block affecting Funnelish’s CDN endpoint.
apps.myfunnelish.com (which hosts essential checkout scripts) is served via Fastly, and some of Fastly’s POP IPs have been picked up by community threat blocklists like SURBL and PlonkatronixBL (and occasionally ZeroDot1). When certain ISPs — particularly in the UK and parts of the US — use these feeds in their parental or security filters, the browser fails the TLS handshake to that domain, triggering ERR_SSL_PROTOCOL_ERROR.
That means the Funnelish scripts (like funnelish-pay.min.js) never load, so Step 1 of the checkout form hangs indefinitely. The fix is to route critical JS through a clean Fastly hostname (e.g. a first-party CNAME) or have Funnelish rotate off the flagged Fastly IP ranges.
Even the support team are being ghosted by the devs right now.
I reported this 2 weeks ago. The fix is to not use Fastly and a CDN that isn’t getting IP blocked.
I will give them 2 more weeks before I have to move on to a different funnel builder.