View Single Post
Old 09-09-2013, 06:29 AM   #7
Lofwyr23
Poker of bits and books
Lofwyr23 can solve quadratic equations while standing on his or her head reciting poetry in iambic pentameterLofwyr23 can solve quadratic equations while standing on his or her head reciting poetry in iambic pentameterLofwyr23 can solve quadratic equations while standing on his or her head reciting poetry in iambic pentameterLofwyr23 can solve quadratic equations while standing on his or her head reciting poetry in iambic pentameterLofwyr23 can solve quadratic equations while standing on his or her head reciting poetry in iambic pentameterLofwyr23 can solve quadratic equations while standing on his or her head reciting poetry in iambic pentameterLofwyr23 can solve quadratic equations while standing on his or her head reciting poetry in iambic pentameterLofwyr23 can solve quadratic equations while standing on his or her head reciting poetry in iambic pentameterLofwyr23 can solve quadratic equations while standing on his or her head reciting poetry in iambic pentameterLofwyr23 can solve quadratic equations while standing on his or her head reciting poetry in iambic pentameterLofwyr23 can solve quadratic equations while standing on his or her head reciting poetry in iambic pentameter
 
Posts: 70
Karma: 12662
Join Date: Sep 2013
Device: Kobo Glo HD, Tolino Vision 5
Quote:
Originally Posted by chaley View Post
That means that some other program, possibly another instance of calibre, has already used port 9090. Alternatively, some security setting prevents calibre from using the port.

Try netstat -p -a and look down the list to see if port 9090 is already used. Alternatively, try a different number such as 9345 or 10034. If calibre can use one of those then allow it through your firewall.

If you drop the port setting then you get a random port that almost certainly will not be opened through your firewall unless you have an application-based firewall and not an IPTables-based one.
Assigned 22000 -EDIT-, which fixed the port error, but CC still doesn't want to connect to the library. Firewall opened with upd AND tcp, I don't know if SELinux interferes, tbh.

-EDIT2- Okay, nothing changed, except a, rather unwanted, reboot. Now it works...

Last edited by Lofwyr23; 09-09-2013 at 06:32 AM.
Lofwyr23 is offline   Reply With Quote