P D 0 Posted October 23, 2024 Posted October 23, 2024 Hello guys , I have a problem opening Trezor Suite app saying "App can't communicate with device" even if the device is not connected. Till today everything worked fine but the problem starts occuring after my ESET Antivurs updates and want me to allow some permissions which i did . Once i dig deeper realized that Firewall option in the ESET was the problem once i toggle it off Suite immediately connects . Do you have any idea why this starts causes this issue given the fact it worked fine till today ? Any idea how to fix it with my Firewall options is on ? Thank you in advance !
Administrators Marcos 5,739 Posted October 23, 2024 Administrators Posted October 23, 2024 If you have the latest ESET CyberSecurity 8.2.800.0 installed, does the issue go away if you temporarily uninstall it and return as soon as you install it from scratch with default settings? If so, please collect logs as per the instructions at https://support.eset.com/en/kb3404, open a ticket with your local ESET distributor and supply them with the generated archive.
P D 0 Posted October 23, 2024 Author Posted October 23, 2024 Hello again . I just tried full preinstallation on ESET but the problem still persist .
P D 0 Posted October 23, 2024 Author Posted October 23, 2024 (edited) Also I tried several times with restarting the pc and notice something strange that sometimes the app starts running while FIrewall is on but also it doesnt probably around 50/50 . Edited October 23, 2024 by P D
Administrators Marcos 5,739 Posted October 23, 2024 Administrators Posted October 23, 2024 Please raise a support ticket and provide step-by-step instructions how to reproduce it. Also mention that you were not able to 100% reproduce it but after temporarily uninstalling the latest version the issue didn't occur.
ESET Staff Robertos 76 Posted October 23, 2024 ESET Staff Posted October 23, 2024 Hello, go to log section in main GUI, select firewall logs and look if you could see blocked communication for problematic application. If you see it, probably it is inbound communication, you can create allowing inbound communication for that application directly from logs using context menu by right click on row log of that application. Or if you are not interested in what this app is doing you can find problematic application in Tools->Application section of main GUI if it is running. Again using context menu you can allow inbound for that application. Or go to Applications folder in Finder, right click on problematic application and allow inbound for it by Finder context menu. If you application is outside /Applications, you must open your parent folder in Finder. Created application rules could be managed then in product preferences in Firewall sub-sheet Application rules. You can read small info text in preferences to know how FW is working, but it is very simple: if application has defined rule that rule is used by firewall in filtering application's communication. By default, e.g. clean installation, there is not application rules. Some application rules could exist if product was upgraded from ECSMPro V6. Simple V6 FW application rules are migrated to v8 during upgrade process. If application has not defined rule for it, fallback rules are applied for it. What fallback rules are you can see in firewall setup -> Fallback rules sheet. You can tweak it as you wish, by default all outbound communication is allowed and only inbound to Apple binaries are allowed. We recommend to allow inbound only for 3rd applications you trust. If allowing inbound does not fix your problem then raise support ticket as Marcos advised you before.
Recommended Posts