Millisecond Forums » Millisecond Forums » Inquisit 6 » HTTP 403 status error

HTTP 403 status error

LePossekel — Tue, 15 Oct 2024 19:02:45 GMT

hello everyone,
we have the following problem: our web study with the name DSST_Masterarbeit is currently running. Since today an error occurred with HTTP 403 status. Locally, the script is running normally. It is not clear to us what the error could be and which data cannot be found... We are in an ongoing survey and would be very happy about quick help. Thank you very much!

RE: HTTP 403 status error

Dave — Tue, 15 Oct 2024 19:02:45 GMT

+x[quote]

[b]Dave - 10/15/2024[/b]
+x[quote]

[b]AKrishna - 10/15/2024[/b]
I imagine recreating the experiment on the US server would not help here due to different launch pages, correct
[/quote]

That would not work, I'm afraid.
[/quote]

This should finally be fully resolved now. Our sincere apologies for the downtime.

RE: HTTP 403 status error

Dave — Tue, 15 Oct 2024 13:20:47 GMT

+x[quote]

[b]AKrishna - 10/15/2024[/b]
I imagine recreating the experiment on the US server would not help here due to different launch pages, correct
[/quote]

That would not work, I'm afraid.

RE: HTTP 403 status error

AKrishna — Tue, 15 Oct 2024 12:41:25 GMT

I imagine recreating the experiment on the US server would not help here due to different launch pages, correct

RE: HTTP 403 status error

AKrishna — Tue, 15 Oct 2024 11:58:23 GMT

+x[quote]

[b]Dave - 10/15/2024[/b]
+x[quote]

[b]AKrishna - 10/15/2024[/b]
Update: the issue seems to be affecting ALL of our tests across two accounts.
[/quote]

Yes, it's a launch page bug -- essentially a typo -- introduced yesterday. The cause for the 403s is that the launch pages mistakenly point the app to download assets from the US region (where your assets do not reside), instead of the EU region (where your assets actually are). We'll get this fixed ASAP, but it will be a couple of hours given that it's only 5AM PST.
[/quote]

OK, that's good to know, thanks! I'll let the study coordinators know.

RE: HTTP 403 status error

Dave — Tue, 15 Oct 2024 11:57:15 GMT

+x[quote]

[b]AKrishna - 10/15/2024[/b]
Update: the issue seems to be affecting ALL of our tests across two accounts.
[/quote]

Yes, it's a launch page bug -- essentially a typo -- introduced yesterday. The cause for the 403s is that the launch pages mistakenly point the app to download assets from the US region (where your assets do not reside), instead of the EU region (where your assets actually are). We'll get this fixed ASAP, but it will be a couple of hours given that it's only 5AM PST.

RE: HTTP 403 status error

AKrishna — Tue, 15 Oct 2024 11:52:49 GMT

Update: the issue seems to be affecting ALL of our tests across two accounts.

RE: HTTP 403 status error

AKrishna — Tue, 15 Oct 2024 11:39:15 GMT

+x[quote]

[b]Dave - 10/15/2024[/b]
+x[quote]

[b]AKrishna - 10/15/2024[/b]
+x[quote]

[b]LePossekel - 10/15/2024[/b]
hello everyone,
we have the following problem: our web study with the name DSST_Masterarbeit is currently running. Since today an error occurred with HTTP 403 status. Locally, the script is running normally. It is not clear to us what the error could be and which data cannot be found... We are in an ongoing survey and would be very happy about quick help. Thank you very much!
[/quote]

Just to add on here, as I was involved in the initial debugging:

The full error message is "Network Error with HTTP Status: 403: 'Permission Denied' in bool __cdecl inquisit::Path::loadFileHttp(class QByteArray &,const class QString &,const class QString &,const class QString &,int,bool)", Code 46. In the past, this has been linked to files that Inquisit needed being misnamed in the upload (https://forums.millisecond.com/Topic36447.aspx) or with filenames containing characters that break HTML code (https://forums.millisecond.com/Topic31697.aspx). I couldn't find any such issues in this script or in the uploaded files; it's only .png files with simple numeric names and the script itself. I tried replacing the original script file (which had spaces) with one that didn't, which didn't help. The files are all accessible if I navigate to them directly in my web browser.

What concerns me most about this case is that the web experiment was running fine up until yesterday. The user swears that they didn't change anything about the Inquisit script, although there was a change in the Unipark questionnaire that links to the script. However, I don't think that's the problem, as I get the same issue when I open the Inquisit launch page directly.

[/quote]

It would be helpful if you could link the experiment at issue. Thank you.
[/quote]

https://mili2nd.eu/g6gc?fbnr=1&lfdn=1234

RE: HTTP 403 status error

Dave — Tue, 15 Oct 2024 11:37:56 GMT

+x[quote]

[b]AKrishna - 10/15/2024[/b]
+x[quote]

[b]LePossekel - 10/15/2024[/b]
hello everyone,
we have the following problem: our web study with the name DSST_Masterarbeit is currently running. Since today an error occurred with HTTP 403 status. Locally, the script is running normally. It is not clear to us what the error could be and which data cannot be found... We are in an ongoing survey and would be very happy about quick help. Thank you very much!
[/quote]

Just to add on here, as I was involved in the initial debugging:

The full error message is "Network Error with HTTP Status: 403: 'Permission Denied' in bool __cdecl inquisit::Path::loadFileHttp(class QByteArray &,const class QString &,const class QString &,const class QString &,int,bool)", Code 46. In the past, this has been linked to files that Inquisit needed being misnamed in the upload (https://forums.millisecond.com/Topic36447.aspx) or with filenames containing characters that break HTML code (https://forums.millisecond.com/Topic31697.aspx). I couldn't find any such issues in this script or in the uploaded files; it's only .png files with simple numeric names and the script itself. I tried replacing the original script file (which had spaces) with one that didn't, which didn't help. The files are all accessible if I navigate to them directly in my web browser.

What concerns me most about this case is that the web experiment was running fine up until yesterday. The user swears that they didn't change anything about the Inquisit script, although there was a change in the Unipark questionnaire that links to the script. However, I don't think that's the problem, as I get the same issue when I open the Inquisit launch page directly.

[/quote]

It would be helpful if you could link the experiment at issue. Thank you.

RE: HTTP 403 status error

AKrishna — Tue, 15 Oct 2024 10:00:27 GMT

+x[quote]

[b]LePossekel - 10/15/2024[/b]
hello everyone,
we have the following problem: our web study with the name DSST_Masterarbeit is currently running. Since today an error occurred with HTTP 403 status. Locally, the script is running normally. It is not clear to us what the error could be and which data cannot be found... We are in an ongoing survey and would be very happy about quick help. Thank you very much!
[/quote]

Just to add on here, as I was involved in the initial debugging:

The full error message is "Network Error with HTTP Status: 403: 'Permission Denied' in bool __cdecl inquisit::Path::loadFileHttp(class QByteArray &,const class QString &,const class QString &,const class QString &,int,bool)", Code 46. In the past, this has been linked to files that Inquisit needed being misnamed in the upload (https://forums.millisecond.com/Topic36447.aspx) or with filenames containing characters that break HTML code (https://forums.millisecond.com/Topic31697.aspx). I couldn't find any such issues in this script or in the uploaded files; it's only .png files with simple numeric names and the script itself. I tried replacing the original script file (which had spaces) with one that didn't, which didn't help. The files are all accessible if I navigate to them directly in my web browser.

What concerns me most about this case is that the web experiment was running fine up until yesterday. The user swears that they didn't change anything about the Inquisit script, although there was a change in the Unipark questionnaire that links to the script. However, I don't think that's the problem, as I get the same issue when I open the Inquisit launch page directly.