[chaley]

Originally Posted by duckpuppy

I have two issues, one with Calibre's standalone content server and one with Calibre Companion.

First, the standalone content-server doesn't announce itself over Bonjour/Zeroconf/whatever, so Calibre Companion doesn't see it without manually setting the IP address and port numbers. Calibre Companion works with the default empty values if I've started the content server via the GUI, but not by running the standalone content-server app. This wouldn't be as much of a problem if not for #2...

The standalone server does advertize using bonjour.

Our experience when building CC was that a *lot* of home network routers block MDNS (bonjour) multicast packets, making bonjour close to useless for CC. We had no end of trouble and complaints about connection problems. Because of this we added a UDP broadcast "find" mechanism to calibre's wireless driver (similar to DHCP), which is only running if the GUI is running. It is almost certain that in your case CC is seeing answers from this mechanism and that bonjour packets are being suppressed somewhere.

Secondly, I'm running the content-server with a url prefix of /calibre, which is the suggested way to handle integrating the content-server into another server via reverse proxy. That works nicely, except that there's no way to tell Calibre Companion that I'm using a prefix, which means that it can't see the content server even if I give it the IP address and port.

I have this problem. I run a standalone server on a VPS in some data center and therefore need to separate the two connection schemes. I have already started work on this.

In the not-far future, the content server IP setup will be separated from the wireless device setup. The new scheme will allow a user to:
- use the settings from the wireless device setup, meaning that ip and port information are determined from the broadcast setup. This will be the default
- use a different IP address & port
- use a specific URL, in which case the port must be embedded in the URL. The URL will the one for the main content server page, not the OPDS subpage. CC takes care of the sub-navigation.

I don't use a prefix so I will use the second scheme. You will use the third.

In the meantime, you might be able to use a port-based named virtual host as the reverse proxy, eliminating the prefix. This works if you have some control over your DNS and are able to add sub-zones. Instead of www.foo.com/library you would use library.foo.com:9090. If you have full access to your configuration files and are running apache, then you could also use www.foo.com:9090 and have that match a different virtual host.