Thread Info
  • State Not Answered
  • +4 person also asked this people also asked this
  • Locked Locked
  • Replies 21 replies
  • Subscribers 20 subscribers
  • Views 7637 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos Network Threat Detection is blocking Cypress automation tool

Adrian Ling

We run Cypress as our web automation tool and as of the past week or two Cypress has been crashing with the error message: Error: read ECONNRESET at TCP.onStreamRead (node:internal/stream_base_commons:211:20)

As I'm not in control of the Sophos Endpoint Agent I was able to get the IT team to give me the tamper password to test disabling the 'Network Threat Protection' once this was done Cypress was able to run the automated tests properly.

(Stack Overflow thread with others reporting issue)

Has something changed recently and is there someway that Sophos can fix this so I don't have to disable the network threat protection? If you need any info or help with this let me know.

Thanks

Adrian



This thread was automatically locked due to age.

Top Replies

  • in reply to Sophos User930 +3

    This seems like a bad solution to disable so many security restraints just to be able to run Cypress. All of my tests have started failing as of recently which has lead me to this forum. We normally develop our tests based on using Chrome, but it looks like now I will have to use Electron until this is fixed/reverted back to how it was previously.

    Is there any ETA on a fix for this issue?

    Jump to answer
  • 0 in reply to Alex Sanders

    2021.3 is the release from last year, not all customers have been migrated to 2022.1.x it yet.  If you're not part of the inital accounts migrated I guess you don't have it yet.

    If you contact Support, they can take your tenant ID, which is on the support page in Sophos Central and requrest it is migrated.

    2022.1.1 is what you need for the 127.0.0.1 exclusion to work, 2022.1.0 will not, I believe 2022.1.1 is going to start rolling out tomorrow for those with access to 2022.1.0 already.

Unfiltered HTML
Share Feedback
×

Submitted a Tech Support Case lately from the Support Portal?

Cookie Information Banner