2e00f2003b61c6a56f811213cbed929bc361bc38
wiki/howto/onboarding.md
| ... | ... | @@ -264,3 +264,4 @@ The path to the solution: On my instance in eu-west-2a, I ran aws --debug ec2 de |
| 264 | 264 | - Problem: A load balancer's target group health checks fail. I was told the checks failed with 403 errors. |
| 265 | 265 | Solution: This was occurring because the website didn't have any content in the /var/www/html. Whilst a site was still served (namely the Apache test page) it does throw a 403 error. If you fill the directory with and index.html the test then passes and a 200 code is returned |
| 266 | 266 | - Problem: Target platform reload in Eclipse. Sometimes reloading via Window -> Plug-in Development -> Target Platform doesn't work, so open the target definition itself and try reloading there. Often a restart proves helpful after the reload. In addition, you can clean all projects and rebuild; then rebuild the individual projects that fail. Sometimes the errors are actually just warnings and you can try to run the GWT SDM (remember the other SDM's must be run if everything is brand new). Lastly, try clearing the plugins content found at `WORKSPACE_HOME/.metadata/.plugins/org.eclipse.pde.core/.bundle_pool/plugins`. |
| 267 | +Test |
|
| ... | ... | \ No newline at end of file |