JATOS on institution server can't login via web browser

thornt9

Hello all!

I have installed JATOS on my institutional server, and I can officially access it via web browser. It brings up a login page asking for username and password, as it expected from my experience on a local server. I can type in the boxes, but the buttons for sign in and such seem inactive, and the page is unresponsive. Anyone have any experience with this?

Thanks!

kri

Hi!

To be honest, no, I never experienced this so far? Are there any errors in your browser's console?

Best,

Kristian

thornt9

Turns out there are several, looks like mostly related to internal server errors serving content. Best I can find it may be a mixed content (HTTP serving over HTTPS protocols?) or maybe the content isn't in the right place on the server. I am not well versed in this stuff, but I jumped in the deep end by trying to host a shinyR app and some OpenSesame content via Jatos through reverse proxies in nginx. Trial by fire for sure.

This is what I see as the login page, and it is clear the content isn't being served correctly.

kri

Your sign in page is definitely not served correctly. What does the browser's console say in errors?

thornt9

this :

Content-Security-Policy warnings 4

Content-Security-Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified signin

Content-Security-Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified signin

Content-Security-Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified signin

Content-Security-Policy: Ignoring “'unsafe-inline'” within script-src: nonce-source or hash-source specified

and:

module was blocked because of a disallowed MIME type (text/plain)

loading failed for module from (URL/assets/lib/jatos-gui/javascripts/(ITEM).js (several of these

kri

Maybe your proxy config has problems. What are you using, Nginx, Apache? Can you post your config here?

thornt9

I am beginning to suspect it is the nginx config. I will post tomorrow when I am back in the office. Thank you for sticking with me on this!

thornt9

nginx conf file

user www-data;
worker_processes auto;
pid /run/nginx.pid;
error_log /var/log/nginx/error.log;
include /etc/nginx/modules-enabled/*.conf;

events {
   worker_connections 768;
   # multi_accept on;
}

http {

   ##
   # Basic Settings
   ##

   sendfile on;
   tcp_nopush on;
   types_hash_max_size 2048;
   # server_tokens off;
   # server_names_hash_bucket_size 64;
   # server_name_in_redirect off;

   include /etc/nginx/mime.types;
   default_type application/octet-stream;

   ##
   # SSL Settings
   ##
   ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3; # Dropping SSLv3, ref: POODLE
   ssl_prefer_server_ciphers on;

   ##
   # Logging Settings
   ##
   access_log /var/log/nginx/access.log;

   ##
   # Gzip Settings
   ##
   gzip on;
   # gzip_vary on;
   # gzip_proxied any;
   # gzip_comp_level 6;
   # gzip_buffers 16 8k;
   # gzip_http_version 1.1;
   # gzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript;

   ##
   # Virtual Host Configs
   ##

   include /etc/nginx/conf.d/*.conf;
   include /etc/nginx/sites-enabled/*;
}

#mail {
#   # See sample authentication script at:
#    # http://wiki.nginx.org/ImapAuthenticateWithApachePhpScript
#
#   # auth_http localhost/auth.php;
#   # pop3_capabilities "TOP" "USER";
#   # imap_capabilities "IMAP4rev1" "UIDPLUS";
#
#   server {
#       listen    localhost:110;
#       protocol  pop3;
#       proxy     on;
#   }
#
#   server {
#       listen    localhost:143;
#       protocol  imap;
#       proxy     on;
#   }
#}

thornt9

Obviously a lot is commented out - but it does look a bit different from the base file on the jatos pages...that may be the challenge

kri

Hi!

First, I added some formatting to your post and I'd recommend to use formatting in the future to make your code more readable for everyone.

Second, there is a JATOS documentation that includes a page about Nginx: https://www.jatos.org/JATOS-with-Nginx.html. There is also a ton of help for Nginx on the Internet readily available. You seemed to have taken some default Nginx config without changing it much. JATOS will not work this way. When you have some more concrete questions please ask again, but this forum is for JATOS specific questions.

Best,

Kristian

thornt9

As someone who has been using the extensive resources now for NGINX and JATOS, and juggling the requirements for ShinyR and JATOS, as I mentioned in my first response, I feel I was being quite specific and looking for assistance on a decently specific question. I apologize that you do not feel this way. This forum has been literally my last stop on the way to tearing my hair out.

The NGINX config works for ShinyR and as such, seems functional with additional changes to the URL routing within NGINX/sites-enabled.

I appreciate the help, I'll keep digging at it.