I am running NIS and NCC on a linux machine and wanted to connect to the NCC web interface from my windows laptop through the local network.
When I connect to 192.168.178.70:8989 (which is the IP of the machine where NCC is running) firefox then tries to connect to http://127.0.0.1:8989/ncc/web/index.html which of course fails.
When I connect to 192.168.178.70:8989/ncc/web/index.html it works fine.
Is that a bug or is this normal behaviour and I am just not understanding something?
1 Like
I am running NIS and NCC on a linux machine and wanted to connect to the NCC web interface from my windows laptop through the local network.
When I connect to 192.168.178.70:8989 (which is the IP of the machine where NCC is running) firefox then tries to connect to http://127.0.0.1:8989/ncc/web/index.html which of course fails.
When I connect to 192.168.178.70:8989/ncc/web/index.html it works fine.
Is that a bug or is this normal behaviour and I am just not understanding something?
Looks like NCC is redirecting automatically to http://127.0.0.1:8989/ncc/web/index.html as soon as you hit 8989.
Just a guess though.
If I'm right NCC would need to be adapted to mak eit possible for people to access ncc remotely without having to use the entire url.
I am running NIS and NCC on a linux machine and wanted to connect to the NCC web interface from my windows laptop through the local network.
When I connect to 192.168.178.70:8989 (which is the IP of the machine where NCC is running) firefox then tries to connect to http://127.0.0.1:8989/ncc/web/index.html which of course fails.
When I connect to 192.168.178.70:8989/ncc/web/index.html it works fine.
Is that a bug or is this normal behaviour and I am just not understanding something?
This is configurable in ncc/config.properties
I am running NIS and NCC on a linux machine and wanted to connect to the NCC web interface from my windows laptop through the local network.
When I connect to 192.168.178.70:8989 (which is the IP of the machine where NCC is running) firefox then tries to connect to http://127.0.0.1:8989/ncc/web/index.html which of course fails.
When I connect to 192.168.178.70:8989/ncc/web/index.html it works fine.
Is that a bug or is this normal behaviour and I am just not understanding something?
This is configurable in ncc/config.properties
neat....didn't know that.
I am running NIS and NCC on a linux machine and wanted to connect to the NCC web interface from my windows laptop through the local network.
When I connect to 192.168.178.70:8989 (which is the IP of the machine where NCC is running) firefox then tries to connect to http://127.0.0.1:8989/ncc/web/index.html which of course fails.
When I connect to 192.168.178.70:8989/ncc/web/index.html it works fine.
Is that a bug or is this normal behaviour and I am just not understanding something?
This is configurable in ncc/config.properties
Ok, thank you!
But why is it like that? In which situations is this behaviour useful?
I am running NIS and NCC on a linux machine and wanted to connect to the NCC web interface from my windows laptop through the local network.
When I connect to 192.168.178.70:8989 (which is the IP of the machine where NCC is running) firefox then tries to connect to http://127.0.0.1:8989/ncc/web/index.html which of course fails.
When I connect to 192.168.178.70:8989/ncc/web/index.html it works fine.
Is that a bug or is this normal behaviour and I am just not understanding something?
This is configurable in ncc/config.properties
Ok, thank you!
But why is it like that? In which situations is this behaviour useful?
I guess it is the standard "protocol" to do it this way. You need a host address and this is how it is configured when it is a local host.
If you request through port 8989, it will call the program located at http://127.0.0.1:8989/ncc/web/index.html. Hence if you want it defined as something else, you need to change the nem.host. Basically there must be an address to point to.
I am running NIS and NCC on a linux machine and wanted to connect to the NCC web interface from my windows laptop through the local network.
When I connect to 192.168.178.70:8989 (which is the IP of the machine where NCC is running) firefox then tries to connect to http://127.0.0.1:8989/ncc/web/index.html which of course fails.
When I connect to 192.168.178.70:8989/ncc/web/index.html it works fine.
Is that a bug or is this normal behaviour and I am just not understanding something?
This is configurable in ncc/config.properties
Ok, thank you!
But why is it like that? In which situations is this behaviour useful?
Since NCC at the moment doesn't support HTTPS, I never make remote connections to it.
I make an SSH tunnel from my PC to my VPS where NIS and NCC are running. So I always access NCC as http://localhost:8989 wherever I am.
I am running NIS and NCC on a linux machine and wanted to connect to the NCC web interface from my windows laptop through the local network.
When I connect to 192.168.178.70:8989 (which is the IP of the machine where NCC is running) firefox then tries to connect to http://127.0.0.1:8989/ncc/web/index.html which of course fails.
When I connect to 192.168.178.70:8989/ncc/web/index.html it works fine.
Is that a bug or is this normal behaviour and I am just not understanding something?
This is configurable in ncc/config.properties
Ok, thank you!
But why is it like that? In which situations is this behaviour useful?
Since NCC at the moment doesn't support HTTPS, I never make remote connections to it.
I make an SSH tunnel from my PC to my VPS where NIS and NCC are running. So I always access NCC as http://localhost:8989 wherever I am.
Ok, but I am accessing it through my local network, so that should not be a problem.
Although it would still be interesting to know how to set up a SSH tunnel...
I am running NIS and NCC on a linux machine and wanted to connect to the NCC web interface from my windows laptop through the local network.
When I connect to 192.168.178.70:8989 (which is the IP of the machine where NCC is running) firefox then tries to connect to http://127.0.0.1:8989/ncc/web/index.html which of course fails.
When I connect to 192.168.178.70:8989/ncc/web/index.html it works fine.
Is that a bug or is this normal behaviour and I am just not understanding something?
This is configurable in ncc/config.properties
Ok, thank you!
But why is it like that? In which situations is this behaviour useful?
Since NCC at the moment doesn't support HTTPS, I never make remote connections to it.
I make an SSH tunnel from my PC to my VPS where NIS and NCC are running. So I always access NCC as http://localhost:8989 wherever I am.
Ok, but I am accessing it through my local network, so that should not be a problem.
Although it would still be interesting to know how to set up a SSH tunnel...
ssh -l root -f server_ip -L 8989:localhost:8989 -N
I guess this is a linux command. But I am running Windows 7 on my laptop. So it is probably a bit more complicated?
Or do I have to type this command at the linux server!?
I guess this is a linux command. But I am running Windows 7 on my laptop. So it is probably a bit more complicated?
Or do I have to type this command at the linux server!?
I guess putty and other software like that can do the same. Just look at them or search google.
Ok, thanks!
Edit: Is it planed to implement https for ncc?
I guess this is a linux command. But I am running Windows 7 on my laptop. So it is probably a bit more complicated?
Or do I have to type this command at the linux server!?
I guess putty and other software like that can do the same. Just look at them or search google.
For the benefit of others this is the guide I followed for using Putty to tunnel a port across the SSH session - http://realprogrammers.com/how_to/set_up_an_ssh_tunnel_with_putty.html
However, I wasn't convinced it work, but then didn't look into it for too long
KC
Thanks for the guide.