Closed danparker92 closed 12 years ago
What do you see when you open http://127.0.0.1:9104 in the browser?
Also, see https://github.com/NV/chrome-devtools-autosave/wiki/Troubleshooting
It says it is running well. It hasn't been working for two days but literally this second has started. Thanks anyway, problem solved :)
On 12 Mar 2012, at 12:15, Nikita Vasilyev wrote:
What do you see when you open http://127.0.0.1:9104 in the browser?
Also, see https://github.com/NV/chrome-devtools-autosave/wiki/Troubleshooting
Reply to this email directly or view it on GitHub: https://github.com/NV/chrome-devtools-autosave/issues/35#issuecomment-4450502
Okay it's started producing the same error message again just randomly. I haven't changed any settings, terminal still says it is running on 127.0.0.1:9104! But if i run that address in the browser it writes "Oops! Google Chrome could not connect to 127.0.0.1:9104" Any suggestions?
Hm, that’s weird. Reopening issue.
Removed the extension Installed from fresh Ran terminal commands Working (y)
hello, i am having issue with Dev auto save. it says Autosave Server doesn't run on http://127.0.0.1:9104 and when i run http://127.0.0.1:9104 it says ""Oops! Google Chrome could not connect to 127.0.0.1:9104"" and i re-installed it twice. i am using it on windows 7
1) Go to CMD window and type autosave. 2) That should boot up autosave. 3) go to http://127.0.0.1:9104 - you should see a line of text saying "DevTools Autosave 1.0.0" - That means server is running. 4) Try Chrome's inspect element tool. 5) Keep the CMD window open just in case.
I've completed all the steps correctly and am receiving " DevTools Autosave 0.3.2 is running on http://127.0.0.1:9104 " Perfect. But when i do try and edit in Chrome (17.0.963.79) I receive a pop-up in the top right reading " DevTools Autosave Server doesn't run on http://127.0.0.1:9104/save' " This is running on Mac OSX 10.6.8