'provision.sh prod' doesn't work fine about fbctf HOT 7 CLOSED

Thanks @mpomarole for clarification! Will try :)

from fbctf.

@mpomarole You're correct, I was on 16.04 which is apparently not supported by HHVM > 3.11. I tried compiling from source but there was some linkage issue. Reverted to 14.04 and all seems good.

from fbctf.

Getting the same error:
nginx: [emerg] BIO_new_file("/etc/nginx/certs/fbctf.csr") failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/nginx/certs/fbctf.csr','r') error:2006D080:BIO routines:BIO_new_file:no such file)
nginx: configuration file /etc/nginx/nginx.conf test failed

And in nginx error.log:
[emerg] 3154#0: BIO_new_file("/etc/nginx/certs/fbctf.csr") failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/nginx/certs/fbctf.csr','r') error:2006D080:BIO routines:BIO_new_file:no such file)

Shouldn't be a quick install\one liner to deploy easily and try it?

from fbctf.

Would be better to create self-signed certificate in default case and provide path to it instead of using .csr file since it breaks nginx configuration.

Note that if you provision in dev mode (i.e. ./extra/provision.sh devpwd``), self signed certificates are used. We forgot to mention this in the README because we do all of our development on a Vagrant VM, and it provisions in dev mode by default. We'll clarify this in the README.

I haven't run into the other issues, but I'll look into them. Thanks for the report!

from fbctf.

I can confirm all these issues. Its propensity to copy certs over to /etc/nginx/certs is also not a great idea with e.g. letsencrypt certs.

With the AsyncMysqlConnectionPool error I am unable to get the project started.

from fbctf.

@STRML could you let us know what version of HHVM and Ubuntu you are running?

from fbctf.

@Dor1s
We recommend using Ubuntu 14.04 and HHVM 3.13 to run the platform at this moment. We are confirming with HHVM team when Ubuntu 16 will be supported.

from fbctf.