Can Not Receive SW Update Notices
Issue #555
closed
I am not sure this should be classified as a bug. It looks like some ISP’s block ports (TCP/UDP) to the N.I.N.A. update servers. I have no problems getting automatic update notices for PixInsight, Adobe products and others. In the future you may want to redesign your SW update protocol. This issue exists with Cox Cable Inc. A short list of Cox Cable port filtering can be seen below.
https://www.cox.com/residential/support/internet-ports-blocked-or-restricted-by-cox.html
Comments (8)
-
-
reporter
I uninstalled McAfee and turned off Win10 Home Firewall / Defender to make sure nothing was blocking the update notice. A log file with errors was posted on Discord some time ago. I get update notices for PixInsight and Adobe Lightroom and some others.
-
reporter
What could be stopping the notices?
-
repo owner
It could be possible that using TLS version 1.2 is disabled on your machine. Then the communication might fail with that error.
-
reporter
TLS 1.0, 1.1 and 1.2 is enabled. Chrome is my default browser. I never got notices for Nightly Builds. Are you issuing notices for Beta builds now? I am using a new Win 10 Home laptop.
-
repo owner
Yes each build gets notices when your auto update source is set to the according build channel in your options.
It’s just a simple RESTful HTTPS GET request. Nothing fancy. Can’t get more simple than that.
(Which browser you are using is not relevant for this) -
reporter
OK - let me contact Cox Cable again and ask for second level support. They may be blocking stuff from a regional standpoint. I forgot to mention that I bypassed my Netgear router and connected directly to my cable modem.
-
repo owner
- changed status to closed
Closing as this is no issue with the software
- Log in to comment
If you can reach the NINA website from your computer, then the app can get the update info. The protocol used is straight-up HTTPS (TCP port 443), nothing fancy or alien.
If NINA isn’t able to get update information then there is likely another reason. First, a log might help hint at the cause and, second, NINA might be blocked from making external connections because of Windows firewall.