This site is being deprecated.

Please see the official X‑Plane Support page for help.

0 votes
asked by (12 points)
retagged by

Hello there

I'm attempting to complete a full X-Plane 11 install (ie with a purchased product key) on Linux. The installer starts up fine and I can enter my product key. However when I then hit 'Continue' the installer reports a problem with the authentication server.

The console output suggests there's a problem with verifying the certificate and I can't get any further:

* Connected to clearancedelivery.x-plane.com (104.200.23.194) port 443 (#0)
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* error setting certificate verify locations:
  CAfile: /tmp/filejGLLbE
  CApath: none
* Closing connection 0

And in the log file it's reporting a few more details:

Writing auth cert to disk returned: 4/13 for path /tmp/filejGLLbE

A few details about my setup:

  • I'm based in the UK and am running Debian Linux 64-bit
  • I'm using the latest Linux 64-bit installer (downloaded again today to make sure)
  • I can confirm the user I'm running the installer with has write access to /tmp and that there is space on the disk (assuming the installer is trying to put a CA there prior to confirming the product key)
  • I've no previous demo install 
  • I've tried over the past three days with no change
  • I am not running any proxies
  • I've attached the log output - http://questions.x-plane.com/?qa=blob&qa_blobid=4343225764084035705

Has anyone else run into this? Any suggestions much appreciated!

-Jon

commented by (148 points)
Can you o

ls -la /tmp/filem3bRNF

and show the results?  The installer is basically saying it can't write a temporary file with our private certificate (embedded in the installer) to disk for CURL's use, so it can't authenticate that the server is the actual server.
commented by (12 points)

I suspected this might be the issue, unfortunately the certificate never appears in tmp although as mentioned I am able to write files there OK. This was whilst the installer was still running, immediately after the error struck:

> ls -la /tmp/file*
ls: cannot access /tmp/file*: No such file or directory
> touch /tmp/file1234
> ls -la /tmp/file*
-rw-r--r-- 1 jon jon 0 Dec 28 22:37 /tmp/file1234

 

Please log in or register to answer this question.

...