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
Lost bridge when changed port #244
Comments
How is your system setup on what type of device and what is the ip of that device? |
The ip is 192.168.0.12 and it is setup up on a qnap nas running on ubuntu through terminal |
Still not sure what is wrong as the bridge says it is listening on all interfaces. This sounds like os setup issues and I'm not familiar with this setup. |
i used to login by going to 192.168.0.99:8080. i then changed web server port under bridge control from 8080 to 80 and hit save. now and i can no longer get to the web interface using 192.168.0.99:8080 or 192.168.0.99:80 i will post what terminial shows below but have noticed this: would the best bet be to refresh ubuntu and re-install everything from fresh? |
dmin@ubuntu_1604: |
Well this says it all: 2016-11-16 18:34:25,879 [Thread-0] INFO spark.webserver.JettySparkServer - >> Listening on 0.0.0.0:80 You either have some other webserver running on port 80 or you do not have access to port 80. Google this to help you on QNAP as this has been discussed before. |
I suspect you are running this as a user. Ports under 1000 are only allowed to be opened by root. Either change the port to something like 8081 or run the program as root |
Is there a guide on how to do this? As i am unable to acces the web interface Cheers |
To run as root: start the program with sudo. E.g. "sudo ./starthabridge.sh" To change the port, add a command line flag. It is detailed in the README.
|
I changed the bridge port through the web interface to 80 but not i cannot access it anymore when tupying the web address in the browser using the original 8080 or 80. not sure if there is a way i can search for where it has gone?
On the bridge terminal it says listening on 0.0.0.0:80
The text was updated successfully, but these errors were encountered: