Hi,
We recently encounter an issue that when we are connected to OpenVPN, the Tawk is not working and getting blocked errors. We thought that this is a CORS or Headers issue with OpenVPN.
The OpenVPN is hosted on AWS. So what we did was to create a new linux server and tried to curl the same URL from our widget and it’s getting cloudflare blocked error too.
We created a fresh windows instance and access the URL and it’s getting Cloudflare blocked issue. Therefore Tawk is blocking AWS IP’s right?
Hi @kkhhg8856 ,
Have you tried switching network connections without using a VPN?
I have confirmed with Tawk Support and Tawk Dev confirmed that they are blocking AWS IPs.
Hi @kkhhg8856 ,
Is it okay to check this with one of our technical team members via call? If yes, please book a call with them at this link: Calendly
Hi JethroPaul,
Not sure if this can be fix thru call since your Dev team confirmed that AWS IP’s are blocked by Tawk.
I have an email thread with support and they confirmed that they are blocking AWS IP’s. Do you think is there a way we can whitelist some legit IP’s?
Is this not quite concerning? If Tawk is blocking AWS IPs? The majority of the cloud services are using AWS. Is this the same case for Azure and GCP?
