moving to the new farm – preload issue

PennController for IBEX Forums Support moving to the new farm – preload issue

This topic contains 3 replies, has 2 voices, and was last updated by Jeremy Jeremy 2 weeks, 5 days ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #6607
    Avatar
    pchen
    Participant

    Dear Jeremy,

    I moved one of my experiments to the new farm (com3 under pchen) following this post: https://www.pcibex.net/forums/topic/come-back-later/.
    However, now it seems I can’t load my audio and picture files properly. For every trial, I got stuck on “Please wait while xxxx” for two minutes or so, and the files were not loaded at all after that: I have four pictures to display on each trial and none of them was displayed.

    When I use the link from the old farm (com3 under pchen), the same experiment runs properly. This seems to rule out the problem with AWS S3 bucket, where I host all the files. Is there anything I need to change when moving the experiment to the new farm?

    Thanks,
    Peiyao

    #6609
    Jeremy
    Jeremy
    Keymaster

    Dear Peiyao,

    Did you need to set some CORS settings with your AWS S3 bucket? If you allowed the origin https://expt.pcibex.net, then you should now also allow the origin https://farm.pcibex.net

    Jeremy

    #6616
    Avatar
    pchen
    Participant

    Hi Jeremy,

    Thank you for your quick reply. I totally forgot about the CORS settings. It works again now.

    When I tested the experiment under Incognito mode, it worked great. But when I tested under non-incognito mode, it sometimes still had the loading problem until I cleared the cache. Do you have any explanations for this? I’m just curious.

    Thanks again,
    Peiyao

    #6617
    Jeremy
    Jeremy
    Keymaster

    If you took your experiment in non-incognito mode before you set the right CORS configuration, your browser might have remembered that the requests failed and not bothered sending them again. Clearing the cache made it send new requests, which were successful now that you have updated the CORS settings

    Jeremy

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.