This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Since installing 15.2.5, lots of "Your session may have timed out"

ERROR:  Operation was not successful, an unknown error occurred.  Your session may have timed out.  Please try logging in again.

Have always seen that once in a great while.  We host 1,300+ sites.  Since installing 15.2.5 on all our host servers, I'm getting multiple of these per day.  Nothing yet is a surefire "this will get you going" solution.  Have one client that has several users having this same problem.

Before I start assuming anything, is anyone else seeing similar behavior since installing 15.2.5?

  • Had two more clients bring up the same problem today.  I was fortunate to have one of them this time open to having a phone call with me.  He was working from home, connected to work VPN.  I asked if he had a home machine he could try from.  He did.  Logged into the site no problem.  So he's going to contact their IT management tomorrow and get someone in touch with me.  Also asked him to try with his work machine at the end of his workday, after he disconnects from work VPN.

  • One client's IT team got involved today and resolved their problem getting to our site by SSL/Forward Bypassing our site on their proxy server.  I spoke, albeit briefly, with their IT analyst who was on the task.  Between the two of us, the only system change on either side that occurred in the time period when these connection attempts began to fail was our ServU MFT upgrade from 15.2.4 to 15.2.5.

    I'll pose this to the next client IT team I have a chance to engage with and share anything I learn.

    EDIT - since forum is not allowing me to post another reply:

    Had another client yesterday that was able to add a bypass for our site on their proxy server, and were able to connect successfully again.  However, their security team will not allow a permanent bypass to be placed.  Instead, I asked if they can connect using SFTP - which we also listen for.

    I believe this confirms now that something changed in 15.2.5 that is affecting connection from clients who use a proxy server.  At least some/most of them.  All these that I've been working with were connecting to us fine prior to our upgrade to 15.2.5

  • Thanks for the detailed report . I've also seen this error. It seems to be relativly rare but nearly always is related to the user having some kind of Web Filtering / SSL decryption in place.

    There was a change in 15.2.5 that related to XSS protection changes that may be being triggered by changes to headers etc by the filters - although this is just a theory.

    Have you reported this to Solarwinds Support? One reply I had from them said some users had been able to fix this issue by clearing their cache & cookies - I wondered if maybe the cache had an old version of the web client files. I've not been able to verify that myself as I do not get this error.

  • Yes, I did create a support ticket following my most recent reply on this thread.  And I did get the cache/cookies recommendation as well, which had no effect.

    Since my reply on 1/7/22, I've had several more clients and one vendor who have come up with the exact same problem authenticating.  All of them have proxy servers in their environment.  It has naturally ramped up the pressure here considerably.  I've been in contact with the IT teams at a few of these and gained valuable feedback.  Some have been able to add a bypass for our hosts on their proxy, which enables their users again.  Others are not allowed to bypass, and I've been trying to help users come in on SFTP instead.  It's a mess.  SW recommended I roll back to the previous version, and I have moved back to 15.2.4 HF1 on half of our servers - to assuage the most pressing needs.

    My most recent response from SW was to suggest a reconfig to our clients of their proxy servers.  This is an untenable suggestion.  Most of these are large organizations, whose users are working fine with every internet resource they need anywhere in the world, except this version of Serv-U MFT.

    Of further interest, I have been communicating with one IT analyst at one of our clients who has been more than willing to help test various scenarios.  Yesterday I asked her to try connecting to the Serv-U 15.3 demo site,  She had the exact same error.  So this means the bug that occurred in 15.2.5 continues to exist in 15.3.  As a further test, she added a bypass on their proxy for that address and was able to connect successfully.  The host server they use here is one that I've rolled back to 15.2.4 HF1, and they are working for now.  But we are at am impasse unless and until SW is ready to admit this is an issue and commits to fixing it.

  • This seems to be a common problem since 15.2.5 continues to exist in 15.3.

    Please could this be looked into a fixed? I'm getting a increasing number of user reporting the same issue as well.

  • Thanks for letting know, checking it.

  • This seems be problem related to loadbalancer settings, I will give an update here once our solution investigation and testing complete.

  • Thanks really appreciate you looking into this.

  • Thanks for investigation. Does "related to loadbalancer" mean, that this problem only exists with loadbalancer enabled in Serv-U? I have this problem without any loadbalancer.

  • I've seen this without the Serv-U load balancer, I think may have been referring to external load balancers. For example, I have seen this when a user was behind a service like

  • We have identified this problem in configuration with either external loadbalancer or proxy.

  • In case of this problem please contact customer support they should be able to help based on our last investigation and solution we prepared.

Reply Children