v7.20 Content Server issue (broken?)

jodeum · 10-21-2024, 09:43 AM

I just upgraded to v7.20 and noticed the content server does not appear to be working correctly. When I try to load a webpage for the server it fails. It does not give me any 'advanced' button to click to go to site for security reasons, there's nothing loading at all. That is via external IP.

From within Calibre I click 'Visit content server in browser' and still nothing loads using the internal IP address.

I have Calibre-Web installed, and that will load fine. So I know my connection, and port forwarding, is working fine, just as it has been for a long time.

I did notice one major difference, when I do click to go to content server (on the internal IP address) this is what loads in the url field of my browsers:
https://[::1]:7154/

I use port 7154, so that part is still coming through, but the rest of the internal IP address is not there. And it use to be. I noticed on the v7.20 patch notes a change to the SSL certificates was made. I'm wondering when this change was made if something broke involved in passing along the IP address of the content server. Both internal IP and external IP now fail to respond or load anything at all. The content server is non-existent as far as browsers can tell.

Anyone else having this problem?

kovidgoyal · 10-21-2024, 09:56 AM

[::] is an IPv6 address, though it should be [::1] You can always manually change it to http://localhost:7154 and it will load fine

And no the change to use bundled SSL certificates has no bearing on the content server

jodeum · 10-21-2024, 10:22 AM

Changing the URL to https://localhost:5304/ Initially does get me a page saying 'Your connection isn't private' with a link to continue to localhost (unsafe). But clicking that link to go forward loads nothing. In Edge, that states 'This page isn't working right now" with an HTTP ERROR 400 showing. No other option available.

It does not load the content server page. Also, localhost would do nothing for trying to load it using an external IP from somewhere else over the internet. The content server is broken with this latest update.

Normally I have had an SSL certificate being used in the settings, which is why I use HTTPS. For testing, I removed the certificate settings, restarted the content server and tried loading regular HTTP. It still loads nothing.

It worked fine before updating to v7.20. Literally the content server would load normally yesterday. I upgraded this morning (the only change made) and it is now broken.

kovidgoyal · 10-21-2024, 10:49 AM

Feel free to downgrade in that case. I will note that the port number in your two messages doesnt match.

jodeum · 10-21-2024, 11:07 AM

Quote:

Originally Posted by kovidgoyal

Feel free to downgrade in that case. I will note that the port number in your two messages doesnt match.

That was part of the troubleshooting. One of the things I tried was to verify any changes were going through. Changing the port used did show up in the URL when I clicked 'Visit content server in browser' from within Calibre.

Since it showed that change in the URL, I know that much at least is still being passed through. Just not the main internal IP address part. Like 192.xxx.x.x.

That's the part that is broken in this latest version.

DNSB · 10-21-2024, 01:26 PM

Have you tried changing the interface on which to listen for connections to your IP V4 connection instead of your IP V6 connection? Preferences => Sharing over the net => Advanced.

And have you tried http://localhost:xxxx??

Did you re-add the SSL private key and certificate files in the Advanced dialog?

kovidgoyal · 10-21-2024, 11:25 PM

There's nothing broken about it. Your IPv4 address will still work, by default the server listens on both IPv6 and IPv4. Feel free to use whichever you prefer.

jodeum · 10-22-2024, 09:02 PM

Quote:

Originally Posted by DNSB

Have you tried changing the interface on which to listen for connections to your IP V4 connection instead of your IP V6 connection? Preferences => Sharing over the net => Advanced.

And have you tried http://localhost:xxxx??

Did you re-add the SSL private key and certificate files in the Advanced dialog?

I do not see any option there for anything to do with ipv4 or ipv6. Not sure which setting you are referring to.

I'll try one more time to explain this. First, I do not use ipv6. My ISP does not use ipv6. My router, supplied by the ISP, does not have ipv6 enabled. There is no possible way I have, or have ever had, anything ipv6 set up or enabled on anything on my computer. Ipconfig command confirms everything is ipv4 on my computer.

But, i think that is where Calibre is now messed up. I did more troubleshooting steps to narrow it down further. First, I removed my certificate all together. Restarted Calibre completely. It still will not load the content server at all. Not going directly to the internal IP address assigned by the router, nor the external IP address.

I have an older copy of Calibre PORTABLE edition. When I start that up, turn on the content server, and test that connection, the 127.0.0.1:5304 (loopback) address will load the webpage normally in a browser. That separate older version works.

But when I shut that down and load the current software, nothing loads from the content server.

So, I cleared the server logs from within the 'sharing over the net' settings area, of the current version. Then I restarted the content server to see what logs it shows.

calibre server listening on [::]:5304
OPDS feeds advertised via BonJour at: 192.168.0.5 port: 5304

That is what I get. As you can see, the current version is not looking at ipv4 address format, it is looking at the ::1 ipv6 address format. Which does not exist on my computer. There is no setting for me to force it back to ipv4 that I know of. But somehow Calibre is now forcing it to use a non-existent ipv6 address. Therein lies the problem.

And for reference, this is the server logs from the Calibre PORTABLE version.

calibre server listening on 0.0.0.0:5304
OPDS feeds advertised via BonJour at: 192.168.0.5 port: 5304

Notice how it is listening on 0.0.0.0 and not the ::1 from the current version? That changed.

So, is there somewhere I am not seeing to force the current release of calibre to use the ipv4 address? Or is this an internal programming issue?

Before anyone asks, I have tried loading the internal IP and the loopback IP on Chrome, Edge, Firefox, Tor, and Vivaldi. And on Android. And a couple friends tried it over the internet. No it doesn't work anywhere. It's not a browser issue.

kovidgoyal · 10-23-2024, 01:04 AM

calibre listens on all ipv6 and ipv4 interfaces by default. This change happened about a year ago in version 7.2.0, not version 7.20. Listening on ipv6 does not mean it doesnt listen on ipv4. And calibre has always had a setting to control which interfaces the content erver listens on, Preferences->Sharing over the net->Advanced->The interface to listen on for connections. Change it to 0.0.0.0 if you only want to listen on IPv4 only. And incidentally the kernel of your machine is advertising ipv6 capabilities regardless whether you configured it to or not.

10-21-2024, 09:43 AM	#1
jodeum Junior Member Posts: 7 Karma: 10 Join Date: Nov 2009 Device: Pocketbook Touch HD 3	v7.20 Content Server issue (broken?) I just upgraded to v7.20 and noticed the content server does not appear to be working correctly. When I try to load a webpage for the server it fails. It does not give me any 'advanced' button to click to go to site for security reasons, there's nothing loading at all. That is via external IP. From within Calibre I click 'Visit content server in browser' and still nothing loads using the internal IP address. I have Calibre-Web installed, and that will load fine. So I know my connection, and port forwarding, is working fine, just as it has been for a long time. I did notice one major difference, when I do click to go to content server (on the internal IP address) this is what loads in the url field of my browsers: https://[::1]:7154/ I use port 7154, so that part is still coming through, but the rest of the internal IP address is not there. And it use to be. I noticed on the v7.20 patch notes a change to the SSL certificates was made. I'm wondering when this change was made if something broke involved in passing along the IP address of the content server. Both internal IP and external IP now fail to respond or load anything at all. The content server is non-existent as far as browsers can tell. Anyone else having this problem?

10-21-2024, 01:26 PM	#6
DNSB Bibliophagist Posts: 46,181 Karma: 168983734 Join Date: Jul 2010 Location: Vancouver Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos	Have you tried changing the interface on which to listen for connections to your IP V4 connection instead of your IP V6 connection? Preferences => Sharing over the net => Advanced. And have you tried http://localhost:xxxx?? Did you re-add the SSL private key and certificate files in the Advanced dialog? Last edited by DNSB; 10-21-2024 at 01:31 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
content-server reader is broken in 6.2	nqk	Server	3	07-29-2022 06:13 AM
Still a content server issue with 2.68	Sydney's Mom	Calibre	1	09-18-2016 03:24 PM
Browser / Content Server Issue	Sardog	Related Tools	3	02-02-2014 02:11 AM
Content Server Issue	pootytang	Calibre	1	06-12-2012 12:28 PM
Content Server authentication issue	judycsullivan	Library Management	6	02-28-2012 09:28 AM

10-21-2024, 09:56 AM	#2
kovidgoyal creator of calibre Posts: 45,345 Karma: 27182818 Join Date: Oct 2006 Location: Mumbai, India Device: Various	[::] is an IPv6 address, though it should be [::1] You can always manually change it to http://localhost:7154 and it will load fine And no the change to use bundled SSL certificates has no bearing on the content server

10-21-2024, 10:22 AM	#3
jodeum Junior Member Posts: 7 Karma: 10 Join Date: Nov 2009 Device: Pocketbook Touch HD 3	Changing the URL to https://localhost:5304/ Initially does get me a page saying 'Your connection isn't private' with a link to continue to localhost (unsafe). But clicking that link to go forward loads nothing. In Edge, that states 'This page isn't working right now" with an HTTP ERROR 400 showing. No other option available. It does not load the content server page. Also, localhost would do nothing for trying to load it using an external IP from somewhere else over the internet. The content server is broken with this latest update. Normally I have had an SSL certificate being used in the settings, which is why I use HTTPS. For testing, I removed the certificate settings, restarted the content server and tried loading regular HTTP. It still loads nothing. It worked fine before updating to v7.20. Literally the content server would load normally yesterday. I upgraded this morning (the only change made) and it is now broken.

10-21-2024, 10:49 AM	#4
kovidgoyal creator of calibre Posts: 45,345 Karma: 27182818 Join Date: Oct 2006 Location: Mumbai, India Device: Various	Feel free to downgrade in that case. I will note that the port number in your two messages doesnt match.

10-21-2024, 11:25 PM	#7
kovidgoyal creator of calibre Posts: 45,345 Karma: 27182818 Join Date: Oct 2006 Location: Mumbai, India Device: Various	There's nothing broken about it. Your IPv4 address will still work, by default the server listens on both IPv6 and IPv4. Feel free to use whichever you prefer.

10-23-2024, 01:04 AM	#9
kovidgoyal creator of calibre Posts: 45,345 Karma: 27182818 Join Date: Oct 2006 Location: Mumbai, India Device: Various	calibre listens on all ipv6 and ipv4 interfaces by default. This change happened about a year ago in version 7.2.0, not version 7.20. Listening on ipv6 does not mean it doesnt listen on ipv4. And calibre has always had a setting to control which interfaces the content erver listens on, Preferences->Sharing over the net->Advanced->The interface to listen on for connections. Change it to 0.0.0.0 if you only want to listen on IPv4 only. And incidentally the kernel of your machine is advertising ipv6 capabilities regardless whether you configured it to or not.