Quote:
Originally Posted by tamhas
OK, starting the Content Server and doing the http://192.168.100.4:8080 works.
So, I retried the wireless connection and it didn't work.
So, I tried the browser on 9090 to see if I got the same you did ... and I got a login screen for OpenEdge Management Console (OpenEdge is a software package I develop in, although I don't use the Management Console).
So, I tried starting the wireless connection on 8090 instead and with CC changed correspondingly, it now connects.
... |
Well, this is a bit embarrassing. The clue was in front of me all along but I simply didn't see it. The calibre log contains the following lines:
Code:
Started up in 35.47 seconds with 1173 books
SMART_DEV ( 0.04: 0.042) _attach_to_port try ip address "" on port 9090
SMART_DEV ( 0.18: 0.000) _attach_to_port socket error on port 9090
SMART_DEV ( 0.25: 0.029) _attach_to_port try ip address "" on port 19285
SMART_DEV ( 1.11: 0.811) startup_on_demand listening on port 19285
Note the third line, which says that something else is listening on port 9090.
I also see in the CC debug log:
Code:
2016-06-27 13:28:18.203: WDConnection: MDNS ServiceAdded. name=calibre smart device client (on ***** port 25244), address=192.168.100.4, port=25244
2016-06-27 13:28:20.567: WDConnection: received broadcast response calibre wireless device client (on *****);8080,25244, address 192.168.100.4
Note that the port is not 9090. The reason: when the default port is not available calibre chooses some other port.
Of course, this still leaves us with the question of why it worked in December and stopped working in January.
I suspect that the default setup (no IP address in CC) will work again now that you have it working with a fixed address.
Quote:
Originally Posted by tamhas
Oh, and thanks again for terrific support!
|
You are welcome.