No, that endpoint just takes the POST request, loads some data tables from backendless, and updates the data in those tables depending on what is in the body.
I finally heard back from Zapier and they suspect that the issue is due to provisioning inconsistencies in the server pool used by Backendless. They asked me to check with you to ensure that all of the servers in your server pool are provisioned correctly and that TLS support is consistent across the server pool.
Please let me know if there is anything else you would like me to ask for. Iām still unable to resolve this intermittent issue.
Hello, @Ian_Rutner
I checked from our side only one server is engaged in SSL handshake, there is also a spare server that is not used. I checked all the servers that can participate in this, everywhere the certificates respond equally correctly.
What exactly did Zapierās support say about the verification from an independent source, which is available at this SSL Server Test: bijouwash.backendless.app (Powered by Qualys SSL Labs) link?
We checked several times and the answer of this service was always correct.
It is possible that some of the TLS modes are not supported bt Zapier, this needs to be clarified.
Can you check the TLS 1.3 support on your servers to make sure it is configured correctly?
Zapier will get back to me if they have any new updates as they are continuing to investigate this.
I looked at the reports described. I see that they are the same, but I have one guess, thatās why I made some changes in the priority of certain encryption algorithms that are supported in TLS 1.3, I made changes. Could you check from your side or indicate how to check that your logic works?
I have started to experience the same problem, hopefully the information below will help:
I have 2 environments, one is a custom domain (production) and one is not custom domain (development).
I have just moved into a WeWork office, and the problem only exists when using their wifi.
The custom domain is not impacted, but the other environment shows this error only when connected to their wifi. If I tether to my phone network, the problem doesnāt occur.
Iāve raised with WeWork and am waiting for a response, but thought this may help.
We also saw a similar issue when connected to an office network, and it was due to the firewall injecting a different certificate. Seems like it is unrelated to the issue here, but that may be helpful for you in tracking down what is going on at your WeWork office.