ariverahorta

Thank you for re-posting Line6Tony's original message phil_m. I understand the post's resolution is to upgrade to Mac OS X v10.12.2. However, my hardware will not go past v10.11.6. Therefore, I posted my solution to get Spider V Remote to login. Again, adding your Line6 account credentials may establish the trust needed for the application to connect to the Line6 servers. If not, then manually downloading Sectigo's SSL certificates and adding them to Mac OS X Keychain Access (or Windows CertMgr.msc) will definitely establish that trust.

To manually add account credentials on Mac OS X: 1. Close HX Edit 2.90. 2. Open Keychain Access (shortcut: Search for “Keychain Access” via Spotlight) a) Click "Go" in the Finder menu at the top of the screen. b) Select the "Applications" menu. c) Double-click the "Utilities" folder in the "Applications" folder. d) Double-click the "Keychain Access" icon in the "Utilities" folder. The application opens and you can browse your saved password information. 3. Create a new Password (shortcut: COMMAND+N) a) Click “File” in the Keychain menu at the top of the screen. b) Select “New Password Item…”. c) On the form that opens, type in a “Keychain Item Name” such as “Line6 account”, Your Line6 “Account Name”, and your Line6 account “Password”. d) To complete, click on “Add”. 4. Open HX Edit 2.90 and attempt to login. If successful, click “Update Now”. (Don’t forget to backup your hardware.) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Please note: The Line6 Downloads landing page shows Helix/HX Firmware 2.90 under “Recent Updates”. When you click on “READ MORE”, it redirects you to the HX Edit Version 2.92. The description reads: “…Doesn't matter what firmware your Helix/HX product is currently running; you can go straight to 2.92.” I clicked on the provided download link, it actually downloaded v2.92.

Spider V Remote v2.00 would not let me log into my Line6.com account from Mac OS X El Capitan (v10.11.6). I went to the Sectigo site, downloaded their SSL certs (among all the rest), and installed them to Keychain Access. No joy... I ended up adding my login credentials to the Keychain Access (Local Items) (Passwords) and that worked. It may be that both steps are needed to be performed for the fix, but if anyone were to try adding their credentials to the keychain first - it might be worth a shot.