I am getting very fed up, since the new update, it must be a month now, and the bugs continue to be there. But not simple bugs, BUGS THAT PREVENT CUSTOMERS FROM ORDERING. The checkout form in fact, since the new update, is buggy: some customers can see it and others (including me) see it as I am showing in the picture! in addition the support responds after hours by saying it is working, but how is it working if multiple customers are complaining about this problem? Get to the bottom of it and quickly fix all these fucking bugs that have been created, it’s shameful to wait all this time, what’s more no one who cares about it!!!
1 Like
Hey @ynguido — I hear you. This is frustrating.
Thanks for flagging it loud and clear.
Quick checklist to troubleshoot the checkout showing/not showing:
- Test in incognito and another device.
- Hard refresh the page (Ctrl+Shift+R / ⌘+Shift+R).
- Duplicate the funnel and test on the clone.
- Check form fields in the checkout step. Make sure required fields match and none are missing.
- Check product bindings. Each product must be properly bound to the product list / buttons.
- Check the submit button interaction. It must be set to Submit step (not stripped or empty).
- If you use Gateway Pools, try switching to classic payment gateway to test if Gateway Pool causes issue.
- Open browser dev console (F12) and look for JS errors or 404s. Copy the error text if you see any.
- Check Stripe (or your gateway) status and that keys are correct for the mode (test vs live).
- Clear any custom code temporarily (custom JS) and retest. Custom scripts can conflict with v2.
If you still face it, please send me:
- Funnel preview link or published URL (DM ok).
- A short Loom video showing the issue and console errors.
I will pass it to the devs and push for priority review.
I know this is costing you time and money. We are working on fixes and on improving response time. Thanks for pushing — we’ll do our best to help get your checkout stable fast.
im having this same issue… tried all of the above. Any fix?
1 Like
@Austin_Eckman DM your funnel share link please.
Hey man I have a different issue and posted a thread about it - I was trying to DM you and see if you had time to look at it soon but it said I can’t send a message to you?
How do I DM you?
Thread is called “PayPal subscriptions aren’t syncing to Shopify on rebills” if you have time to look at it.
1 Like
I wrote you in DM but you don’t answer me.
Hey @Austin_Eckman @ynguido can you DM me your live checkout page url, and do you have any details on when it’s not loading ? as in does it not load on specific browsers, regions, or devices?
1 Like
Hi @ynguido,
I have checked your DM, your landing/checkout pages and recorded video url are not correct, they are returning 404 not found. Could you provide the right one?
Thank you
Hi @anwerashif , I’m having one issue on my checkout too. Is pretty urgent, suddenly checkout with CC doesn’t work. I can’t integrate Airwallex Payment anymore. Always worked with no issue until yesterday. We need to solve this issue ASAP. Can you please DM me? I can’t find the option to DM you.
Hi @mgecom click on on the profile icon and you will find the message option to DM.
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.
1 Like
@apostle Do you think is that related to my issue too?
My issue is that once someone tries to purchase with CC (airwallex) gives back one error ( Error: airwallex status code != 200, 400)
Seems one API - integration issue, but I can’t figure out how to fix this. Tried already to do again the integration with Airwallex but worked only for 2-3 orders and now stopped to work again
So my question is: Funnelish bug or I can try to fix it somehow by myself? Is related to the issue that you mentioned or something different?
1 Like
Hi @apostle
The issue reported here with apps.myfunnelish.com has been fixed actually a few days ago, you should not be facing that issue going forward.
Let us know if you are still facing any issues,
Can you PM me the checkout page url, and have you tested it on test mode does it have the same issue?
Airwallex returning that error often means it got disconnected, but it might also be something else.
Thanks I will monitor.
1 Like
Hi @yassine I can’t DM you. Do you mind DMing me so I can send you everything? Thanks
i got this error as well. this is frustrating
Hey @ynguido @Austin_Eckman @mgecom @RYgy @apostle 
Thanks for sharing all the details here — really appreciate you taking the time to explain everything clearly.
The team from Airwallex and Funnelish are already working together on this issue. The Airwallex devs have noticed some API calls returning unexpected errors, and both teams are digging into it to find a stable fix.
It’s a serious issue and being treated with high priority. We’ll update you all once there’s more info or a confirmed solution.