+x DaveFraser - 9/28/2022Hi,I get an error when I try to run scripts with InquisitWeb it saysInquisit was unable to communicate with the license server (Error Transferring: 500 - ). The experiment will not be run.InquisitWeb 6.6 I have tried different browsers. My license is active. It worked on the computer previously. I don't think I changed anything. I saw a previous post with this problem but the resolution just said "it should be fixed now"
+x Dave - 9/28/2022+x DaveFraser - 9/28/2022Hi,I get an error when I try to run scripts with InquisitWeb it saysInquisit was unable to communicate with the license server (Error Transferring: 500 - ). The experiment will not be run.InquisitWeb 6.6 I have tried different browsers. My license is active. It worked on the computer previously. I don't think I changed anything. I saw a previous post with this problem but the resolution just said "it should be fixed now"(1) It's either an issue with your script, in which case you need to provide the link to the web experiment. In particular, certain characters (e.g. "+") in the script's file name can cause verification issues, as these will break the URL.(2) If that isn't it, then a firewall on your network is blocking the traffic to the license server and terminating the connection. We've had a few isolated reports of this in the past, and the most concrete example I can give you is that in two of those cases URL filtering on Palo Alto border firewalls was mistakenly flagging the traffic as high risk. It could be any other kind of firewall or network security device as well, however. This is something you'd have to have your local IT / network people look at. The base URL that the Inquisit player will attempt to contact for license verification is https://mili2nd.net/inquisit6/verifylicense ; mili2nd.net is currently set up as a load balancer and will distribute traffic to different IPs (which may change and come and go, depending on load).
+x DaveFraser - 9/28/2022+x Dave - 9/28/2022+x DaveFraser - 9/28/2022Hi,I get an error when I try to run scripts with InquisitWeb it saysInquisit was unable to communicate with the license server (Error Transferring: 500 - ). The experiment will not be run.InquisitWeb 6.6 I have tried different browsers. My license is active. It worked on the computer previously. I don't think I changed anything. I saw a previous post with this problem but the resolution just said "it should be fixed now"(1) It's either an issue with your script, in which case you need to provide the link to the web experiment. In particular, certain characters (e.g. "+") in the script's file name can cause verification issues, as these will break the URL.(2) If that isn't it, then a firewall on your network is blocking the traffic to the license server and terminating the connection. We've had a few isolated reports of this in the past, and the most concrete example I can give you is that in two of those cases URL filtering on Palo Alto border firewalls was mistakenly flagging the traffic as high risk. It could be any other kind of firewall or network security device as well, however. This is something you'd have to have your local IT / network people look at. The base URL that the Inquisit player will attempt to contact for license verification is https://mili2nd.net/inquisit6/verifylicense ; mili2nd.net is currently set up as a load balancer and will distribute traffic to different IPs (which may change and come and go, depending on load).Thanks for the reply. The scripts I'm using are the ones from the library, so I suspect that the script is not the problem. In the case of the firewall, it's curious because this hasn't been a problem in the past. I will check with the IT guys here at work and also try at home to see if that makes a difference.
+x Dave - 9/28/2022+x DaveFraser - 9/28/2022+x Dave - 9/28/2022+x DaveFraser - 9/28/2022Hi,I get an error when I try to run scripts with InquisitWeb it saysInquisit was unable to communicate with the license server (Error Transferring: 500 - ). The experiment will not be run.InquisitWeb 6.6 I have tried different browsers. My license is active. It worked on the computer previously. I don't think I changed anything. I saw a previous post with this problem but the resolution just said "it should be fixed now"(1) It's either an issue with your script, in which case you need to provide the link to the web experiment. In particular, certain characters (e.g. "+") in the script's file name can cause verification issues, as these will break the URL.(2) If that isn't it, then a firewall on your network is blocking the traffic to the license server and terminating the connection. We've had a few isolated reports of this in the past, and the most concrete example I can give you is that in two of those cases URL filtering on Palo Alto border firewalls was mistakenly flagging the traffic as high risk. It could be any other kind of firewall or network security device as well, however. This is something you'd have to have your local IT / network people look at. The base URL that the Inquisit player will attempt to contact for license verification is https://mili2nd.net/inquisit6/verifylicense ; mili2nd.net is currently set up as a load balancer and will distribute traffic to different IPs (which may change and come and go, depending on load).Thanks for the reply. The scripts I'm using are the ones from the library, so I suspect that the script is not the problem. In the case of the firewall, it's curious because this hasn't been a problem in the past. I will check with the IT guys here at work and also try at home to see if that makes a difference. Firewalls get updated with new software versions and/or new rulesets periodically, too. In the other cases I'm aware of, it hadn't been an issue previously either. Particularly URL filtering and risk ranking often relies on heuristics and it is not always transparent why a certain URL is suddenly deemed suspicious although it hadn't been before.If you're using library scripts, those shouldn't be the issue, but feel free to give me the link to the experiment and I'll be happy to check if it verifies successfully for me.