Failed to fetch error with MS Edge Extension #94

Closed
opened 2026-02-20 07:36:01 -05:00 by deekerman · 6 comments
Owner

Originally created by @ghost on GitHub (Sep 18, 2018).

I am running the latest Windows 10 Pro v1803 build 17134.285, and Latest MS Edge v42.17134.1.0. This is installed on a Qnap NAS. I am pretty new to Qnap/Docker so I'm not sure how to provide any more information. Other than this issue, it is working on all my other devices meaning apps/extensions work fine.

Originally created by @ghost on GitHub (Sep 18, 2018). I am running the latest Windows 10 Pro v1803 build 17134.285, and Latest MS Edge v42.17134.1.0. This is installed on a Qnap NAS. I am pretty new to Qnap/Docker so I'm not sure how to provide any more information. Other than this issue, it is working on all my other devices meaning apps/extensions work fine.
Author
Owner

@shauder commented on GitHub (Sep 19, 2018):

I am able to reproduce this by running a local copy and trying to log into it via the edge extension. I can log in via the Windows desktop app but not through the edge extension. I am able to use the edge extension with my main vault that runs behind a reverse proxy and https via letsencrypt.

I then put my local copy also behind a reverse proxy and it seems to work better. Even with http and not https. I am not familiar with extensions at all so I may have to pass this on to someone else who may have experience with them, Seems like its some weird "security" feature of edge blocking the communication with the local server. There are no logs on the back-end as if it never tried to talk.

@shauder commented on GitHub (Sep 19, 2018): I am able to reproduce this by running a local copy and trying to log into it via the edge extension. I can log in via the Windows desktop app but not through the edge extension. I am able to use the edge extension with my main vault that runs behind a reverse proxy and https via letsencrypt. I then put my local copy also behind a reverse proxy and it seems to work better. Even with http and not https. I am not familiar with extensions at all so I may have to pass this on to someone else who may have experience with them, Seems like its some weird "security" feature of edge blocking the communication with the local server. There are no logs on the back-end as if it never tried to talk.
Author
Owner

@dani-garcia commented on GitHub (Sep 19, 2018):

I think the Windows 10 apps have communication blocked with localhost by default. There is a setting to change it for edge in the developer settings but as edge extensions are counted as separate apps, maybe that needs to be changed for the bitwarden extension too?

https://stackoverflow.com/questions/30334289/cant-open-localhost-in-microsoft-edge-project-spartan-in-windows-10-preview

@dani-garcia commented on GitHub (Sep 19, 2018): I think the Windows 10 apps have communication blocked with localhost by default. There is a setting to change it for edge in the developer settings but as edge extensions are counted as separate apps, maybe that needs to be changed for the bitwarden extension too? https://stackoverflow.com/questions/30334289/cant-open-localhost-in-microsoft-edge-project-spartan-in-windows-10-preview
Author
Owner

@ghost commented on GitHub (Sep 19, 2018):

That option is already enabled.


From: Daniel García notifications@github.com
Sent: Wednesday, September 19, 2018 6:26:57 AM
To: dani-garcia/bitwarden_rs
Cc: diehardbattery; Author
Subject: Re: [dani-garcia/bitwarden_rs] Failed to fetch error with MS Edge Extension (#192)

I think the Windows 10 apps have communication blocked with localhost by default. There is a setting to change it for edge in the developer settings but as edge extensions are counted as separate apps, maybe that needs to be changed for the bitwarden extension too?

https://stackoverflow.com/questions/30334289/cant-open-localhost-in-microsoft-edge-project-spartan-in-windows-10-previewhttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstackoverflow.com%2Fquestions%2F30334289%2Fcant-open-localhost-in-microsoft-edge-project-spartan-in-windows-10-preview&data=02%7C01%7C%7C107573dbc0ce4ebd6c7208d61e22cf8e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636729532183005674&sdata=rlpom9nGjm7T%2FZRrZEleXHIp6TF1ysMgMrinyjGoUik%3D&reserved=0


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdani-garcia%2Fbitwarden_rs%2Fissues%2F192%23issuecomment-422765026&data=02%7C01%7C%7C107573dbc0ce4ebd6c7208d61e22cf8e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636729532183005674&sdata=oOld%2Bi7rBVaDpiw5LE8uMShouTpNQ7VnE39FJIyY%2Fmo%3D&reserved=0, or mute the threadhttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FApH9vk_s8I-HerwezdxTajayOLdEDT-fks5ucioBgaJpZM4WvT_M&data=02%7C01%7C%7C107573dbc0ce4ebd6c7208d61e22cf8e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636729532183005674&sdata=G6zWFj%2BB28EMk3YZH6K%2BKFvC8sfjMuIVgdi5iBYybvo%3D&reserved=0.

@ghost commented on GitHub (Sep 19, 2018): That option is already enabled. ________________________________ From: Daniel García <notifications@github.com> Sent: Wednesday, September 19, 2018 6:26:57 AM To: dani-garcia/bitwarden_rs Cc: diehardbattery; Author Subject: Re: [dani-garcia/bitwarden_rs] Failed to fetch error with MS Edge Extension (#192) I think the Windows 10 apps have communication blocked with localhost by default. There is a setting to change it for edge in the developer settings but as edge extensions are counted as separate apps, maybe that needs to be changed for the bitwarden extension too? https://stackoverflow.com/questions/30334289/cant-open-localhost-in-microsoft-edge-project-spartan-in-windows-10-preview<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstackoverflow.com%2Fquestions%2F30334289%2Fcant-open-localhost-in-microsoft-edge-project-spartan-in-windows-10-preview&data=02%7C01%7C%7C107573dbc0ce4ebd6c7208d61e22cf8e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636729532183005674&sdata=rlpom9nGjm7T%2FZRrZEleXHIp6TF1ysMgMrinyjGoUik%3D&reserved=0> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdani-garcia%2Fbitwarden_rs%2Fissues%2F192%23issuecomment-422765026&data=02%7C01%7C%7C107573dbc0ce4ebd6c7208d61e22cf8e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636729532183005674&sdata=oOld%2Bi7rBVaDpiw5LE8uMShouTpNQ7VnE39FJIyY%2Fmo%3D&reserved=0>, or mute the thread<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FApH9vk_s8I-HerwezdxTajayOLdEDT-fks5ucioBgaJpZM4WvT_M&data=02%7C01%7C%7C107573dbc0ce4ebd6c7208d61e22cf8e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636729532183005674&sdata=G6zWFj%2BB28EMk3YZH6K%2BKFvC8sfjMuIVgdi5iBYybvo%3D&reserved=0>.
Author
Owner

@shauder commented on GitHub (Sep 19, 2018):

I found how to debug an extension in edge. Seems like we are on the right track with what the issue is. I think your best bet will be running it behind a reverse proxy. You'll also get websockets this way if you configure it right.

I messed around with some settings and I am able to get edge to show the local vault but I am unable to get the extension to communicate still.

background.html (1,1)

 HTML1527: DOCTYPE expected. Consider adding a valid HTML5 doctype: "!DOCTYPE html>".
background.html (1,1)

 API Call 'browserAction.setIcon' has been bridged to another Edge API: browserAction.setIcon with absolute path

 CONSOLE21301: serviceWorker.getRegistrations is rejected due to unsecure context or host restriction in ms-browser-extension://EdgeExtension_8bitSolutionsLLCbitwardenFreePasswordManager_h4e712dmw3xyy/background.html.
@shauder commented on GitHub (Sep 19, 2018): I found how to debug an extension in edge. Seems like we are on the right track with what the issue is. I think your best bet will be running it behind a reverse proxy. You'll also get websockets this way if you configure it right. I messed around with some settings and I am able to get edge to show the local vault but I am unable to get the extension to communicate still. ```HTML1300: Navigation occurred. background.html (1,1) HTML1527: DOCTYPE expected. Consider adding a valid HTML5 doctype: "!DOCTYPE html>". background.html (1,1) API Call 'browserAction.setIcon' has been bridged to another Edge API: browserAction.setIcon with absolute path CONSOLE21301: serviceWorker.getRegistrations is rejected due to unsecure context or host restriction in ms-browser-extension://EdgeExtension_8bitSolutionsLLCbitwardenFreePasswordManager_h4e712dmw3xyy/background.html.
Author
Owner

@shauder commented on GitHub (Sep 19, 2018):

@diehardbattery try running this (restart edge after and run in administrator powershell):

https://stackoverflow.com/questions/32384571/why-does-microsoft-edge-open-some-local-websites-but-not-others-where-the-doma

Run:
CheckNetIsolation LoopbackExempt -a -n="Microsoft.MicrosoftEdge_8wekyb3d8bbwe"

This fixed it for me in my test environment

@shauder commented on GitHub (Sep 19, 2018): @diehardbattery try running this (restart edge after and run in administrator powershell): https://stackoverflow.com/questions/32384571/why-does-microsoft-edge-open-some-local-websites-but-not-others-where-the-doma Run: `CheckNetIsolation LoopbackExempt -a -n="Microsoft.MicrosoftEdge_8wekyb3d8bbwe"` This fixed it for me in my test environment
Author
Owner

@dani-garcia commented on GitHub (Dec 13, 2018):

This hasn't had activity in some time, so I'm closing it now.
If this is still an issue, please reopen it.

@dani-garcia commented on GitHub (Dec 13, 2018): This hasn't had activity in some time, so I'm closing it now. If this is still an issue, please reopen it.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/vaultwarden#94
No description provided.