KRLS

I would like to join the club. This new interactive window is useless because gives no info about the connection being established to create a proper rule. Also in recent versions ESET started blocking connections without any warning or log. You enable firewall no connection, you disable firewall everything works. And no interactive prompt ask for the connection.

That is why It was working the week before I opened the topic and then stopped working. I wasn't aware of the cert, because the solution proposed in the "old" topic I mentioned (linked) excluded spideroak.exe to be analized by ESET. When I triggered the interactive mode then ESET prompted about the certificate and I could see what was going on. No because the problem was on their side, not on "your filter" blocking something. All this coincidentally appeared in a period where they pulled out the client for downloading... Now the problem is solved and I'm looking for another cloud provider. Sorry for pointing ESET as the source of the problem and thank you for your time.

My apologies Marcos. I tested everything last week and I didn't find the time to report/ try to solve it until yesterday. What changed? Look at the dates (dd/mm/yyyy). I think this image is self explanatory in many ways. After removing all certificates/applications from the lists, all exclusions and activated interactive mode, this popped up: Zero conf? Just for the search engines: SpiderOak is using the default Kubernetes Ingress Controller Fake Certificate for SpiderOakONE in the production version of the software.

Nothing pops up. I deleted firefox.exe spideroak.exe, from the rules to force it pop up just in case: Attatched video as proof. When I try to generate the link nothing pops up with and without automatic rules on the list. Firewall its allways in interactive btw (you can probably see that from the logs). 2022-06-14 12-47-50.zip

Logging was active while I tried to generate a shared link from windows explorer an afterwards inside the spideroak client itself. Diagnostics.zip eis_logs.zip

I have the same problem as in: Which is: when I try to create a shared file or folder (requires login) i get the following error: The solution proposed in the topic didn't work for me, maybe because its 8 years old and there is another module interfering with the bypass. I've tried this: Disabling all ESET modules don't allow me to log in /share files, Uninstalling ESET allowed me, so its clearly ESET blocking something. For these tests spideroak has full in/out connections permissions on the firewall.