Proxy injection failed.

[MaxPleaner]

You can see the error here:

It says 'Proxy injection failed". I don't know what it means, and I don't have any errors in my dev console or my terminal tab (webpack).

Chrome version Version 56.0.2924.76 Built on Ubuntu , running on Ubuntu 16.04 (64-bit)

[posva]

Hey, can you boil down the error and provide a repro using this template?
Thanks!

[rwlinda]

I'm having the same issue. I worked on Vue locally, but have put the code in a Java-based project (with .jsp-files) and since then I get this message. Like the OP, there're no errors or any other pointers to look for the issue. So, my bet is that it's not a Vue thing, but the environment in which its being used. If I find out the issue, I'll come back here...

[MaxPleaner]

When I got this error I was proxying my Rack server (port 3000) to a Webpack server (port 8080). That was my attempt to have the frontend and api running on the same host so that I would be able to set cookies. This was buggy for reasons other than the error in Vue dev tools, so I ended up ditching this idea and am hosting the two apps separately now. The error "proxy injecion failed" is gone.

…

On Fri, Mar 10, 2017 at 4:12 AM, rwlinda ***@***.***> wrote: I'm having the same issue. I worked on Vue locally, but have put the code in a Java-based project (with .jsp-files) and since then I get this message. Like the OP, there're no errors or any other pointers to look for the issue. So, my bet is that it's not a Vue thing, but the environment in which its being used. If I find out the issue, I'll come back here... — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#277 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEzWx78a-8D2r5jsGpZYwFgAvehtyInvks5rkT4dgaJpZM4MWaYb> .

[rwlinda]

We got the issue solved by changing some security settings. The error has nothing to do with Vue. The app worked fine in IE as that browser handles the security policies differently. We have everything working in all browsers now. Sorry, I don't know exactly what settings were changed, but your Vue is most likely just fine

[yyx990803]

Closing since there doesn't seem to be anything actionable now.

[dobromir-hristov]

This error comes up when using devtools with firefox on a hot-reloaded app using Laravel Mix.

[dobromir-hristov]

Ways to fix this:
Restart Firefox (mostly fixes it... rsrly)
This happens to me when:
a) My PC was a sleep for some time
b) When Firefox needs to update it self

[noBlubb]

Same for me - restarting Chrome was all it took

[dengshenkk]

Same for me - restarting Chrome was all it took

this does not work!