Problems setting up JATOS with Apache and AWS
Hi, I'm trying to get JATOS to work using the documentation on the JATOS web site.
Without Apache running, I can get get JATOS to run using the numeric IP address of my AWS instance, but not the named hosted zone, (but I'm not sure why.)
But since I can't download the saved data from JATOS using this configuration, it seems that I should be running Apache2.
When Apache2 is running, I can't get JATOS to load. I'm really going around in circles here, and I'm not even sure what information I need to provide here to make my question more answerable. I'd appreciate any help you can give.
Comments
Update: I have solved both problems. The AWS problem was related to a missing A record for my domain (I had only records for the subdomains). The JATOS problem was solved by changing the production.conf file so that the host was not specified. This came from https://forum.cogsci.nl/discussion/6347/cannot-open-jatos-via-ecs-server
The JATOS instructions probably could do with some updating on how to configure to use Apache.
Hi,
Could you please tell us a bit more what you have changed in the
production.confin order to get it working? What do you mean with 'so that the host was not specified'. I'm asking out of curiosity but also for everyone else who might have the same problem in the future. And what would you change in the JATOS Apache docs (do you mean this one: https://www.jatos.org/JATOS-in-Amazons-Cloud-without-Docker.html)?Hi, sorry for taking so long to reply but I was busy trying to get all this working to actually collect data. :)
With respect to your question, item 7 of the linked documentation page says:
Configure IP and port in
conf/production.conf: Use the 'Private IP' from your instance description (the one that starts with 172.x.x.x) and port 80But if you are using Apache this will not work, and instead you need to keep the defaults:
# HTTP address and port
# ~~~~~~~~~~~~~~~~~~~~~
# Defaults are 0.0.0.0 (all local IPs) and 9000
play.server.http.address = "0.0.0.0"
play.server.http.port = 9000
And since it's impractical not to be running Apache I think that the instructions for setting up JATOS with AWS should probably point directly to the Apache setup.
Also, self-signed certificates now are really trapped by most browsers, so it's probably helpful to explain that you need an real certificate to properly allow HTTPS traffic to your server. A nice free certificate issuer is https://certbot.eff.org/ from the Electronic Frontier Foundation.
Hi,
Thank you for your help with the documentation. I added your suggestions to 'JATOS on AWS' and 'JATOS with Nginx' and 'JATOS with Apache'. Certbot is great!
Best,
Kristian