Help Needed getting JATOS to work on Windows Server
Hi, I am looking for help getting JATOS working on a windows 2016 server with IIS.
I have followed the “Install JATOS on a server” instructions and have it sitting in my wwwroot folder where it works fine locally with a port such as 9000 (eg 1.2.3.4:9000/jatos) as configured via the loader.bat / production.conf files
However when I try and open the site over the internet (eg 1.2.3.4/jatos) I get the message “HTTP Error 403.14 – Forbidden - The Web server is configured to not list the contents of this directory” presumably because IIS doesn’t recognise that there is any valid web page files (html, aspx, php etc) in the jatos directory.
If I change the loader.bat / production.conf files to use port 80 (the default port for IIS) and restart the server when I open the site at 1.2.3.4/jatos or 1.2.3.4:80/jatos I still get the error message above and now the loader.bat file wont start anymore (since I assume it is clashing with IIS),
the JATOS application logs show
[ERROR] - a.i.TcpListener - Bind failed for TCP channel on endpoint [/1.2.3.4:80]
java.net.BindException: Address already in use: bind
and the Loader log shows –
Oops, cannot start the server.
akka.stream.impl.io.ConnectionSourceStage$$anon$2$$anon$1: Bind failed because of java.net.BindException: Address already in use: bind
Caused by: java.net.BindException: Address already in use: bind
I don’t have any firewalls running or anything installed on the server apart from IIS
Can anyone help me get JATOS working properly thanks.
Comments
I'm by no means an expert in Windows administration, but I think in what you said, 'since I assume it is clashing with IIS', you were probably right. IIS is bound to port 80 and JATOS can't bind to it anymore. JATOS does not need IIS - it runs independently. So I guess you have to turn off IIS or at least bind it to another port. Then JATOS is free to bind to 80.
Best,
Kristian
Hi Kristian, thanks for the quick reply, i have uninstalled IIS and JATOS is now running on the server under port 80 (eg 1.2.3.4/jatos) i don't understand however how i can make it accessible to anyone else over the internet (which is my aim) without using IIS.
JATOS is its own server. IIS is just Windows' standard web server. In the Linux world IIS is comparable with Apache. But from your question I deduct that you are new in this administration world. Is there maybe an IT department/guy that can help you setting this up?
Got it working, it turns out when i uninstalled IIS windows reset the firewall settings so the port was blocked
David, that is great! Sorry for sounding a bit harsh in the last post. But I'd like to ask you a question: It's a unusual these days to use Windows instead of Linux as a server OS. Why did you choose this? I'm just curious. JATOS works on both.
Hi Kristian, the university where i work is a windows environment (for better or worse!) so there wasn't any choice
Hi Kristian@kri, I have the similar problem on the Linux server when start the JATOS server. Here is the last part of log show:
How should I solve this issues?
Thanks so much! Bo.
Hi Bo,
Your issue is likely different from David's. It looks like you want to start JATOS on port 80 on Linux, correct? Since port 80 belongs to the privileged ports you need to start JATOS with root user (or some similar user). If you want to run JATOS with a normal user use a port 1023 (e.g. the default port 9000) and use Apache / Nginx in front.
Best,
Kristian
Hi, Kristian@kri, I have switch the Linux CentOS 8.2 (before on a Ubuntu system) and start JATOS on port 80 with root user. However, I still get some errors as below.
I try start JATOS on port 9000 with root user, and I got the similar errors as above.
When I start JATOS use the default setting (127.0.0.1:9000) , I only some warnings.
Is this caused by Java environment or something else? How should I solve this issues?
Thank you so much!
Hi, Kristian@kri, I have found the cause of this issue. I set the ip use the Public IP not the Private IP of the server. This problem has bothered me for several days. Is the warnings should I care about? Thank you so much!
Ah, yes you are on some cloud server then? Did not think about this. Nice you solved it.
You can ignore warning from 'com.google.inject'. Do you have others?
Thank you, Kristian. There was no other warnings or errors.