UserAgent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36

Steps to reproduce the problem:
1. Run program, eg node server.js --inspect
2. On the browser, open chrome-devtools using the Remote Target link in the chrome://inspect/#devices page
3. Set breakpoints at points known to fire
4. Refresh page that will execute the node server.js code that has the breakpoints

What is the expected behavior?
Debugger should stop on breakpoints.

What went wrong?
Debugger does not stop on breakpoints. Page is served as expected without interruption from breakpoints.

Did this work before? Yes What ever I had before v66. I assume it was v65. How can I know?

Chrome version: 66.0.3359.139  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

Yesterday I was debugging fine. Today I booted, opened Chrome to the new version 66, and stopping on breakpoints no longer works. My node version is v6.11.2. My colleague has node v8.10.0 and Chrome 66 and his debugging doesn't stop on breakpoints either. Another colleague still has Chrome v65 and his works fine.