[pid  5466] openat(AT_FDCWD, "/dev/nvidiactl", O_RDWR) = 37
[pid  5435] openat(AT_FDCWD, "/usr/share/fonts/truetype/ariali.ttf", O_RDONLY) = 37
[pid  5455] openat(AT_FDCWD, "/etc/ssl/certs/ca-certificates.crt", O_RDONLY <unfinished ...>
[pid  5455] <... openat resumed> )      = -1 ENOENT (No such file or directory)
[pid  5435] openat(AT_FDCWD, "/home/db/neXt/prefs.ini", O_WRONLY|O_CREAT|O_TRUNC, 0666) = 39
 
 

Nicht OK:
[pid  7809] socket(AF_INET6, SOCK_DGRAM, IPPROTO_IP) = 16
[pid  7825] socket(AF_INET, SOCK_STREAM, IPPROTO_TCP) = 34
[pid  7825] connect(34, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("217.160.0.15")}, 16) = -1 EINPROGRESS (Operation now in progress)
[pid  7825] getpeername(34, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("217.160.0.15")}, [128->16]) = 0
[pid  7825] getsockname(34, {sa_family=AF_INET, sin_port=htons(58698), sin_addr=inet_addr("192.168.178.3")}, [128->16]) = 0
[pid  7830] socket(AF_INET, SOCK_STREAM, IPPROTO_TCP <unfinished ...>
[pid  7830] connect(39, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("217.160.0.15")}, 16 <unfinished ...>
[pid  7830] getpeername(39, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("217.160.0.15")}, [128->16]) = 0
[pid  7830] getsockname(39, {sa_family=AF_INET, sin_port=htons(58700), sin_addr=inet_addr("192.168.178.3")}, [128->16]) = 0
[pid  7835] socket(AF_INET, SOCK_STREAM, IPPROTO_TCP <unfinished ...>
[pid  7835] connect(39, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("217.160.0.15")}, 16 <unfinished ...>
[pid  7835] getpeername(39, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("217.160.0.15")}, [128->16]) = 0
[pid  7835] getsockname(39, {sa_family=AF_INET, sin_port=htons(58702), sin_addr=inet_addr("192.168.178.3")}, [128->16]) = 0
 
OK:
[pid  8464] socket(AF_INET6, SOCK_DGRAM, IPPROTO_IP) = 16
[pid  8519] socket(AF_INET, SOCK_STREAM, IPPROTO_TCP <unfinished ...>
[pid  8519] connect(35, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("217.160.0.15")}, 16 <unfinished ...>
[pid  8519] getpeername(35, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("217.160.0.15")}, [128->16]) = 0
[pid  8519] getsockname(35, {sa_family=AF_INET, sin_port=htons(58712), sin_addr=inet_addr("192.168.178.3")}, [128->16]) = 0
[pid  8521] socket(AF_INET, SOCK_STREAM, IPPROTO_TCP) = 38
[pid  8521] connect(38, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("217.160.0.15")}, 16) = -1 EINPROGRESS (Operation now in progress)
[pid  8521] getpeername(38, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("217.160.0.15")}, [128->16]) = 0
[pid  8521] getsockname(38, {sa_family=AF_INET, sin_port=htons(58714), sin_addr=inet_addr("192.168.178.3")}, [128->16]) = 0
[pid  8533] socket(AF_INET, SOCK_STREAM, IPPROTO_TCP <unfinished ...>
[pid  8533] connect(36, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("217.160.0.15")}, 16 <unfinished ...>
[pid  8533] <... getpeername resumed> {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("217.160.0.15")}, [128->16]) = 0
[pid  8533] <... getsockname resumed> {sa_family=AF_INET, sin_port=htons(58716), sin_addr=inet_addr("192.168.178.3")}, [128->16]) = 0
 
 

[pid  7645] getpeername(39, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("217.160.0.15")}, [128->16]) = 0
[pid  7645] getsockname(39, {sa_family=AF_INET, sin_port=htons(53620), sin_addr=inet_addr("192.168.178.3")}, [128->16]) = 0
[pid  7645] openat(AT_FDCWD, "/etc/ssl/certs/ca-certificates.crt", O_RDONLY) = -1 ENOENT (No such file or directory)
[pid  7645] close(39)                   = 0
[pid  7645] write(1, "Curl error 77: Error reading ca cert file from /etc/ssl/certs/ca-certificates.crt\n\n \n(Filename: ./Modules/UnityWebRequest/Implementations/TransportCurl.cpp Line: 734)\n\n", 168Curl error 77: Error reading ca cert file from /etc/ssl/certs/ca-certificates.crt
 
 
(Filename: ./Modules/UnityWebRequest/Implementations/TransportCurl.cpp Line: 734)
 
) = 168
 
 

       --cacert <file>
              (TLS) Tells curl to use the specified certificate file to verify the peer. The file may contain multiple CA certificates. The certificate(s) must be in PEM  format.  Nor-
              mally curl is built to use a default file for this, so this option is typically used to alter that default file.
 
              curl recognizes the environment variable named 'CURL_CA_BUNDLE' if it is set, and uses the given path as a path to a CA cert bundle. This option overrides that variable.
 
              The  windows  version  of curl will automatically look for a CA certs file named ´curl-ca-bundle.crt´, either in the same directory as curl.exe, or in the Current Working
              Directory, or in any folder along your PATH.
 
              If curl is built against the NSS SSL library, the NSS PEM PKCS#11 module (libnsspem.so) needs to be available for this option to work properly.
 
              (iOS and macOS only) If curl is built against Secure Transport, then this option is supported for backward compatibility with other SSL engines, but it should not be set.
              If  the  option  is not set, then curl will use the certificates in the system and user Keychain to verify the peer, which is the preferred method of verifying the peer's
              certificate chain.
 
              (Schannel/WinSSL only) This option is supported for WinSSL in Windows 7 or later with libcurl 7.60 or later. This option is  supported  for  backward  compatibility  with
              other SSL engines; instead it is recommended to use Windows' store of root certificates (the default for WinSSL).
 
              If this option is used several times, the last one will be used.
 
       --capath <dir>
              (TLS)  Tells  curl  to use the specified certificate directory to verify the peer. Multiple paths can be provided by separating them with ":" (e.g.  "path1:path2:path3").
              The certificates must be in PEM format, and if curl is built against OpenSSL, the directory must have been processed using the c_rehash  utility  supplied  with  OpenSSL.
              Using --capath can allow OpenSSL-powered curl to make SSL-connections much more efficiently than using --cacert if the --cacert file contains many CA certificates.
 
              If this option is set, the default capath value will be ignored, and if it is used several times, the last one will be used.