:help: Could not start the content server. Error:

Ersatzreifen · 06-13-2015, 06:19 AM

Every startup of Calibre I get this message:

calibre, version 2.29.0
ERROR: Failed to start Content Server: Could not start the content server. Error:
error('No socket could be created',)

Being that I'm not a programmer I haven't the foggiest idea of what to do about this.

How do I get the server working?

theducks · 06-13-2015, 08:52 AM

Was it ever working?

A possibility is your Firewall updated and now blocks. You need to whitelist (allow) Calibre.exe (if you launch the CS from the GUI) or caliber-server.exe if you launch the standalone.

Remember that you need to configure the server in Preferences: Sharing or use the proper CLI switches

Ersatzreifen · 06-13-2015, 09:14 AM

Nevermind. I finally was presented with relevant info only AFTER posting this.

I used search before posting and it gave me nothing. This program's search function is not at all user intuitive or even helpful.

Anyway...

The fix was to change the port to 8787. That worked.

I wish MobileRead's SEARCH function would work better!

Ersatzreifen · 06-13-2015, 09:20 AM

Quote:

Originally Posted by theducks

Was it ever working?

Nope. But no problem, I got it working finally. Just had to switch ports again, this time to 8787, then tell everything from modem/router through firewall to allow the new port. It's funny, because I already switched to port 85 because I know I don't have anything running on it, but that didn't work either. 8787 did for some reason.

kovidgoyal · 06-13-2015, 09:28 AM

On linux, non-root processes are not allowed to use ports under 1024.

BetterRed · 06-13-2015, 09:37 AM

Quote:

Originally Posted by Ersatzreifen

I wish MobileRead's SEARCH function would work better!

@Ersatzreifen - sometimes a site search with Google gives better results

Code:

"calibre server" site:www.mobileread.com

BR

06-13-2015, 06:19 AM	#1
Ersatzreifen Bibliothekar Posts: 38 Karma: 10 Join Date: Jun 2011 Location: San Jose City, Philippines Device: Galaxy Tab S w/Bookari Premium	:help: Could not start the content server. Error: Every startup of Calibre I get this message: calibre, version 2.29.0 ERROR: Failed to start Content Server: Could not start the content server. Error: error('No socket could be created',) Being that I'm not a programmer I haven't the foggiest idea of what to do about this. How do I get the server working?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
500 Internal Server Error accessing content server Calibre 0.8.8	DaddyO57	Calibre	1	07-20-2012 06:08 PM
Calibre Crashing on Start - Content Server	Tkosh	Calibre	2	01-06-2012 08:57 AM
Can only start the Calibre Content Server once Per port	Apothe0sis	Calibre	1	04-16-2011 08:25 AM
calibre, start content server, syncing iPad	vonCZ	Calibre	3	09-12-2010 04:23 AM
Content Server Problem - Wont Start	jtcweb	Calibre	2	05-10-2009 09:20 AM

06-13-2015, 08:52 AM	#2
theducks Well trained by Cats Posts: 31,240 Karma: 61360164 Join Date: Aug 2009 Location: The Central Coast of California Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A	Was it ever working? A possibility is your Firewall updated and now blocks. You need to whitelist (allow) Calibre.exe (if you launch the CS from the GUI) or caliber-server.exe if you launch the standalone. Remember that you need to configure the server in Preferences: Sharing or use the proper CLI switches

06-13-2015, 09:14 AM	#3
Ersatzreifen Bibliothekar Posts: 38 Karma: 10 Join Date: Jun 2011 Location: San Jose City, Philippines Device: Galaxy Tab S w/Bookari Premium	Nevermind. I finally was presented with relevant info only AFTER posting this. I used search before posting and it gave me nothing. This program's search function is not at all user intuitive or even helpful. Anyway... The fix was to change the port to 8787. That worked. I wish MobileRead's SEARCH function would work better!

06-13-2015, 09:28 AM	#5
kovidgoyal creator of calibre Posts: 45,596 Karma: 28548962 Join Date: Oct 2006 Location: Mumbai, India Device: Various	On linux, non-root processes are not allowed to use ports under 1024.

Advert

Advert