View Single Post
Old 12-22-2016, 11:43 AM   #2
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,605
Karma: 204624552
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
The port forwarding needs to be forwarding port 8080 (I believe) to your internal calibre machine's IP. That's if you're connectng to calibre's built-in server. If you're trying to connect to calibre's wireless device service (like with the calibre companion app) then that's a different port.

Another process needs to occassionally test and update your No-IP hostname address (unless you have a static IP that never changes).

The No-IP hostname might not work from behind your own router. The public IP could be sending traffic through your router instead of directly to your local machine.

Try accessing it from outside your own network to determine for sure if it's "working," or not. If it is, then you may need to add your local calibre machine's IP to the hosts file of the machines that need to access it from your own network.

Last edited by DiapDealer; 12-22-2016 at 04:00 PM.
DiapDealer is offline   Reply With Quote