Hi,
I'm running the latest nightly LMS 7.9.2 on Windows Server 2012R2. It gets the fixed IP 192.168.1.2 from the router.
For example, the UPNP bridge plugin knows about this IP
but further down the log, it seems that the CLI on port 9090 is not aware.
The only peculiar thing about the machine on which the server runs is that there are 4 Ethernet ports on the motherboard, of which only one is connected. I've specifically opened up port 9090 on the motherboard and things like iPeng has always worked fine.
How can I trouble shoot this? Philippe44 suggests this may be leading to problems with his plugin.
I'm running the latest nightly LMS 7.9.2 on Windows Server 2012R2. It gets the fixed IP 192.168.1.2 from the router.
For example, the UPNP bridge plugin knows about this IP
Code:
[18-06-03 21:05:45.2127] Plugins::UPnPBridge::Settings::handler2 (257) reading: upnp_socket 192.168.1.2
[18-06-03 21:05:45.2131] Plugins::UPnPBridge::Settings::handler2 (257) reading: log_limit -1Code:
[18-06-03 21:25:51.3718] Slim::Plugin::CLI::Plugin::cli_socket_accept (227) Begin Function
[18-06-03 21:25:51.4576] Slim::Plugin::CLI::Plugin::cli_socket_accept (250) Access to CLI is restricted to the local network or localhost: 169.254.148.151The only peculiar thing about the machine on which the server runs is that there are 4 Ethernet ports on the motherboard, of which only one is connected. I've specifically opened up port 9090 on the motherboard and things like iPeng has always worked fine.
How can I trouble shoot this? Philippe44 suggests this may be leading to problems with his plugin.