# At Recovery Homey Not Responding -- RootCause: CORS policy enforced by Chrome (v94 and higher) -- How to disable CORS **URL:** \ **Category:** Questions & Help\ **Created:** [November 2, 2021, 4:34pm UTC](https://community.homey.app/t/at-recovery-homey-not-responding-rootcause-cors-policy-enforced-by-chrome-v94-and-higher-how-to-disable-cors/54166 "2021-11-02T16:34:06Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![MCoelman](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mcoelman/32/34878_2.png) [@MCoelman](https://community.homey.app/u/MCoelman)\ **Post date:** [November 2, 2021, 4:34pm UTC](https://community.homey.app/t/at-recovery-homey-not-responding-rootcause-cors-policy-enforced-by-chrome-v94-and-higher-how-to-disable-cors/54166/1 "2021-11-02T16:34:06Z")
Hi all, I´ve had troubles recovering my Homey. I could see packets exchanged to & from my Homey, but recovery procedure did not progress(halted) after “Connect to HomeySetup” & changing towards the “HomeySetup XXXX” wifi. A support request at athom/homey is still pending. As they did not come back yet, i was eager to find out more myself… Further investigation showed, Chrome CORS´s policy was blocking access towards Homey: _Access to XMLHttpRequest at ‘[http://10.199.198.1/system](http://10.199.198.1/system)’ from origin ‘[http://setup.athom.com](http://setup.athom.com)’ has been blocked by CORS policy: The request client is not a secure context and the resource is in more-private address space `private`._ Reading up, Chrome has changed its "private network access " policies (CORS-RFC1918: interaction local, private & public networks), enforcing https…However, the current Homey recovery still uses http… Guess this issue must hit more people trying to recover Homey with a new Chrome (v94 and higher) instance… My work around consisted of 2 parts: 1. Run chrome browser without CORS 2. Alter chrome flags: Set “Block insecure private network requests” to “disabled” The full detailed solution including reference links is outlined in next posts (1st post within this community only allows upto 2 embedded links…I have more). This worked for me:-)… Hope it works for you too:-) Cheers, Marcel Coelman. Note: Im not sure if step 1 is necessary…In trying to find a solution I started with step 1… ![Connect to HomeySetup not working -- incl Console](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/8/f844be38e89080e34731180a819fe67e6edde0c5.png) ---
**Author:** ![MCoelman](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mcoelman/32/34878_2.png) [@MCoelman](https://community.homey.app/u/MCoelman)\ **Post date:** [November 2, 2021, 4:35pm UTC](https://community.homey.app/t/at-recovery-homey-not-responding-rootcause-cors-policy-enforced-by-chrome-v94-and-higher-how-to-disable-cors/54166/2 "2021-11-02T16:35:09Z")
1. Run Chrome browser without CORS a. Right click on desktop, add new shortcut. b. Add the target as “[PATH\_TO\_CHROME]\chrome.exe” --disable-web-security --disable-gpu --user-data-dir=C:/tmp/chrome (note: Win 10 approach, directory to be aligned with OS) c. Click OK. Alternatively run/execute from CMD line: “[PATH\_TO\_CHROME]\chrome.exe” --disable-web-security --disable-gpu --user-data-dir=C:/tmp/chrome (See: [crunchify.com/how-to-fix-access-control-allow-origin-issue-for-your-https-enabled-wordpress-site-and-maxcdn/](http://crunchify.com/how-to-fix-access-control-allow-origin-issue-for-your-https-enabled-wordpress-site-and-maxcdn/)) ---
**Author:** ![MCoelman](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mcoelman/32/34878_2.png) [@MCoelman](https://community.homey.app/u/MCoelman)\ **Post date:** [November 2, 2021, 4:35pm UTC](https://community.homey.app/t/at-recovery-homey-not-responding-rootcause-cors-policy-enforced-by-chrome-v94-and-higher-how-to-disable-cors/54166/3 "2021-11-02T16:35:46Z")
1. Alter chrome flags: Set “Block insecure private network requests” to “disabled” a. Type within chrome bar: chrome://flags/ b. Next look for “Block insecure private network requests” and set this to “disabled” c. restart browser (See: answer of [android - Chrome future update Restrict "private network requests". Will it affect scanning hardware on devices that make local connections? - Stack Overflow](https://stackoverflow.com/questions/67294093/chrome-future-update-restrict-private-network-requests-will-it-affect-scannin)) ![Chrome disable Block insecure private network requests](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/a/2a72131a869b1a4bf1a22e4a56f28b356a29b0f5.png) ---
**Author:** ![MCoelman](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mcoelman/32/34878_2.png) [@MCoelman](https://community.homey.app/u/MCoelman)\ **Post date:** [November 2, 2021, 4:39pm UTC](https://community.homey.app/t/at-recovery-homey-not-responding-rootcause-cors-policy-enforced-by-chrome-v94-and-higher-how-to-disable-cors/54166/4 "2021-11-02T16:39:05Z")
Chrome report wrt CORS: > **[Private Network Access update: Introducing a deprecation trial - Chrome...](https://developer.chrome.com/blog/private-network-access-update/)** > > Chrome is deprecating access to private network endpoints from non-secure public websites in Chrome 94 as part of the Private Network Access specification. Read on for recommended actions. ---
**Author:** ![MCoelman](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mcoelman/32/34878_2.png) [@MCoelman](https://community.homey.app/u/MCoelman)\ **Post date:** [December 15, 2021, 9:47pm UTC](https://community.homey.app/t/at-recovery-homey-not-responding-rootcause-cors-policy-enforced-by-chrome-v94-and-higher-how-to-disable-cors/54166/6 "2021-12-15T21:47:12Z")
Great to read it worked for you too 😀 ---
**Author:** ![Dijker](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@Dijker](https://community.homey.app/u/Dijker)\ **Post date:** [March 1, 2022, 6:19pm UTC](https://community.homey.app/t/at-recovery-homey-not-responding-rootcause-cors-policy-enforced-by-chrome-v94-and-higher-how-to-disable-cors/54166/7 "2022-03-01T18:19:37Z")
> [@MCoelman](#): > > Type within chrome bar: chrome://flags/ from now you finally can use the Mobile App > [@\[HowTo\]\[Pro\] Restarting Homey Pro to Recovery Mode - Adv. Options From Mobile](https://community.homey.app/t/howto-pro-restarting-homey-pro-to-recovery-mode-adv-options-from-mobile/61222): > > This option is only for Homey (Pro) models “Early 2016”, “Early 2018” and “Early 2019” so Only the White Ball’s Sometimes you need the extra options, things hidden for normal use, for example: Full Firmware download Complete Reset to sell your old Homey Or maybe you just want to change Homey’s WiFi. There are now a couple of extra options in the mobile Apps, so no need to use an FireFox or Chome Browser with flags enabled to press the Alt- key on your keyboard. Just use your App from no…