Database server needs to increase keep-alive connection, because when I work in Joomla 4, it has been automatic logout from control panel many times.
Control panel session is set to 240 minutes, but logout in 2-4 minutes.
Ehā¦ what keep alive connection are you referring to?
With ācontrol panelā I assume you mean the admin panel of Joomla? Not the hosting control panel we provide, right?
Most CMS handle logins with PHP sessions or some custom cookie implementation. Some CMS store session related data in a database. But thatās a choice of the application developer and not something thatās controlled with a setting on the database server.
Our servers are configured with the default value for PHP session lifetime: 24 hours. But individual CMS can make tweaks to increase or decrease this.
The Security Token seems like the CSRF implementation of Joomla. Iām not that much of a Joomla expert but that does seem like a session related thing.
Yes, I mean work with backend admin panel Joomla. Other hostings, for example, free version of cloudaccess.net, will store PHP and CSRF sessions normally and not logout so fast.
I just asking for it, maybe you have solution.
Maybe it happens from special settings on infinityfree, I donāt know.
Can you send this question to ifastnet? Just interesting
Our hosting also stores PHP and CSRF sessions normally. I donāt know why you have these problems.
Can I? Of course! But only if I see a reasonable reason to believe that this is a server issue. So far, all I know is that your site does not seem to be working correctly on our hosting. If I knew that all Joomla sites have this issue, then I would report it. But I canāt bother them because of what might well be a code or configuration issue.
Itās not iFastNetās job (or, frankly, mine) to debug your website. We only provide hosting. Itās your responsibility to build a working website.
I looked at your Joomla configuration and it seems youāre using the Database session handler. This means it doesnāt use regular PHP sessions and the session handling is done entirely by the Joomla code. This means Joomla is responsible for storing, retrieving, checking and cleaning sessions.
This makes me more convinced that this is not a server problem, because there isnāt any server option that controls this.