flaxsearch / flaxcode

Automatically exported from code.google.com/p/flaxcode
4 stars 1 forks source link

Server only works from localhost #217

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Install Flax on Windows 2008 Server
2. Networking Configuration is IPV4 based.
3. Even when IPV6 is disabled server still tries to bind to IPV6 address. 
Uses :::1:: by default.
4. Web interface is available only via localhost and not by 127.0.0.1, 
HOSTNAME, or any DNS(A) records that point to that host. Essentially the 
server is only accessible locally via localhost.

What is the expected output? What do you see instead?
When you visit the address mypc.mydomain.local:8090 you should see the 
search interface. Instead a connection error occurs because the server is 
not binding to an IPV4 address as it should.

What version of the product are you using? On what operating system?
Windows 2008 Server (64bit, installed Flax as 32 program), Version 1.0.0

Please provide any additional information below.
There needs to be a method for checking the bindings or else needs to be a 
check to fall back when no IPV6 address is being given. I've gone so far as 
to disable IPV6 in the registry yet the server is still being bound to a V6 
blank IP. You can check it by doing netstat -a.

Original issue reported on code.google.com by jim.for...@gmail.com on 22 Dec 2009 at 4:53

GoogleCodeExporter commented 9 years ago
In the event that anyone is concerned that a firewall is the problem, I have 
reproduced 
this on a server with no antivirus or firewall. The problem is with port 
binding, not 
blocked ports.

Original comment by jim.for...@gmail.com on 22 Dec 2009 at 4:54

GoogleCodeExporter commented 9 years ago
Fixed for now by adding this line to cp.conf. 

server.socket_host = 'WINDOWSPCHOSTNAME'

Still unclear why binding does not work by default. If IPV6 is enabled but no 
IPV6 
address is being assigned by DHCP localhost should still be falling back to 
127.0.0.1. Perhaps this has to do with how MS does IPV6 addressing but there 
still 
needs to be a check of some kind.

Original comment by jim.for...@gmail.com on 22 Dec 2009 at 5:41