Quote:
Originally Posted by Wryhder
Okay, so I changed the port to 8085 for the content server and gave 8080 to the wireless device. This page (accessing wireless device, 127.0.0.1:8080) loaded like it was the content server, only that my books could not load.
|
The calibre content server stuff is probably in the browser's cache.
The second image says that the request timed out, so it failed to connect instead of connecting and getting "wrong" data.
Quote:
I still couldn't access it from CC or my mobile web browser ("site cannot be reached").
I found these lines in /etc/services/, so that's probably normal?
Code:
http-alt 8080/tcp webcache # WWW caching service
http-alt 8080/udp
BTW, I could access the server just fine from 8085, from CC and pc web browser.
|
I have only one more thing to suggest. Although I have no idea why this would be happening, it is possible that the WD connection "listen" is somehow getting confused in python or in linux. One possible fix: tell calibre to listen on a specific IP address, in your case the public IP address of the laptop 192.168.0.100. To do this, in calibre go to Preferences / Plugins. Search for SmartDevice. Click on "Customize Plugin". Paste the laptop's IP address into the "Use this IP address" box. Press OK until you are back to calibre, then stop and restart the wireless device. At this point connecting from a web browser on the laptop should not work. Connecting from your device might work.