Editing Troubleshooting Elastic Beanstalk Deployment (section)

== Connectivity ==

=== Empty HTTP response ===

'''Symptom'''

Make a request for the URL of the site via curl:

<pre>
$ curl https://www.mydomain.com
</pre>

0 bytes and no headers sent in response. 

'''Possible cause'''

PHP code is exiting without errors, but before returning a response.

'''Solution'''

'''Check nginx logs.'''

* `/var/log/nginx/access.log`
* `/var/log/nginx/error.log`

PHP errors are logged to the nginx error log.

'''Confirm that requests are being made to the correct host.''' If nothing is reported in the log files, try connecting to a non-existent file. Then view the access log to confirm that a 404 error was logged. 

'''Confirm PHP configuration.''' Upload a simple index.php file to the server containing a "Hello world" type of response. Make a request to that page. If the server returns the expected response, then it will be necessary to step through the production PHP to locate the code that is causing the script to exit without a response.

=== ERR_CONNECTION_REFUSED in Chrome ===

Attempting to load the site using https protocol in Chrome results in ERR_CONNECTION_REFUSED error.

Check the security certificates in `/etc/letsencrypt/live/`. There should be a directory with the name of the domain, and another directory named `ebcert` that is a symbolic link to `/etc/letsencrypt/live/securedomainname.com`

If this directory does not exist, refer to [[Elastic Beanstalk Security Certificates]] for instructions on installing the security certificates.

Check that the server is configured to accept requests on port 443, e.g. in `/etc/nginx/conf.d/https_custom.conf`

<p class="alert alert-warning">nginx configuration is set back to defaults during `eb deploy`, meaning the certificates configuration is removed from the server. Also, haven't figured out how to insert custom configuration on the server via .ebextensions configuration directives. It may be necessary to copy this https configuration file manually after running `eb deploy`.</p>

=== 403 HTTP error ===

Receiving a 403 error when attempting to load the hosted site indicates that something unintended was uploaded to the root of the web directory. 

SSH to the server to confirm the content of that directory, e.g. `/var/www/html/`.

=== 500 HTTP error ===

Check PHP error logs at `/var/log/php-fpm/www-error.log`