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 was able to connect to the Content Server using Calibre Companion. When I Iinitially installed Calibre, in the Connect/Share it showed the internal actual IP of the Mac and the port I assigned. This is a Uverse Gateway, so though I can do the forwarding I need, some ports are dedicated to their use (like ). 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. 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. The Mac has both wired and wireless interfaces, though it's only being connected to thru the wired interface. The same Mac that runs Calibre also runs Plex. Looking forward to getting the library cleaned up and in use! I know this is a hardware dependent issue. I don't have any issues with Plex 'losing' the connection to those 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 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. 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. Now I'm in the process of resurrecting the database and cleaning up the metadata. I can connect through the web browser to my library as I could before, so I know the port forwarding is working correctly. 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. The one thing in this dialog box I don't understand is the prompt for Wi-Fi to be on. 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. 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. I found, though, that initially the Content Server IP address was still reported as 127.0.0.1. I re-installed the prior version, which I luckily still had in the recycle bin. I ended up uninstalling the current version of Calibre, since all of this took place after I "upgraded". It should show the internal network IP address.Ĭan 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |