-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remote connections don’t work #13
Comments
Thanks for looking in to this! Feel free to submit a PR |
Thanks @turbio. Continuing to make notes here as I poke at this in my spare time. I note two error messages: The first doesn't really seem to be related at all. I get this when I exit vim after bracey has been started:
The second is what is logged when attempting to open the address via remote browser:
Feel free to chime in if you have a suggestion of what to investigate based on this. I'll just keep poking at it here and there. I'm a little slow going cos I'm pretty rusty as a developer, and I'm also doing 100% of my development work on an iPad—mostly for the challenge of it :) |
This problem was raised a while back. I had a similar situation recently. I download the plugin on my laptop and later on downloaded it on my PC. The first time I was way more attentive on what I was doing but the second time around I forgot to do an important thing which generated the exact same error message. |
I’m trying to debug why remote connections aren’t working for me in bracey. In the process, I’ve discovered at least one bug (#12) which got me a little farther.
I’m going to share what I learn while attempting to debug here.
For reference, I’m using the following config:
When starting
:Bracey
, I get:--allow-remote-web
didn't show up in the args until fixing #12, so that's some progress.I can confirm that bracey' s node server is running and listening on 8080:
When visiting
http://[ip-address]:8080
, I note in my browser dev tools that it performs a 302 redirect and the address changes tohttp://[ip-address]:8080/projectfolder/index.html
and then fails.When I look at vim, I note an error message:
I check netstat again and find that it's no longer listening.
I check Bracey’s default configured log path and there is nothing of note logged there.
So at some point, it's hitting that redirect and then failing. I'll probably keep digging at this as I have time.
The text was updated successfully, but these errors were encountered: