Jump to content

Canada's top-tier Telescopes & Accessories
Be as specific as possible when reporting issues and *ALWAYS* include the full version number of the application you are using and your exact *CAMERA MODEL*
NEVER POST YOUR KEY IN ANY PUBLIC FORUM, INCLUDING THE O'TELESCOPE SUPPORT FORUM ::: IF YOU DO YOUR KEY WILL BE DEACTIVATED WITHOUT NOTICE!
  • 0

Cannot Validate Licence Key


degrbi

Question

I hate to bark up this tree as it seems like a common issue. I downloaded the Backyard eos 3.2.3 trial, just to see if I could get it to run. I am running Windows 7 professional and really like it, so i'm not up for upgrading as it works fine with all my other astronomy gear. I cannot get the validation code to accept. The code is right and the identifier is right, but I keep getting the error where it says I have to be connected to the internet and make sure that any firewall or security software is not blocking it. I have checked the setting in regedit and it is running TLS 1.2 after going through the process to enable it. The frustrating thing is I have BYE on two other systems, but I really need it to run on this one as it's directly connected to my observatory. Any suggestions?

Derek

Link to comment
Share on other sites

11 answers to this question

Recommended Posts

  • 0

How is the observatory computer, that is running BYE, connected to the internet?

Do other apps that use the Internet work OK on the observatory computer?

Are you using Copy/Paste to transfer the license key from the O'Telescope web site into the BYE license validation dialog?

Have you customized your firewall software to allow BinaryRivers.BackyardEOS.Start.Camera1.exe, as well as Camera2, Camera3, and Camera4 through your firewall?

If you temporarily disable the firewall software will your license validate?

If your observatory computer is connected to the internet, then it may be a security vulnerability for your entire network because the Windows 7 is not longer supported by Microsoft and new security issues may not be patched. You should upgrade, even though it is working for your astro needs.

 

Link to comment
Share on other sites

  • 0

Hi,

What do you mean, you have BYE installed on 2 other systems? Is this using a trial or purchase key? I because the Internet is required only for Trial keys, and I can confirm 100% that your trial key in your account degrbi has not been activated on 2 other system looking at the server logs. Do you have a purchase key under another account? If yes, use your purchase key.

Keep us posted.

Link to comment
Share on other sites

  • 0

Well, it is behaving like either BYE is not using TLS 1.2 to communicate with the license server or the license server is down.

Despite the fact that Windows 7, 8, and 8.1 are no longer supported by Microsoft, it seems like a lot of people are still using them. It should be possible to configure the license server to accept older versions of TLS which would avoid the not uncommon license validation issue for for users of old Windows versions. Or make it very prominent to new users that operation of BYE and BYN with Windows version earlier than Windows 10 are not guaranteed and require the use of TLS 1.2.

Link to comment
Share on other sites

  • 0

Purchase keys do not expire! I first bought BYE back in 2011. I upgraded the license from a multi-line key to a single line key when version 3.1 was released. I did pay the upgrade fee when they first came out with a Premium license. No other license fees were necessary even though I have replaced the PC's several times. I have it installed with the same license on a desktop computer and a laptop. See below how this is allowed and what the restrictions are.

The developers of BYE were spending a lot of time helping people who were using BYE 3.0 and earlier who misplaced their multi-line license key to re-issue the key to them. With BYE 3.1 they went to a different licensing mechanism where the key was reduced to a single line key and the key was held on the BYE servers and was always available to a user via a web page on the server. They provided an upgrade path where users of older versions of BYE (with a multi-line key) could use that key to get a new single line key at no cost. That key is valid for all versions of BYE from 3.1 to the latest version as of October 2023. So in order to access your license key(s) you only need to remember the username that you were logged on with when you purchased the key. If you want to upgrade a multi-line key to a single line key just click on the "BackyardEOS Upgrade Instructions" link in the page footer below.

Also, the End User License Agreement (EULA) allows you to have BYE installed on multiple computers using the same license key as long as you only run one at a time. However, if you have an observatory with 2 imaging setups and you want to run them with their own PC and you plan to run both at the same time you would need multiple licenses. That said, you also have the ability to run 4 different instances of BYE with a single license on a single PC. They can be configured to create master-slave relationships or they can run independently, as your needs dictate.

It may also be worth saying that BYE and BYN are two different products and each requires their own license. The licenses are not interchangeable as they are two different products.

Link to comment
Share on other sites

  • 0
2 hours ago, astroman133 said:

Well, it is behaving like either BYE is not using TLS 1.2 to communicate with the license server or the license server is down.

Despite the fact that Windows 7, 8, and 8.1 are no longer supported by Microsoft, it seems like a lot of people are still using them. It should be possible to configure the license server to accept older versions of TLS which would avoid the not uncommon license validation issue for for users of old Windows versions. Or make it very prominent to new users that operation of BYE and BYN with Windows version earlier than Windows 10 are not guaranteed and require the use of TLS 1.2.

I can confirm with 100% certainty that the activation server is healthy and operational.

Link to comment
Share on other sites

  • 0
3 hours ago, astroman133 said:

Well, it is behaving like either BYE is not using TLS 1.2 to communicate with the license server or the license server is down.

Despite the fact that Windows 7, 8, and 8.1 are no longer supported by Microsoft, it seems like a lot of people are still using them. It should be possible to configure the license server to accept older versions of TLS which would avoid the not uncommon license validation issue for for users of old Windows versions. Or make it very prominent to new users that operation of BYE and BYN with Windows version earlier than Windows 10 are not guaranteed and require the use of TLS 1.2.

Our current hosting provider does expose this setting, so the short answer is no :(

Link to comment
Share on other sites

  • 0
On 10/12/2023 at 9:08 PM, degrbi said:

I am running Windows 7 professional ... I cannot get the validation code to accept. The code is right and the identifier is right, but I keep getting the error where it says I have to be connected to the internet and make sure that any firewall or security software is not blocking it. I have checked the setting in regedit and it is running TLS 1.2 after going through the process to enable it. The frustrating thing is I have BYE on two other systems, but I really need it to run on this one as it's directly connected to my observatory. Any suggestions?

Derek

Perhaps you need to confirm that your Observatory PC does indeed have functional TLS 1.2 support.  Try this website:  SSLLabs TLS Client Support Test

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

This site uses cookies to offer your a better browsing experience. You can adjust your cookie settings. By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to the use of cookies, our Privacy Policy, and our Terms of Use