|
|
Thread Tools | Search this Thread |
09-03-2022, 11:59 PM | #1 |
Enthusiast
Posts: 33
Karma: 10
Join Date: Sep 2022
Device: Microsoft Surface Pro 7, Apple iPad
|
Content Server on Windows 10 (Surface Pro), Can't access IP:PORT in browser on macOS
Hello,
While I've known about Calibre for a while and been using it for conversions for a while now, I only just started customizing and using it for library/content management. The documentation being excellent, I've been able to find answers to most of my queries, either there or a bit of googling (site:www.mobileread.com QUERY). This appears to be an exception where none of the solutions have worked for me. The Setup & the Problem Running Calibre 6.3 on Windows 10 Home on a Surface Pro 7 device. Started Content Server from the main menu > Connect/share > Start Content server. The menu now shows Stop Content server [192.168.31.112, port 8080, HTTP]. Tested to be working in the browser using Visit Content server in browser (from the same menu) which takes me to http://127.0.0.1:8080 in my default browser (Google Chrome). Then when I visit http://192.168.31.112:8080 in Google Chrome, I am greeted with this error. Code:
This site can’t be reached http://192.168.31.112:8080/ is unreachable. ERR_ADDRESS_UNREACHABLE
Question(s) The manual page makes it seem like this shouldn't be complex at all. So, what am I missing? Could someone help me out? Assume that I am a noob and please try to be as detailed as possible. Thank you! |
09-04-2022, 02:29 AM | #2 |
Bibliophagist
Posts: 35,513
Karma: 145557716
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Forma, Clara HD, Lenovo M8 FHD, Paperwhite 4, Tolino epos
|
If you can't ping the address, it's unlikely that you will be able to connect to it over HTTP/HTTPS.
In Windows Defender Firewall with Advanced Security, did you try settings all the profiles so Inbound Connections that do not match a rule are allowed when testing? You may have Domain/Private/Public or Private/Public depending on the Windows variant. What is the IP address on your MacOS machine? In the same subnet as your Windows machine? Port forwarding should not matter since to use a 192.168 private address (see RFC-1918 for the definition of private network blocks), you would need to be connected to the same router. If you are trying to connect from outside your local network, then you would need to start worrying about port forwarding and what external IP your router is using. Last edited by DNSB; 09-04-2022 at 02:34 AM. |
09-04-2022, 05:28 AM | #3 |
Well trained by Cats
Posts: 29,820
Karma: 54830978
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
|
additionally: Some (most) WiFi routers block connections on the same LAN by default.
Also, both must use the same band. 2.4 or 5.0 Having the host on a wired network is a Plus |
09-04-2022, 06:53 AM | #4 | |
Grand Sorcerer
Posts: 11,742
Karma: 6997045
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
|
Quote:
|
|
09-04-2022, 08:20 AM | #5 | ||
Enthusiast
Posts: 33
Karma: 10
Join Date: Sep 2022
Device: Microsoft Surface Pro 7, Apple iPad
|
Enabled echo/ping requests as advised by @DNSB, following both these tutorials: https://kb.iu.edu/d/aopy and https://www.howtogeek.com/howto/wind...ista-firewall/. For some reason this didn't allow pinging immediately, even after a restart. But it did work later magically, somehow! (Two things I did during this time: Changed WiFi security from WPA/WPA2 to WPA2 and then router got restarted.)
Also, during the time the above wasn't working, I looked into other suggestions. Quote:
Confirmed both computers are on same band (2.4 GHz). Quote:
Nope, not signed into guest network. No Wireless isolation or related settings found. Anyway, the issue has been resolved by enabling pinging on the Windows 10 device hosting Calibre Content Server. Thank you so very much! |
||
09-04-2022, 09:06 AM | #6 | |
Enthusiast
Posts: 33
Karma: 10
Join Date: Sep 2022
Device: Microsoft Surface Pro 7, Apple iPad
|
Quote:
|
|
09-12-2022, 12:42 PM | #7 |
Enthusiast
Posts: 33
Karma: 10
Join Date: Sep 2022
Device: Microsoft Surface Pro 7, Apple iPad
|
After adding Firewall rules, you might have to restart router!
Note to self: If you are unable to ping again for some reason (and therefore cannot access Calibre Content Server), see if restarting the router fixes it.
If that doesn't work, reset the Windows Defender Firewall rules (Control Panel > Windows Defender Firewall > Restore defaults, or Control Panel > Windows Defender Firewall > Advanced settings > Inbound Rules, and manually remove the rules), add the rules again, then restart the router. Unsure why this might happen (happed only once to me), but if it was working before, one of these should do the trick. Last edited by 01100001; 09-12-2022 at 12:43 PM. Reason: added message title |
Tags |
calibre 6.3, catalina, macos, surface pro 7, windows 10 |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Can't access Calibre server even with port forwarded | Chabotnick | Related Tools | 6 | 04-23-2014 11:33 PM |
Calibre Content Server - change port - Windows Firewall Settings | rl77 | Calibre | 2 | 02-19-2014 02:15 PM |
Windows 8 Surface Pro Reviews | fjtorres | News | 39 | 01-18-2013 05:07 PM |
Content Server and Port Forwarding with FIOS | joeindallas | Calibre | 0 | 09-26-2011 12:14 PM |
Calibre Content Server, Windows 7 Pro, SMC Docsis 3 | SensualPoet | Calibre | 4 | 05-12-2011 12:57 AM |