Terra Session Timeouts Completed

Post author
Josh Evans

Some users have reported receiving a session timeout message after a long period of inactivity - a few hours - and needing to log back into the application. 

Our engineering teams are aware of the issue and are working to resolve it.  Currently logging back into the application resolves the issue until another period of inactivity. 

Comments

38 comments

  • Comment author
    Josh Evans
    • Official comment

    Our engineering teams have updated the application and sessions should no longer timeout after a few hours of inactivity.

  • Comment author
    Matt Preimesberger

    Hello,

    The last two days I have been getting timed out and have to log back in every couple of hours.

    Thanks,

    Matt Preimesberger  

    0
  • Comment author
    Josh Evans

    Hi Matt,

    Thanks for reaching out! I have a few follow up questions that should help me find the best solution for you: 

    • Which browser do you use with the application? (Currently, our only supported browser is Chrome.)
    • Do you have any browser plugins that affect cookies?
    • Are you currently running any ad blocking software?
    • Is your browser set to block third party cookies?
    • Could you please try clearing your cookies and cache?

    Please let me know if you have any questions.

    Best,

    Josh

    0
  • Comment author
    Matt Preimesberger

    Hi Josh,

    Thanks for the reply.

    I am using Chrome and I did have an Ad blocker enabled which I have now disabled.  I've also cleared my cookies and cache and will let you know if I continue to experience session timeouts.

    Thanks again.

    Regards,

    Matt Preimesberger

    0
  • Comment author
    Josh Evans

    Hi Matt,

    Thanks for letting me know! Removing Adblock and clearing the cookies and cache are two great troubleshooting steps for this issue! Please keep me in the loop if this issue comes up again.

    Best,

    Josh

    0
  • Comment author
    Matt Preimesberger

    Hi Josh,

    Unfortunately, the timeouts are continuing to occur.  I get the following message:

    {"source":"leonardo","message":"Your account is not authenticated","statusCode":401,"exceptionClass":"class org.broadinstitute.dsde.workbench.leonardo.model.AuthenticationError","traceId":null}

    Thanks again for your help.

    Regards,

    Matt Preimesberger

    0
  • Comment author
    Josh Evans

    Hi Matt,

    Thanks for providing the error message, it's very helpful! What part of the application are you in when you see this error message? Has it always been this same message or has their been a change after you followed the troubleshooting steps? What browser plugins do you have installed in the browser.

    Please let me know if you have any questions.

    Best,

    Josh

    0
  • Comment author
    Matt Preimesberger

    Hi Josh,

    I see the error message after returning from a period of inactivity.  The sequence is as follows:

    I will click on an item in my history to check status or refresh etc. and get an initial error message (see attached screenshot) within my Galaxy instance.

    After clicking OK, the error message disappears and I return to the Galaxy instance.  I try to click or refresh something else and the process repeats a couple of times before I get booted to a blank screen with the aforementioned error:

    {"source":"leonardo","message":"Your account is not authenticated","statusCode":401,"exceptionClass":"class org.broadinstitute.dsde.workbench.leonardo.model.AuthenticationError","traceId":null}

    Upon closing the error message tab and returning to my Terra workspace tab, I find that I've been timed out (see top right of image below) and have to re-log in.

    I believe that sequence of events has been the same before and after clearing cookies/cache and turning off Adblocker.  The browser plugins I have are: AdblockPlus, Adobe PDFviewer, Cisco Webex extension, Google Scholar, SoundBooster, Zoom Scheduler, and Zotero.

    Thanks again for your help.

    Regards,

    Matt

     

    0
  • Comment author
    Josh Evans

    Hi Matt,

    Thanks for the information! This is very helpful! Do you only see these timeouts from the Galaxy environment or in other parts of Terra as well? If it's just Galaxy, how often do the re-create the environment from scratch? (By that I mean, how often do you delete it and create it from scratch?) Could we have the name of the current Galaxy environment. You can find that information from this page: https://app.terra.bio/#clusters and click the View link under details for the workspace's Cloud Environment.

    Please let me know if you have any questions.

    Best,

    Josh

    0
  • Comment author
    Matt Preimesberger

    Hi Josh,

    I have only seen these timeouts in Galaxy as that is all I've used thus far.  I have not deleted the environment and re-created it yet.

    Here is the information you requested:

    Name: terra-app-9dba3395-bcb3-442a-9de8-04f3f4975532
    Billing ID: terra-25c8b26c
    Persistent Disk: saturn-pd-e9c0df22-6305-4cf6-bb08-b63138533517
     
    I have been hesitant to delete the environment while the Terra support team is troubleshooting (I have another open ticket dealing with very long queue times).
     
    Thanks for your help.
     
    Regards,

    Matt
    0
  • Comment author
    Josh Evans

    Hi Matt,

    Thanks for the update! Normally, deleting and recreating the entire environment is the first troubleshooting step I would try, but I agree that we should wait for the troubleshooting to be finished in the other ticket. Let me know once that's been completed and we can try re-creating the environment then.

    Alternatively, you could clone the workspace while you wait and create a Galaxy Environment in that new workspace. (Note there will a cost associated with running an additional Galaxy Environment.) You could then test if the timeouts happen in that environment. 

    However, it might be best to wait for now. Please let me know if this information was help, or if you have any questions.

    Best,

    Josh 

    0
  • Comment author
    Matt Preimesberger

    Hi Josh

    I noticed today that I get timed out from the Terra workspace dashboard as well (with the Galaxy instance paused).

    Your comments above make sense.  I'll try deleting/recreating and/or cloning depending on the other ticket's timeline.

    Thanks,

    Matt

    0
  • Comment author
    Josh Evans

    Hi Matt,

    Thanks for the update! If you're seeing the timeouts from the workspace dashboard as well, then this might not be related to just the Cloud Environment.

    What are the current cookie setting from your browser? On Chrome you can go to Settings > Privacy and Security > Cookie and other site data.  Make sure that it's set to allow third party cookies. 

    Also, do you use a VPN client or have any modifications to your computer or network's DNS settings?

    Please let me know if you have any questions.

    Best,

    Josh

    0
  • Comment author
    Josh Evans

    Hi Matt,

    Another option we can try to rule out Chrome is to try to run the application in FireFox. While Chrome is our preferred browser, the application should work fine in FireFox and we can use this to determine if the issue is isolated to Chrome. 

    Thank you for your patience will we try these troubleshooting steps. I know there have been a lot of them, but we want to make sure you're having the best experience possible with Terra.

    Please let me know if that information is helpful to you, or if you have any questions.

    Best,

    Josh

    0
  • Comment author
    Matt Preimesberger

    Hi Josh,

    Thanks for following up.  I have my browser set to allow third party cookies.  I'm not using a VPN and have not made any changes to my computer's DNS settings.

    I'll give Firefox a try if the other solutions above do not work.

    Regards,

    Matt

    0
  • Comment author
    Josh Evans

    Hi Matt,

    Thanks for the reply! I look forward to hearing how your testing goes.

    Best,

    Josh

    0
  • Comment author
    Ray Jones

    I am seeing similar timeouts in Terra notebooks (after only short times, such as ~20 minutes) on Chrome.  I will try Firefox, as well.

    0
  • Comment author
    Ray Jones

    This is also a problem in Firefox.    

    0
  • Comment author
    Josh Evans

    Hi Ray,

    Thanks for writing in! I have a few questions that might help me find the best solution for you:

    • When did you first notice this issue?
    • Do you only get the timeouts with notebooks?
    • Are the two browsers set to accept third party cookies?
    • Does either browser have any addons that affect cookies?
    • Does either browser have any ad blocking software?
    • Does your computer use a VPN or any application that would affect DNS?

    Please let me know if you have any questions.

    Best,

    Josh

    0
  • Comment author
    Ray Jones

    I noticed a week or two ago.

    Timeouts happen on app.terra.bio in general (notebooks and workspaces).

    No addons that affect cookies.  I removed ad-blockers, as well.

    No VPN.

    Ray

    0
  • Comment author
    Josh Evans

    Hi Ray,

    Thanks for getting back to me! In Chrome, please try clearing the Cookies and Cache and making sure that browser is set to accept third party cookies.  Also, what version of Chrome are you currently using? Have you rebooted your computer since you noticed the issue? 

    Please let me know if you have any questions.

    Best,

    Josh

    0
  • Comment author
    Ray Jones

    This seems to have resolved.  Clearing Cookies and Cache didn't have any effect, but a few days ago it seems to have resolved, regardless.

    0
  • Comment author
    Matt Preimesberger

    Hi,

    The problem is not resolved for me.  I got timed out today while actively working.  I was working in my cloned workspace with a freshly deleted and recreated Galaxy environment.  Same error codes as before: 

    {"source":"leonardo","message":"Your account is not authenticated","statusCode":401,"exceptionClass":"class org.broadinstitute.dsde.workbench.leonardo.model.AuthenticationError","traceId":null}

    Regards,

    Matt Preimesberger

    0
  • Comment author
    Josh Evans

    Hi Matt,

    I'm sorry to hear that you're sit getting this error message.  Are you seeing the error in FireFox as well as Chrome? Please give FireFox a try if you haven't already and let me know if you run into the error again.

    Please let me know if you have any questions.

    Best,

    Josh

    0
  • Comment author
    Matt Preimesberger

    Hi Josh,

    I cannot open an (already running) Galaxy environment with Firefox as my browser.  I get the following error:

    Thanks,

    Matt Preimesberger

    0
  • Comment author
    Matt Preimesberger

    Hi Josh,

    Here are additional details after a timeout using Chrome:

    {
      "userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/106.0.0.0 Safari/537.36",
      "onLine": true,
      "version": "21.09",
      "xhr": {
        "readyState": 4,
        "responseText": "{\"source\":\"leonardo\",\"message\":\"Your account is not authenticated\",\"statusCode\":401,\"exceptionClass\":\"class org.broadinstitute.dsde.workbench.leonardo.model.AuthenticationError\",\"traceId\":null}",
        "responseJSON": {
          "source": "leonardo",
          "message": "Your account is not authenticated",
          "statusCode": 401,
          "exceptionClass": "class org.broadinstitute.dsde.workbench.leonardo.model.AuthenticationError",
          "traceId": null
        },
        "status": 401,
        "statusText": "error"
      },
      "options": {
        "parse": true,
        "url": "/proxy/google/v1/apps/terra-8eb6f7f4/terra-app-b375525d-edef-4897-b87c-82c793e86675/galaxy/history/current_history_json",
        "view": "dev-detailed",
        "emulateHTTP": false,
        "emulateJSON": false,
        "textStatus": "error",
        "errorThrown": ""
      },
      "url": "https://notebooks.firecloud.org/proxy/google/v1/apps/terra-8eb6f7f4/terra-app-b375525d-edef-4897-b87c-82c793e86675/galaxy/proxy/google/v1/apps/terra-8eb6f7f4/terra-app-b375525d-edef-4897-b87c-82c793e86675/galaxy/history/current_history_json",
      "model": {
        "model_class": "History",
        "id": null,
        "name": "Unnamed History",
        "state": "new",
        "deleted": false,
        "contents_active": {},
        "contents_states": {},
        "nice_size": "(empty)"
      },
      "user": {
        "id": "a9779b921b64eb06",
        "username": "matt.preimesberger",
        "total_disk_usage": 10595419979,
        "nice_total_disk_usage": "9.9 GB",
        "quota_percent": null,
        "is_admin": true,
        "preferences": {},
        "tags_used": [],
        "deleted": false,
        "purged": false,
        "quota": "unlimited"
      }
    }
    0
  • Comment author
    Josh Evans

    Hi Matt,

    Thanks for the log files! We're investigating this issue on our end to see if we can find a solution.  I'll contact you once I have an update.

    Please let me know if you have any questions.

    Best,

    Josh

    0
  • Comment author
    Josh Evans

    Hi Matt,

    I wanted to give you an update on this ticket.  We've gotten a few reports of this error, so I've opened a bug report with our engineering teams to take a look.  I'll let you know once I have any updates or this bug has been fixed.

    Please let me know if you have any questions.

    Best,

    Josh

    0
  • Comment author
    Matt Preimesberger

    Hi Josh,

    Thanks for the update. 

    Regards,

    Matt Preimesberger

    0
  • Comment author
    Ray Jones

    Hi Josh,

    Are there any updates on this issue?  I and several of my group members are encountering it again, quite frequently now, to the point that it's interfering with our ability to do work on Terra.

    Thanks,
    Ray Jones

    0

Please sign in to leave a comment.