View Single Post
Old 09-09-2013, 06:23 AM   #6
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 11,741
Karma: 6997045
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by Lofwyr23 View Post
Thanks, adding the machine's hostname (Which wasn't set at install... :shakes fist at Fedora: ) to /etc/hosts fixed it.

-EDIT- Okay, that was too early... now it says (roughly translated): Driver for wireless connection wasn't started: couldn't bind port 9090

Dropping the port setting,m it starts, but still isn't seen.

I've opened up a port in the firewall, but that didn't fix either...
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.
chaley is offline   Reply With Quote