• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Serious problem with session idle time. They don't last more than a few minutes

EdwradG

New Pleskian
Hi

We just switched to a new Ubuntu 12.04 LTS server and installed plesk 11.5.30.

I didn't notice it during or tests but now that we switched we noticed that the sessions don't last longer than a few minutes. So I tried to change the session idle time to 120 minutes. But it seems more like 120 seconds to me.

Any idea what other settings I should check out? Apache, nginx, php?

Any help is really appreciated.

Some more info:
- I'm experiencing this same problem in plesk admin as in our applications

Session settings:
Capture.PNG

Session cookies in chrome:
Capture2.PNG
 
Last edited:
Your settings look fine! Try clearing ALL history / cookies (from your browser) and try again logging on ...Let me know if this does not solve the problem!
 
Hi Abdi,

I think I finally know what's happening. Maybe you can confirm this?

When I encountered the problem I was working inside my application's admin whil also doing some work in the plesk admin. What I think happens is that every time I visit the plesk login it wil destroy the session. Is that correct? I think that this combined with the fact that I'm logging in as www.domain.com:8443 makes plesk and my application share the same session, while normally I would always use something like ip:8443 or dedicated-plesk-domain:8443.

So every time I would log into plesk it would kill my application's session and when I relogin into my application it wipes my plesk session.

I did a test logging in with domain.com:8443 and I'm already logged in longer than I managed before.
 
It's actually Google chrome that destroys the session (since you are using the same domain for 2 different systems requiring different sessions)
 
Back
Top