MobileRead Forums - View Single Post

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?

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?