September 30th, 2021 authentication fix

Following a component break of one of the components used to run Xangle/Virtual.ink (LetsEncrypt), a manual fix need to be applied. A new version is going to be provided eventually, but for the moment, this is the procedure to apply. It’s been a stressful morning to figure out what was happening, but Laurent and Valentin came up with a clean solution pretty quickly. Here’s the reason why it happened out of nowhere today: https://www.zdnet.com/article/fortinet-shopify-others-report-issues-after-root-ca-certificate-from-lets-encrypt-expires/

Solution 1 (Windows only - easy)

  1. close Xangle

  2. download license_fix.bat

  3. move to your XangleCs folder (where you launch the software)

  4. run the batch file

  5. run Xangle

Solution 2 (Windows or Mac)

  1. Close Xangle

  2. Open the config text file in a text editor. On a Windows computer, this is located in c:\users\your-user-name\xangleCs\config\server_settings.json
    * On a Mac computer, you’re going to find this file in /Users/xangle …
    * For Virtual.ink, look for the “virtual.ink” folder from the same user path

  3. Change the value of “licenseapi” / “url” to http://fix.xangleapps.net (with the “fix” subdomain, and without the “s” in http)
    "license_api": {

    "url": "http://fix.xangleapps.net"

    },

  4. Save the json file and restart Xangle

Additional notes

  1. If you’re using the sharing module, repeat the #2.3 procedure and replace the sharing_api url to http://fix.sharing.xangleapps.net

I’ll be as quick as possible to help if you encounter any issues with the steps above. Always include dev@xangle.team so Valentin and Laurent can help with the replies

I’m sorry about this inconvenient. We’ll come up with a definite fix soon.

Thanks <3

EriC