IP Address binding local and LAN
Opened this issue · 1 comments
Is it possible to get advice on the configuration of the bob environment to alter both the Localhost and LAN IP Addresses used?
This may be a purely configuration issue,
- To help I believe however its seems perhaps the act of configuring such settings is not being passed through to the the tiddlywiki Node subsystem.
- This request is related to #153 because having to install a new bobexe I need to redo this configuration (which worked previously) but no longer seems possible (Perhaps something has changed in recent updates?)
- Thus I am raising this issue to request your guidance on the appropriate configuration, and perhaps this will help you find a settings bug that is resulting in occasional server crashes.
I would like to have a given Bob server available on a localhost address of 127.0.4.84 (as an example), using port 80 so there is no need to include port in the address. This server would not be made available on the LAN. I have other servers on my computer and sometime which to run more than one bob instance. No port number in the address allows one to use a DNS entry, having to provide a port forces a need to store a URL that includes the port.
I plan to have a separate bob server I run when needed to serve on the LAN
Have a given Bob server available on a localhost address of 127.0.5.84 (as an example), using port 80 so there is no need to include port in the address.
Have that same server available on the LAN at IP Addresses 192.168.1.84 port 80 which is an additional IP on the current computer, but may be moved one day. I would like to avoid using 0.0.0.0 as this appears to bind to all 10 of this computers LAN IP addresses. This works on native "node" by using 192.168.1.84 as the IP Address rather than 0.0.0.0 but seems a problem on Bob.
This would also stop interference with an Apache server on my key IP Address 192.168.1.119, and TiddlyServer on 192.168.1.81
An optional extra would be with this same server if I can also have Bob saver server running on say 192.168.1.85:61192 or 192.168.1.84:61192 at the moment Bob reposts its available on the LAN at the numerically lowest IP Address available.
I am running (check any that apply, put an x inside the [ ] to check a box, like this: [x]):
- Windows
- OSX
- Linux
- Other
and using
- The nodejs version
- The single file executable
Before posting I read issue guidelines and:
- I am using the newest version
- The answer to my question isn't listed in the documentation or this isn't
a question - This is not a duplicate issue
- I have not done anything that required me to set acceptance to
I Will Not Get Tech Support For This
This is why I am asking here.
Thanks
In case it were relevant I get an unexplained console message of
WebSocket error: TypeError: Cannot read property 'fields' of undefined
Regards
Tony