Problem accessing JATOS on Docker from browser

ethanweed

Hi JATOS gurus! I have installed JATOS in a Docker container on an Azure server rented from my university. Everything about the installation seems successful, and if I run "docker ps" it shows that it has been up for 11 hours. If I go to the webaddress, however, I get an "unable to connect" message (Firefox) or a "refused to connect" (Chrome). The funny thing is, I *was* briefly able to connect through Firefox, not long after starting the container. In fact, I still get the JATOS favicon briefly when I go to the container's address in a browser. Any help would be much appreciated!

Best,

Ethan

kri

Hi Ethan,

I'm tempted to say: "Have you tried turning it off and on again?" :D

Okay, this can have many reasons. What comes to my mind (don't feel offended if they are too obvious):

• Did you forward JATOS port 9000 to the standard HTTP port 80? With docker you can do this with the parameter -p 80:9000.
• Since you are on Azure: you can probably see how much memory and disk is used. If one of it is full you should give it a 'better' instance with more memory or disk.
• I know from AWS and maybe this is the case with Azure too, that they not only give you an public IP but also an private IP. You have to use the public IP in your browser.
• If you have JATOS in a docker you most likely do not want to set up IP and port in JATOS' production.conf. If you have, it's probably not what you want. Use docker's -p parameter.
• Do you use any proxy in front of JATOS, e.g. Apache or Nginx? Check the forwarding to localhost and port 9000.

Best,

Kristian

ethan

Hooray, it's solved! I really thought I had tried everything, including, yes, turning it off and on again, several times! As far as I can reconstruct, I think what happened was that I had:

• first started a container without forwarding JATOS from port 9000 to 80
• realized that I should forward to port 80
• started a second container with forwarding (which must have been the one I briefly saw)
• realized I should stop one of the containers.
• stopped the wrong one
• saw that things no longer worked
• stopped the other container
• restarted, but forgot to forward to port 80, while thinking I had

In any case, everything seems to work now. I guess I did just need to turn it on and off, but also needed to use the right switch ;-)

Thanks very much for the help!

/Ethan