Calibre Server IP Address

[dbender54]

When I click the "Connect/Share" icon on the toolbar, what IP address should it show for the content server? Should it show 127.0.0.1:Port# or should it show the internal IP address of the computer (ie. 192.x.x.x) and port number I've assigned? The port number I setup for port forwarding is the same port I specified in Preferences for 'Share -->Sharing Over the Net" under server port. I can connect to the server via the internet and it shows my library, so I know that port I assigned to be forwarded to the Calibre server is correct.

The Wireless device connection shows the internal IP address and the port and I can connect as a wireless device, but I cannot connect to the Content Server (Content Server sharing is started). The Wireless Sharing dialog under Connect/Shares hows the internal network IP address of the Calibre server and port 9090.

I've restarted both the application (Calibre) and the computer (Mac Mini), started and stopped the Calibre server.

Suggestions?

[eschwartz]

It should show the internal network IP address.

Can you connect to 192.x.x.x via the web browser on your phone? If so, and CC cannot connect, the problem lies there, not in calibre.

[dbender54]

Yes. When using my cell phone on my local area network, using wi-fi, I can connect to the Caliber server 192.168.x.x:Port# . It asks me to authenticate with e user name and password I set up, and then it displays the catalog.
By the way, for the 2nd time, Calibre 'lost' my database (which was stored on a shared drive on my server). So I lost all of my metadata, etc. After having this happen twice, I decided to create a new library on the local hard drive. But of course, that means I have to rebuild the entire database.
Here's a link to a screenshot of the server's share info.
https://dl.dropboxusercontent.com/u/...2014.48.48.png
How can I get it to use something other than the internal loopback address if it is supposed to show the internal IP address?
Thanks for your help.

[eschwartz]

Take a look at Preferences ==> Tweaks.

I don't know why this would have happened, but your issue reminds me of the tweak:

#: What interfaces should the content server listen on
# ID: server_listen_on
# By default, the calibre content server listens on '0.0.0.0' which means that it
# accepts IPv4 connections on all interfaces. You can change this to, for
# example, '127.0.0.1' to only listen for connections from the local machine, or
# to '::' to listen to all incoming IPv6 and IPv4 connections (this may not
# work on all operating systems)
server_listen_on = '0.0.0.0'

Is that set to 127.0.0.1 by any chance?



But if so, I cannot imagine why your phone's browser can connect.

[theducks]

Shared Drive on a network is asking for the problems (lost DB) you found
Read the FAQ and avoid future pain


127 is only for the local machine and nothing outside the same mainboard

port 80 (or 8080) (common WEB interface) may either be blocked or in use. Check your firewall

[dbender54]

In searching thru the tweaks, which I'd not messed with, iI see: server_listen_on='0.0.0.0'
I don't know how to tell if this is enabled or not. I tried putting a # in front of that line and saving/restarting, but that doesn't do anything. The tweak still shows the same and the interface still shows 127.0.0.1 for the content server under Connect/Share. I also tried reseting the tweak and restarting. No change.
Im away from my local network and was able to connect via the Web interface to the ip address and port iIspecified.

[dbender54]

Originally Posted by eschwartz

It should show the internal network IP address.

Can you connect to 192.x.x.x via the web browser on your phone? If so, and CC cannot connect, the problem lies there, not in calibre.

I ended up uninstalling the current version of Calibre, since all of this took place after I "upgraded". I re-installed the prior version, which I luckily still had in the recycle bin. I found, though, that initially the Content Server IP address was still reported as 127.0.0.1. So I went into the Preferences-->Tweaks and looked for the tweak mentioned regarding the interface and changed the '0.0.0.0' to my Calibre server's internal IP address, restarted the Calibre server, and it now shows the proper internal IP address and port number.

The proof of the 'fix' is that I could connect to the Content Server with my phone using Calibre Companion and see/browse the library. The one thing in this dialog box I don't understand is the prompt for Wi-Fi to be on. I'm not sure why it should matter whether Wi-Fi is on since I'm not connecting through my internal network, unless it is presuming that the device is a solely non cellular connection.

I can connect through the web browser to my library as I could before, so I know the port forwarding is working correctly.

Now I'm in the process of resurrecting the database and cleaning up the metadata. With the change in location of the database to an internal drive, I am obviously hopeful that I won't experience any further database corruption. I have an app (Caffeine) I use on the Mac Mini to ensure the drives don't sleep, because of the very same issue that was mentioned relative to network drives. I run Plex on the Mini, but have way more multimedia content to serve up than I'd would probably fit on an internal drive (and don't want a stack of externals), which doesn't have any redundancy. I don't have any issues with Plex 'losing' the connection to those drives. I know this is a hardware dependent issue.

Thank you for your patience and support. Looking forward to getting the library cleaned up and in use!

[theducks]

dbender
Do you have more than 1 NIC in your box? (that is mostly what the tweak was intended for. Make it only listen on one adapter)
Do you have other devices (eg Blutooth) that have an IP assignment (not necessarily in the same subnet)

IIRC there was an issue way back, with rampant 'tunnel devices' .
System cleanup was needed

[eschwartz]

Originally Posted by dbender54

I ended up uninstalling the current version of Calibre, since all of this took place after I "upgraded". I re-installed the prior version, which I luckily still had in the recycle bin. I found, though, that initially the Content Server IP address was still reported as 127.0.0.1. So I went into the Preferences-->Tweaks and looked for the tweak mentioned regarding the interface and changed the '0.0.0.0' to my Calibre server's internal IP address, restarted the Calibre server, and it now shows the proper internal IP address and port number.

Huh. The only code change this version that touched the server is https:///github.com/kovidgoyal/calib...d18e64a09cde85 and I can't imagine why that would break things.

The fact that an old version still didn't do the trick would imply something changed on your system.

The proof of the 'fix' is that I could connect to the Content Server with my phone using Calibre Companion and see/browse the library. The one thing in this dialog box I don't understand is the prompt for Wi-Fi to be on. I'm not sure why it should matter whether Wi-Fi is on since I'm not connecting through my internal network, unless it is presuming that the device is a solely non cellular connection.

Because most people don't have use port forwarding with a dynamic DNS service, which means they need to connect via LAN, which means a cellular connection won't be able to see the server.

[theducks]

Originally Posted by eschwartz

Because most people don't have port forwarding with a dynamic DNS service, which means they need to connect via LAN, which means a cellular connection won't be able to see the server.

Huh!

Port forwarding is done in my router, regardless of current WAN IP

Dyndns allows your router (gateway) to be easily re-found from the WAN
No IP chasing needed

[eschwartz]

Sorry, I meant they don't use it.

Having the option when you have never touched the router configuration pages (still using the password printed on the side and all) doesn't do much good...

[dbender54]

The same Mac that runs Calibre also runs Plex. The Mac has both wired and wireless interfaces, though it's only being connected to thru the wired interface. For Plex (running on the Mini) , the port forward from the router is to a port in the range of 32000, while for Calibre, it's in the 2000 range. There's a Synology server on the same network with various port forwards for the different services in use there, but none of those are conflicting with the Mac Mini. This is a Uverse Gateway, so though I can do the forwarding I need, some ports are dedicated to their use (like 80 and 8080).
When I Iinitially installed Calibre, in the Connect/Share it showed the internal actual IP of the Mac and the port I assigned. I was able to connect to the Content Server using Calibre Companion. Once iIinstalled the update though, the Connect/Share showed the loopback address for the Content server and nothing I did (turning sharing off/on, restarting the program, restarting the computer), changed that. I could always connect to the Web interface of the server using the external address and port (port used in the router port forward). Since 'forcing' the assignment through the tweak, it now has no problem connecting, except that even on my phone, it insists on a Wi-Fi connection being active (when away from my home network) . No wifi connection, no connection to the Content Server! If i have a 3 or 4G data connection from my phone, why should I have to have a Wi-Fi connection? If i am somewhere where there is wifi, then it can connect.
What do ineed to change in my config settings, and where?
Bluetooth is in use on the Mini for a wireless keyboard and mouse. Again though, it worked without the tweak before the version upgrade.
As to the tweak, if there's a better workaround than my forced assignment, open to suggestions.
Thank you for the help.

[theducks]

You may need the tweak because what you have is no longer working.

Quit muddling the basic issue with all those other Port forwarded things.
4G irrelevant,
Blutooth (other than one with a IP FTP channel) irrelevant
That may come in way later. You proved you rig has some network access move on and nail the basic problem of 127.0.0.1

Basic Troubleshooting:

You first need to solve WHY calibre is on the wrong IP
If it is not accessible ON YOUR LAN, it sure ain't gonna be from the WAN.
Fix the first problem and you may find the rest just works.

Your rig has multiple network devices, so you may need to use the tweak to steer it. Theory says it should not matter. If the theory was perfect, the tweak would not be there .

what does the netstat command (or a gui network status tool) turn up?
Lots of Macs running out there on the current version (14% of the Calibre users use OSX). If there was a problem, we would see more help requests here.

This is something unusual with your rigs configuration.

Have you tried renaming the Calibre Config folder (so it regenerates)?

[theducks]

Originally Posted by dbender54

The same Mac that runs Calibre also runs Plex. while for Calibre, it's in the 2000 range.

Wait a minute you set the content server port in the 2xxx range



There is a very good chance that there is a clash with common services.

There is a reason to use the higher 4digit>numbers

[dbender54]

I can try changing the port forward to Calibe to a higher number. It's now 2600. I'll review open port ranges and see what makes sense. I'm out of town for a few days, and would prefer not to do this remotely. When I uninstalled the instance of Calibre after I updated, I believe I got the /prefs in the home directory as well (thought that might have been the problem), but will check (I used AppZapper to uninstall). I will also try netstat to see what it reveals, and renaming the config folder (hadn't tried either of those). I agree that if I can fix this part, it will work as it did before. I'd like to actually fix the issue rather than force a bandaid on it, as I know it works (worked previously).

Thanks you for the suggestions. I'll let you know what I see.