View Single Post
Old 04-21-2024, 02:49 PM   #7
jmurphy
Connoisseur
jmurphy ought to be getting tired of karma fortunes by now.jmurphy ought to be getting tired of karma fortunes by now.jmurphy ought to be getting tired of karma fortunes by now.jmurphy ought to be getting tired of karma fortunes by now.jmurphy ought to be getting tired of karma fortunes by now.jmurphy ought to be getting tired of karma fortunes by now.jmurphy ought to be getting tired of karma fortunes by now.jmurphy ought to be getting tired of karma fortunes by now.jmurphy ought to be getting tired of karma fortunes by now.jmurphy ought to be getting tired of karma fortunes by now.jmurphy ought to be getting tired of karma fortunes by now.
 
Posts: 98
Karma: 1133068
Join Date: Sep 2007
Device: ipaq
Quote:
Originally Posted by LazyGirl View Post
I'm having the same issue. I can only access the content server on the device which is running calibre (desktop PC), using the address provided in the user manual for this purpose (http://127.0.0.1:8080 - I have no clue if these numbers are unique to me or the same for all users).

Previously I've been able to access the content server from other devices on my home network. (My ISP doesn't allow port-forwarding so I have no experience connecting from a different network.)

Now, when I try to access the server from a different device on the same network (android phone), by using the IP address listed by the "stop content server" button, I get ERR_CONNECTION_TIMED_OUT messages.

The IP address that is populated in the user manual has a different host ID, and trying that one results in the message ERR_ADDRESS_UNREACHABLE.

Not sure if this matters or not, but clicking "Visit Content Server in browser" under the "Connect/Share" button no longer links to http://127.0.0.1:8080/ but instead http://[::1]:8080/. It appears to work the same.

In case it isn't obvious, I know very little about this but I can follow directions.
You need to use the address that shows up in "stop content server", 127.0.0.1 is only valid on the local device.

Try browsing using the network name of your pc instead of the address. If you don't know the name, log in to the PC, open a command prompt and type 'ping -a 127.0.0.1' The response will have the network name of the pc in the first line. Then from another device, browse to HTTP://PCNAME:8080
jmurphy is offline   Reply With Quote