since of today, we cant get access to our tables anymore.
I think the proxy at our side is categorizing the traffic/site as “suspicious”. I can access the tables through my personal computer / internet connection. Only accessing from the companies (high security) network I get this error.
Were there any changes in the infrastructure at your side?
I also will check at our side, but as it is a very large company that will tak some time.
I have seen this message one time before with another website. That website was accessed through Cloudflare. Are your services behind a service like Cloudflare?
I have only ideas why this happened. Most likely from my point is that the increased the security settings of our nginx-server running in front of cloud.seatable.io.
The DNS-Servers did not change, yet. We will switch them to exoscale within the next days.
Thanks for your followup.
I just checked again and the problem persists. Not only when accessing my own tables, but just trying to access www.seatable.io results in the above error message.
Hey Peter,
I have absolutely no idea what might cause this issue. Our certificate is completely legit and trustworth.
Here just a screenshot from ssllabs:
Do you have any more infos about your company network. Do you use any kind of proxy or application firewall that malformats the ssl certificates or has additional checks? I ask because you wrote that the problem only occurs from your company network, right?
I don’t know the details of the infrastructure, other than they use Firewalls and Proxies and do some SSL interception on the BlueCoats.
It is a big company and I don’t have info about details or if there was any change in the infra a few days ago. As far as I can see I am experiencing this behavior only with the Seatable site.
A few months ago whe had simular problems accessing tables on a competitor which were hosted by them but we had our own domain name accessing it. Same error, only went away when we changed the DNS config to not use cloudflare as DNS servers. They used Cloudflare for their SSL connection.
I think I will create a ticket at the IT department and see if they can help me. (no high hopes).
The seatable websites were categorized as suspicious bij de Bluecoat proxy servers of the company network (dutch government). The IT department placed a request to assign them to another category and now they work fine!
