Nate wroteI'm sorry, I don't understand. The Spine trial download is working fine, there may be something wrong with your network or ISP.
@Nate I finally know what was the problem. Although I tested everything with firewall, anti-virus and everything off (I use Eset), there happens to be a SSL setting that Eset didn't switch off even when it states everything is disabled.
I found out that the problem lies in Eset Internet Security though because I had another strange network-problem lately with using Composer to install php-packages. That was a very long debug session at that time, but this solved it. So I just tried to see if this also fixes my issue installing Spine Trial earlier... and it did!
So for your information, and in case other people are having the same problem I had and are using Eset, this was the blocking setting [also see screenshot in attachment]:
My problem was that Eset was set per default to check the SSL/TLS communication, but somehow that is causing problems with some programs, like Composer and Spine. Strangely some other programs work fine with it, like NPM or other software I use that need connections with servers via SSL. So I'm not sure why some programs are ok with it and others don't but at least this does the trick:
- Rightclick on Eset-icon in the notification area of the taskbar and click 'Advanced Setup'
- Open the 'Web and Email'-'tab' on the left and than maximize the 'SSL/TLS' panel on the right
- If you switch off 'Enable SSL/TLS protocol filtering' and click OK to close all Eset dialogs, you can install Spine without a problem, so that solves the issue.
- But if you like to keep this setting enabled, than click on 'edit' next to 'List of SSL/TLS filtered applications' to see if Spine is in the list. If it is, just select it and click the delete-button. If you now restart Spine (and Eset has SSL/TLS protocol filtering mode set to 'Interactive mode' in the panel you have open) Eset will popup a window to ask you if you like to scan the connection. Just choose not to and Esets skips scanning the SSL connection for Spine. problem solved![/i]
This took me a long time to figure out and I'm glad I finally figured it out and got Spine Trial working now, so I'm posting this to maybe help others having the same problem with Spine in combination with Eset.
