Skip to content
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

open to the network / world #29

Closed
vo1pwf opened this issue Apr 2, 2015 · 1 comment
Closed

open to the network / world #29

vo1pwf opened this issue Apr 2, 2015 · 1 comment
Assignees
Labels

Comments

@vo1pwf
Copy link

vo1pwf commented Apr 2, 2015

I can access it via local lan, I was going to put it on the internet, I opened up the port 8100
and to ease usage I removed the following from the conf file
root_cap=

but I get as far as:
Loading client…
Loading plugins…
Connecting to server…

is there something else I can do to let it through??

@kpreid
Copy link
Owner

kpreid commented Apr 3, 2015

You need to open the port 8101 as well, for the WebSocket data connections. Any time startup gets stuck at that point there's a problem with the WebSocket connection.

If you had opened the JavaScript console in the browser you would have seen a connection error. (I'm aware that having an error message actually on-screen by default would be helpful.)

@kpreid kpreid closed this as completed Apr 3, 2015
@kpreid kpreid added the support label Apr 3, 2015
@kpreid kpreid self-assigned this Apr 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants