Advertisement
User login very slow
Moderator: General Support Moderators
Forum rules
Forum Rules
Absolute Beginner's Guide to Joomla! <-- please read before posting.
Forum Post Assistant - If you are serious about wanting help, you should use this tool to help you post.
Windows Defender SmartScreen Issues <-- please read this if using Windows 10
Forum Rules
Absolute Beginner's Guide to Joomla! <-- please read before posting.
Forum Post Assistant - If you are serious about wanting help, you should use this tool to help you post.
Windows Defender SmartScreen Issues <-- please read this if using Windows 10
-
- Joomla! Intern
- Posts: 93
- Joined: Sun Jun 25, 2006 5:51 pm
User login very slow
Why might user login have become very slow? I have a server where user login is taking about 17 seconds.
Yet running with debug, the profile suggests that handling the request is taking 309 milliseconds. The database queries are said to be taking 57 milliseconds. There is no sign of server problems - load is low, memory is ample, CPU load is minimal, disk latency is in microseconds and utilisation below 1%.
Other pages load more or less instantly. What could be causing this?
Yet running with debug, the profile suggests that handling the request is taking 309 milliseconds. The database queries are said to be taking 57 milliseconds. There is no sign of server problems - load is low, memory is ample, CPU load is minimal, disk latency is in microseconds and utilisation below 1%.
Other pages load more or less instantly. What could be causing this?
Advertisement
- AMurray
- Joomla! Master
- Posts: 10488
- Joined: Sat Feb 13, 2010 7:35 am
- Location: Australia
Re: User login very slow
It could simply be your internet connection, not the web server.
What Joomla 5.x are you using?
Is it the standard Login module, or a third party login module you're using?
What Joomla 5.x are you using?
Is it the standard Login module, or a third party login module you're using?
Regards - A Murray
Global Support Moderator
Global Support Moderator
-
- Joomla! Intern
- Posts: 93
- Joined: Sun Jun 25, 2006 5:51 pm
Re: User login very slow
The problem has been noticed from various different locations. Other pages load very quickly.
Joomla version is 5.2.1 and login is the standard Joomla module.
Joomla version is 5.2.1 and login is the standard Joomla module.
- AMurray
- Joomla! Master
- Posts: 10488
- Joined: Sat Feb 13, 2010 7:35 am
- Location: Australia
Re: User login very slow
Is it also apparent on different devices - desktop laptop etc?
Can you please post the FPA report? (FPA = Forum Post Assistant, as per Forum Rules in the red box at the top of the forum screen).
Is it the same for front-end as backend?
What template are you using for the front-end?
On my own sites, I haven't noticed any significant time lag with log-in.
Can you please post the FPA report? (FPA = Forum Post Assistant, as per Forum Rules in the red box at the top of the forum screen).
Is it the same for front-end as backend?
What template are you using for the front-end?
On my own sites, I haven't noticed any significant time lag with log-in.
Regards - A Murray
Global Support Moderator
Global Support Moderator
-
- Joomla! Intern
- Posts: 93
- Joined: Sun Jun 25, 2006 5:51 pm
Re: User login very slow
Problem exists on PC or smartphone or tablet. It is specifically on the user (front end) side.
The template is custom. But switching to Cassiopeia does not alter the situation.
The template is custom. But switching to Cassiopeia does not alter the situation.
-
- Joomla! Intern
- Posts: 93
- Joined: Sun Jun 25, 2006 5:51 pm
Re: User login very slow
Deleted to remove smilies
Last edited by counterpoint on Sat Nov 23, 2024 8:51 am, edited 1 time in total.
-
- Joomla! Intern
- Posts: 93
- Joined: Sun Jun 25, 2006 5:51 pm
Re: User login very slow
Deleted to remove smilies
Last edited by counterpoint on Sat Nov 23, 2024 8:51 am, edited 1 time in total.
-
- Joomla! Intern
- Posts: 93
- Joined: Sun Jun 25, 2006 5:51 pm
Re: User login very slow
Forum Post Assistant (v1.6.7) : 23-Nov-2024 wrote:Basic Environment :: wrote:Joomla! Instance :: Joomla! 5.2.1-Stable (Uthabiti) 7-November-2024
Joomla! Configured :: Yes | Read-Only (444) |
Configuration Options :: Offline: false | SEF: true | SEF Suffix: false | SEF ReWrite: true | .htaccess/web.config: No (ReWrite Enabled but no .htaccess?) | GZip: false | Cache: false | CacheTime: 15 | CacheHandler: file | CachePlatformPrefix: false | FTP Layer: false | Proxy: false | LiveSite: Is Not Empty | Session lifetime: 60 | Session handler: database | Shared sessions: false | SSL: 0 | Error Reporting: default | Site Debug: false | Language Debug: false | Default Access: Public | Unicode Slugs: false | dbConnection Type: mysqli | PHP Supports J! 5.2.1: Yes | Database Supports J! 5.2.1: Yes | Database Credentials Present: Yes |
Host Configuration :: OS: Linux | OS Version: 6.1.0-18-amd64 | Technology: x86_64 | Web Server: Apache/2.4.62 | Encoding: gzip, deflate, br, zstd | System TMP Writable: Yes | Free Disk Space : 18.80 GiB |
PHP Configuration :: Version: 8.2.24 | PHP API: fpm-fcgi | Session Path Writable: Yes | Display Errors: 0 | Error Reporting: 22527 | Log Errors To: | Last Known Error: | Register Globals: | Magic Quotes: | Safe Mode: | Allow url fopen: 1 | Open Base: | Uploads: 1 | Max. Upload Size: 24M | Max. POST Size: 28M | Max. Input Time: 60 | Max. Execution Time: 300 | Memory Limit: 512M
Database Configuration :: Version: 10.11.6-MariaDB-0+deb12u1-log (Client:mysqlnd 8.2.24) | Database Size: 2757.45 MiB | #of Tables with config prefix: 207 | #of other Tables: 8 | User Privileges : GRANT ALLDetailed Environment :: wrote:PHP Extensions :: Core (8.2.24) | date (8.2.24) | libxml (8.2.24) | openssl (8.2.24) | pcre (8.2.24) | zlib (8.2.24) | filter (8.2.24) | hash (8.2.24) | json (8.2.24) | random (8.2.24) | Reflection (8.2.24) | SPL (8.2.24) | session (8.2.24) | standard (8.2.24) | sodium (8.2.24) | cgi-fcgi (8.2.24) | mysqlnd (mysqlnd 8.2.24) | PDO (8.2.24) | xml (8.2.24) | bcmath (8.2.24) | calendar (8.2.24) | ctype (8.2.24) | curl (8.2.24) | dom (20031129) | mbstring (8.2.24) | FFI (8.2.24) | fileinfo (8.2.24) | ftp (8.2.24) | gd (8.2.24) | gettext (8.2.24) | iconv (8.2.24) | intl (8.2.24) | exif (8.2.24) | mysqli (8.2.24) | pdo_mysql (8.2.24) | Phar (8.2.24) | posix (8.2.24) | readline (8.2.24) | shmop (8.2.24) | SimpleXML (8.2.24) | soap (8.2.24) | sockets (8.2.24) | sysvmsg (8.2.24) | sysvsem (8.2.24) | sysvshm (8.2.24) | tokenizer (8.2.24) | xmlreader (8.2.24) | xmlrpc (1.0.0RC3) | xmlwriter (8.2.24) | xsl (8.2.24) | zip (1.21.1) | Zend OPcache (8.2.24) | Zend Engine (4.2.24) |
Potential Missing Extensions ::
Switch User Environment :: PHP CGI: Yes | Server SU: Yes | PHP SU: Yes | Potential Ownership Issues: NoFolder Permissions :: wrote:Core Folders :: images/ (755) | components/ (755) | modules/ (755) | plugins/ (755) | language/ (755) | templates/ (755) | cache/ (755) | logs/ (---) | tmp/ (755) | administrator/components/ (755) | administrator/modules/ (755) | administrator/language/ (755) | administrator/templates/ (755) | administrator/logs/ (755) | api/ (755) |
Elevated Permissions (First 10) :: images/repository/ (775) |Database Information :: wrote:Database statistics :: Uptime: 10825225 | Threads: 11 | Questions: 707226459 | Slow queries: 1014 | Opens: 33531 | Open tables: 9658 | Queries per second avg: 65.331 |Extensions Discovered :: wrote:Components :: Site ::
Core ::
3rd Party:: os_authnet (4.1.0) ? | os_stripe (2.26.3) ? | os_paypal (4.1.0) ? | os_eway (4.1.0) ? | os_offline (4.1.0) ? | Profile Uploads (4.0) 1 | Remository multi-purpose module (4.0.0) 1 | Remository Total Downloads (3.96) 1 | Remository Tree (4.00) 1 | Remository Containers (3.97) 1 | Remository Update Server (3.99) 1 | Remository AuthorList (4.0) 1 | Remository language check (4.0.0) ? | plg_emailalerts_remository (1.0.0) ? | User-Remository (4.0.0) 1 | Quickdown (3.99.0) 0 | Remository Search (3.99.0) ? | plg_finder_remository (3.99) ? | Remository Audio (3.96) ? | CB REMOSITORY (1.0.2) ? | Remository Video (3.95.2) ? | Extension-Remository (3.99.0) 1 |
Components :: Admin ::
Core :: com_plugins (4.0.0) 1 | com_messages (4.0.0) 1 | com_content (4.0.0) 1 | com_templates (4.0.0) 1 | com_guidedtours (4.3.0) 1 | com_redirect (4.0.0) 1 | com_associations (4.0.0) 1 | com_cache (4.0.0) 1 | com_privacy (3.9.0) 1 | com_categories (4.0.0) 1 | com_languages (4.0.0) 1 | com_joomlaupdate (4.0.3) 1 | com_newsfeeds (4.0.0) 1 | com_mails (4.0.0) 1 | com_actionlogs (3.9.0) 1 | com_admin (4.0.0) 1 | com_installer (4.0.0) 1 | com_config (4.0.0) 1 | com_fields (4.0.0) 1 | com_postinstall (4.0.0) 1 | com_menus (4.0.0) 1 | com_contenthistory (4.0.0) 1 | com_users (4.0.0) 1 | com_checkin (4.0.0) 1 | com_tags (4.0.0) 1 | com_media (3.0.0) 1 | com_modules (4.0.0) 1 | com_cpanel (4.0.0) 1 | com_ajax (4.0.0) 1 | com_wrapper (4.0.0) 1 | com_workflow (4.0.0) 1 | com_finder (4.0.0) 1 | com_login (4.0.0) 1 | com_banners (4.0.0) 1 | com_scheduler (4.1.0) 1 |
3rd Party:: JMP Delete My Account (1.0.0) 1 | com_joomdle (2.3.1) 1 | com_joomdle (2.1.0) 1 | com_remsearch (2.3) 1 | COM_FAILEDLOGINATTEMPTS (2.5.8) 1 | com_osmembership (4.1.0) 1 | COM_BLANK (1.0.5) 1 | LADkit (3.03) 1 | Helpdesk Pro (6.0.0) 1 | COM_ALFCONTACT (3.4.1) ? | Remository (4.2.12) 1 | FlexiContact (16.00) 1 | Plotalot (8.00) 1 | Eyesite (8.03) 1 |
Modules :: Site ::
Core :: mod_stats (3.0.0) 1 | mod_users_latest (3.0.0) 1 | mod_related_items (3.0.0) 1 | mod_random_image (3.0.0) 1 | mod_articles_news (3.0.0) 1 | mod_banners (3.0.0) 1 | mod_footer (3.0.0) 1 | mod_articles_archive (3.0.0) 1 | mod_tags_popular (3.1.0) 1 | MOD_ARTICLES (5.2.0) 1 | mod_menu (3.0.0) 1 | mod_login (3.0.0) 1 | mod_articles_popular (3.0.0) 1 | mod_articles_category (3.0.0) 1 | mod_tags_similar (3.1.0) 1 | mod_custom (3.0.0) 1 | mod_languages (3.5.0) 1 | mod_finder (3.0.0) 1 | mod_feed (3.0.0) 1 | mod_whosonline (3.0.0) 1 | mod_breadcrumbs (3.0.0) 1 | mod_syndicate (3.0.0) 1 | mod_articles_categories (3.0.0) 1 | mod_wrapper (3.0.0) 1 | mod_articles_latest (3.0.0) 1 |
3rd Party:: My Favourites (4.0) 1 | Remository My Downloads (4.00) 1 | Joomdle courses (1.2.0) 1 | Remository multi-purpose module (4.0.0) 1 | mod_remsearch (3.2.0) 1 | Membership Status (4.1.0) 1 | Membership Plans (4.1.0) 1 | Remository Total Downloads (3.96) 1 | Public Profile (1.0.0) 1 | Remository Tree (4.00) 1 | Remository Containers (3.97) 1 | Remository Update Server (3.99) 1 | My Uploads (4.0) 1 | My Updates (4.00) 1 | IceMegaMenu Module (3.0.1) 1 | Membership Pro View (2.26.3) 1 | Remository My Feedback (1.0) 1 | Remository AuthorList (4.0) 1 | Carousel Banner (3.1.2) 1 | Profile Uploads (1.0) 1 | Joomdle My Courses (1.2.0) 1 | Membership Pro View (4.1.0) 1 | RepNews (4.1) 1 | JMP Login As User (1.0.0) 1 | Display diagnostics (1.0) 1 | XLC Activation Code (1.0) 1 |
Modules :: Admin ::
Core :: mod_messages (4.0.0) 1 | mod_privacy_status (4.0.0) 1 | mod_user (4.0.0) 1 | mod_latestactions (3.9.0) 1 | mod_version (3.0.0) 1 | mod_logged (3.0.0) 1 | mod_sampledata (3.8.0) 1 | mod_loginsupport (4.0.0) 1 | mod_menu (3.0.0) 1 | mod_privacy_dashboard (3.9.0) 1 | mod_login (3.0.0) 1 | mod_post_installation_messages (4.0.0) 1 | mod_submenu (3.0.0) 1 | mod_title (3.0.0) 1 | mod_quickicon (3.0.0) 1 | mod_guidedtours (4.3.0) 1 | mod_custom (3.0.0) 1 | mod_frontend (4.0.0) 1 | mod_multilangstatus (3.0.0) 1 | mod_feed (3.0.0) 1 | mod_latest (3.0.0) 1 | mod_popular (3.0.0) 1 | mod_stats_admin (3.0.0) 1 | mod_toolbar (3.0.0) 1 |
3rd Party:: Membership Pro - Latest Subscriptio (4.1.0) ? | Display diagnostics (1.0) 1 |
Libraries ::
Core ::
3rd Party:: file_fof40 (4.0.8) ? | Library - compojoom (5.2.3) 1 | FOF30 (3.3.4) ? | system-bsrlibrary (2.0.0) ? |
Templates Discovered :: wrote:Templates :: Site :: excelcalcs (1.0) 1 | cassiopeia (1.0) 1 | excelcalcs (1.0) 1 |
Templates :: Admin :: atum (1.0) 1 |
-
- Joomla! Intern
- Posts: 93
- Joined: Sun Jun 25, 2006 5:51 pm
Re: User login very slow
Forum Post Assistant (v1.6.7) : 23-Nov-2024 wrote:Basic Environment :: wrote:Joomla! Instance :: Joomla! 5.2.1-Stable (Uthabiti) 7-November-2024
Joomla! Configured :: Yes | Read-Only (444) |
Configuration Options :: Offline: false | SEF: true | SEF Suffix: false | SEF ReWrite: true | .htaccess/web.config: No (ReWrite Enabled but no .htaccess?) | GZip: false | Cache: false | CacheTime: 15 | CacheHandler: file | CachePlatformPrefix: false | FTP Layer: false | Proxy: false | LiveSite: Is Not Empty | Session lifetime: 60 | Session handler: database | Shared sessions: false | SSL: 0 | Error Reporting: default | Site Debug: false | Language Debug: false | Default Access: Public | Unicode Slugs: false | dbConnection Type: mysqli | PHP Supports J! 5.2.1: Yes | Database Supports J! 5.2.1: Yes | Database Credentials Present: Yes |
Host Configuration :: OS: Linux | OS Version: 6.1.0-18-amd64 | Technology: x86_64 | Web Server: Apache/2.4.62 | Encoding: gzip, deflate, br, zstd | System TMP Writable: Yes | Free Disk Space : 18.80 GiB |
PHP Configuration :: Version: 8.2.24 | PHP API: fpm-fcgi | Session Path Writable: Yes | Display Errors: 0 | Error Reporting: 22527 | Log Errors To: | Last Known Error: | Register Globals: | Magic Quotes: | Safe Mode: | Allow url fopen: 1 | Open Base: | Uploads: 1 | Max. Upload Size: 24M | Max. POST Size: 28M | Max. Input Time: 60 | Max. Execution Time: 300 | Memory Limit: 512M
Database Configuration :: Version: 10.11.6-MariaDB-0+deb12u1-log (Client:mysqlnd 8.2.24) | Database Size: 2757.45 MiB | #of Tables with config prefix: 207 | #of other Tables: 8 | User Privileges : GRANT ALLDetailed Environment :: wrote:PHP Extensions :: Core (8.2.24) | date (8.2.24) | libxml (8.2.24) | openssl (8.2.24) | pcre (8.2.24) | zlib (8.2.24) | filter (8.2.24) | hash (8.2.24) | json (8.2.24) | random (8.2.24) | Reflection (8.2.24) | SPL (8.2.24) | session (8.2.24) | standard (8.2.24) | sodium (8.2.24) | cgi-fcgi (8.2.24) | mysqlnd (mysqlnd 8.2.24) | PDO (8.2.24) | xml (8.2.24) | bcmath (8.2.24) | calendar (8.2.24) | ctype (8.2.24) | curl (8.2.24) | dom (20031129) | mbstring (8.2.24) | FFI (8.2.24) | fileinfo (8.2.24) | ftp (8.2.24) | gd (8.2.24) | gettext (8.2.24) | iconv (8.2.24) | intl (8.2.24) | exif (8.2.24) | mysqli (8.2.24) | pdo_mysql (8.2.24) | Phar (8.2.24) | posix (8.2.24) | readline (8.2.24) | shmop (8.2.24) | SimpleXML (8.2.24) | soap (8.2.24) | sockets (8.2.24) | sysvmsg (8.2.24) | sysvsem (8.2.24) | sysvshm (8.2.24) | tokenizer (8.2.24) | xmlreader (8.2.24) | xmlrpc (1.0.0RC3) | xmlwriter (8.2.24) | xsl (8.2.24) | zip (1.21.1) | Zend OPcache (8.2.24) | Zend Engine (4.2.24) |
Potential Missing Extensions ::
Switch User Environment :: PHP CGI: Yes | Server SU: Yes | PHP SU: Yes | Potential Ownership Issues: NoFolder Permissions :: wrote:Core Folders :: images/ (755) | components/ (755) | modules/ (755) | plugins/ (755) | language/ (755) | templates/ (755) | cache/ (755) | logs/ (---) | tmp/ (755) | administrator/components/ (755) | administrator/modules/ (755) | administrator/language/ (755) | administrator/templates/ (755) | administrator/logs/ (755) | api/ (755) |Extensions Discovered :: wrote:
Plugins ::
3rd Party:: Restful-Installer (1.0.0) 1 | Action Log - Membership Pro (4.1.0) 0 | Installer - Membership Pro (4.1.0) 1 | PLG_INSTALLER_FAILEDLOGINATTEMPTS (2.5.8) 1 | Installer - Helpdesk Pro (6.0.0) 1 | Search - Joomdle Course Topics (1.0) 1 | plg_search_categories (3.1.0) 0 | plg_search_content (3.1.0) 1 | plg_search_contacts (3.1.0) 0 | Search - Joomdle Courses (1.0) 1 | plg_search_tags (3.1.0) 0 | PLG_SEARCH_REMOSITORY (3.99.0) 1 | plg_search_newsfeeds (3.1.0) 0 | Search - Joomdle Course Categories (1.0) 1 | HTML purifier for Joomla (1.3) 1 | Content - Membership Plans (4.1.0) 0 | Content - Membership Tags (4.1.0) 0 | Content - Open Source Design Conten (3.1.0) ? | Content - Membership Restriction (4.1.0) 0 | content-selectbygroup (1.0.0) 1 | Quickdown (3.99.0) 0 | Content - Helpdesk Pro (6.0.0) 0 | PLG_CONTENT_[youtube] (4.0.5) 1 | Content - Membership Pro Subscripti (4.1.0) ? | Content - Membership Pro Content Re (4.1.0) ? | Content - Plotalot (7.01) 1 | CB Avatar for Community Builder (3.0) 0 | content-selectbygroup (1.0.0) 1 | Membership Pro SMS - Textlocal (4.1.0) 0 | Membership Pro SMS - Clickatell (4.1.0) 0 | Membership Pro SMS - Clockwork (4.1.0) 0 | System - Membership Schedule Conten (4.1.0) ? | System - Membership Pro Trigger Act (4.1.0) ? | System - Membership Schedule SPPage (4.1.0) ? | System - Helpdeskpro Reply Via Emai (5.1.2) ? | system-restful (1.1.0) 1 | System - Helpdeskpro Auto Close Tic (6.0.0) ? | System - Membership Pro (4.1.0) 1 | System - Membership Pro SP Page Bui (4.1.0) ? | System - Membership Schedule K2 Ite (4.1.0) ? | plg_system_cleantalkantispam_name (3.2.5) 1 | System - Membership Pro Articles Re (4.1.0) ? | System - Membership Pro SMS (4.1.0) 0 | System - Joomdlesession (1.0) 1 | System - Membership Pro Offline Rec (4.1.0) ? | PLG_SYS_SCRIPTSDOWN (3.0.8) 0 | System - Membership Pro K2 items Re (4.1.0) ? | PLG_SYSTEM_FAILEDLOGINATTEMPTS (2.5.8) 1 | System - Membership Pro Registratio (4.1.0) ? | IceMegaMenu Plugin (3.0.0) 0 | System - Eyesite Scanner (7.01) 1 | system-diagnostic (1.1) 1 | plg_system_email (2.4.2) 0 | plg_system_email (2.3.1) 0 | System - Helpdesk Pro Ticket From C (5.4.1) ? | System - Membership Pro Update Subs (4.1.0) ? | PLG_SYSTEM_WEB357FRAMEWORK (1.9.5) 1 | System - Membership Pro Cleaner (4.1.0) 0 | System - Membership Pro URLs Restri (4.1.0) ? | System - Joomdle License (1.0.0) 1 | PLG_SYSTEM_HTTP2PUSH (1.2.2) 0 | System - Membership Schedule Docume (4.1.0) ? | plg_system_tweakurl (1.0.0) 0 | System - Clicky Tracking Code (1.5) 1 | System - Incomplete Payment Subscri (4.5.1) ? | AcyMailing: override Joomla mailing (5.10.14) ? | plg_system_osmylicensesmanager (2.0.17) 1 | System - Membership Pro Clean Email (4.1.0) ? | System - Membership Pro Reminder (4.1.0) 1 | Smart Search - Membership Pro (-) 0 | Extension-Remository (3.99.0) 1 | Helpdesk Pro - Ticket Attachments (6.0.0) 0 | Helpdesk Pro - Ticket History (6.0.0) 0 | Helpdesk Pro - Pre-reply messages (6.0.0) 0 | Helpdesk Pro - Assign Ticket (6.0.0) 0 | plg_editors_codemirror (6.0.0) 1 | plg_editors_tinymce (6.8.4) 1 | PLG_AJAX_WEB357FRAMEWORK (1.9.5) 1 | plg_task_mphousekeeping (4.0.1) 0 | plg_task_mpofflinepaymentreminder (4.0.1) 0 | Membership Pro - Mailchimp (4.1.0) 0 | Membership Pro - Virtuemart Shopper (4.1.0) ? | Membership Pro - Helpdesk Pro Ticke (4.1.0) ? | Membership Pro - AcyMailing (4.1.0) 0 | Membership Pro - Easysocial (4.1.0) 0 | Membership Pro - Joomdle plugin (1.3.1) 1 | Membership Pro - Easy Profile (4.1.0) 0 | Membership Pro - Subscription Contr (4.1.0) ? | Membership Pro - PHP Script (4.1.0) 1 | Membership Pro - HTTP (4.1.0) 0 | Membership Pro - Group Membership P (4.1.0) ? | Membership Pro - Events Booking Reg (4.1.0) ? | Membership Pro - Joomla Groups (4.1.0) 1 | Membership Pro - Limit Subscription (4.1.0) ? | Membership Pro - Fields Assignment (4.1.0) 0 | Membership Pro - Acymailing 5 (2.25.1) 0 | Membership Pro - K2 Groups (4.1.0) 0 | Membership Pro - Documents (4.1.0) 0 | Membership Pro - Userprofile (4.1.0) 0 | Membership Pro - Delete User Accoun (4.1.0) ? | Membership Pro - CB (4.1.0) 0 | Membership Pro - User Files (4.1.0) 0 | Membership Pro - Joomsocial (4.1.0) 0 | Membership Pro - Auto Subscribe (4.1.0) 0 | Membership Pro - ActiveCampaign (4.1.0) 0 | MagicAuthentication - Magic (1.1) 0 | PLG_AUTHENTICATION_FAILEDLOGINATTEM (2.5.8) ? | plg_authentication_email (2.4.2) 0 | plg_authentication_email (2.3.1) 0 | plg_authentication_exceluser (1.0.0) 1 | Joomdleprofile - Joomdle Membership (1.1.1) ? | Check User email addresses with sim (1.0) ? | User hooks - Joomdle (1.0) 1 | PLG_USER_FAILEDLOGINATTEMPTS (2.5.8) 1 | User - Membership Pro (4.1.0) 0 | User-Remository (4.0.0) 1 | PLG_USER_RESTRICTUSERNAME_NAME (2.3.0) 1 |Templates Discovered :: wrote:Templates :: Site :: excelcalcs (1.0) 1 | excelcalcs (1.0) 1 |
Templates :: Admin ::
- AMurray
- Joomla! Master
- Posts: 10488
- Joined: Sat Feb 13, 2010 7:35 am
- Location: Australia
Re: User login very slow
you have some elevated permissions that should be changed to 755 (the one shown as 775).
Also "live site' should be empty - should not contain any value.
You have a third party extension "Login as user" try disabling that then try logging in again.? You said you didn't have any other "login" extensions earlier.
Does Membership Pro perhaps have its own login module?
Suggestion: set up a second test site, plain default install. Does the login take as long as you have indicated on your actual site?
Also "live site' should be empty - should not contain any value.
You have a third party extension "Login as user" try disabling that then try logging in again.? You said you didn't have any other "login" extensions earlier.
Does Membership Pro perhaps have its own login module?
Suggestion: set up a second test site, plain default install. Does the login take as long as you have indicated on your actual site?
Regards - A Murray
Global Support Moderator
Global Support Moderator
- Per Yngve Berg
- Joomla! Master
- Posts: 31568
- Joined: Mon Oct 27, 2008 9:27 pm
- Location: Romerike, Norway
Re: User login very slow
In addition to what is already mentioned, change Session Handler from Database to Filesystem.
- ceford
- Joomla! Hero
- Posts: 2979
- Joined: Mon Feb 24, 2014 10:38 pm
- Location: Edinburgh, Scotland
- Contact:
Re: User login very slow
These values are a bit low: Max. Upload Size: 24M | Max. POST Size: 28M - I suggest you change them to 64M.
My guess is that one of your plugins is doing something. Search your plugins for onUserLogin if you can. That is easy on a local installation, not so easy on a live site. If you can identify suspect plugins you could try disabling them and see what happens.
My guess is that one of your plugins is doing something. Search your plugins for onUserLogin if you can. That is easy on a local installation, not so easy on a live site. If you can identify suspect plugins you could try disabling them and see what happens.
-
- Joomla! Intern
- Posts: 93
- Joined: Sun Jun 25, 2006 5:51 pm
Re: User login very slow
Thanks for the comments.
The 775 permission doesn't make any difference since the owner of the directory is the only member of the group.
The live_site ABSOLUTELY SHOULD NOT BE EMPTY. I have raised this before, and never got any response. Joomla DOES NOT WORK without live_site being specified if the environment is PHP-FPM.
"Login as user" is not a login module in the general sense. The login module for normal login was the standard Joomla version, which is what I stated. I had tested disabling "login as user", and that made no difference.
Why is it preferable to use filesystem session handler? I have found it problematic in the past.
I have now found the cause of the problem. The size of the #__sessions table was huge. Why does Joomla not deal with this? Or at least give a warning if it is very large? I guess switching to filesystem would have fixed the problem (I actually used the Joomla prune utility and added it to cron jobs). But past bad experiences discouraged me from doing that.
The 775 permission doesn't make any difference since the owner of the directory is the only member of the group.
The live_site ABSOLUTELY SHOULD NOT BE EMPTY. I have raised this before, and never got any response. Joomla DOES NOT WORK without live_site being specified if the environment is PHP-FPM.
"Login as user" is not a login module in the general sense. The login module for normal login was the standard Joomla version, which is what I stated. I had tested disabling "login as user", and that made no difference.
Why is it preferable to use filesystem session handler? I have found it problematic in the past.
I have now found the cause of the problem. The size of the #__sessions table was huge. Why does Joomla not deal with this? Or at least give a warning if it is very large? I guess switching to filesystem would have fixed the problem (I actually used the Joomla prune utility and added it to cron jobs). But past bad experiences discouraged me from doing that.
- ceford
- Joomla! Hero
- Posts: 2979
- Joined: Mon Feb 24, 2014 10:38 pm
- Location: Edinburgh, Scotland
- Contact:
Re: User login very slow
Have a look at the source of your page. Anything you put in live_site is prefixed to resource links such as css, js and img links. If you use the url of your site you get away with it, you just convert relative urls to absolute urls. If you use the url of a related site you may get away with it - the resources are just fetched from a similar site, mostly. It would be interesting to know what you have in your $live_site variable!counterpoint wrote: ↑Mon Nov 25, 2024 2:10 pm The live_site ABSOLUTELY SHOULD NOT BE EMPTY. I have raised this before, and never got any response. Joomla DOES NOT WORK without live_site being specified if the environment is PHP-FPM.
-
- Joomla! Explorer
- Posts: 440
- Joined: Thu Jun 10, 2010 12:38 pm
Re: User login very slow
There were plenty of responses to your posting a few weeks ago: viewtopic.php?f=706&t=1005143&p=3705958 ... e#p3705958counterpoint wrote: ↑Mon Nov 25, 2024 2:10 pm Thanks for the comments.
The live_site ABSOLUTELY SHOULD NOT BE EMPTY. I have raised this before, and never got any response. Joomla DOES NOT WORK without live_site being specified if the environment is PHP-FPM.
- AMurray
- Joomla! Master
- Posts: 10488
- Joined: Sat Feb 13, 2010 7:35 am
- Location: Australia
Re: User login very slow
I'm no techy/coder but many on the forum in the past have said use "file" instead of "database". The one drawback of using database is as you found; the session table can get quick big, very quickly.
I think the "left behind" sessions can be caused by, for one reason, the end-user closing their browser before actually logging off (and many other reasons).
Emptying the session table on a regular basis is the best way, e.g. with a scheduled CRON job or doing so manually. Of course, that will auto-log out everyone since you have no control over who you log out.
Login-as-user is a plugin that allows an administrator/super user to effectively log in as any other user. I forgot what it was for.
You could suggest an improvement (on Github) e.g. to warn about the session table size (?). Maybe it just needs to be a small addition or a admin module you can add to the dashboard that simply says "session table (approx size): XYZ KB/MB"
I think the "left behind" sessions can be caused by, for one reason, the end-user closing their browser before actually logging off (and many other reasons).
Emptying the session table on a regular basis is the best way, e.g. with a scheduled CRON job or doing so manually. Of course, that will auto-log out everyone since you have no control over who you log out.
Login-as-user is a plugin that allows an administrator/super user to effectively log in as any other user. I forgot what it was for.
You could suggest an improvement (on Github) e.g. to warn about the session table size (?). Maybe it just needs to be a small addition or a admin module you can add to the dashboard that simply says "session table (approx size): XYZ KB/MB"
Regards - A Murray
Global Support Moderator
Global Support Moderator
- ceford
- Joomla! Hero
- Posts: 2979
- Joined: Mon Feb 24, 2014 10:38 pm
- Location: Edinburgh, Scotland
- Contact:
Re: User login very slow
The session table is processed regularly. I just looked at one of mine - it holds about 1000 entries for the last 10 hours or so. I think garbage collection is called during login and I guess during other processes too.
-
- Joomla! Intern
- Posts: 93
- Joined: Sun Jun 25, 2006 5:51 pm
Re: User login very slow
The problem I had was that there were millions of entries in the session table. Garbage collection appears to be ineffective. I have now added a call to the Joomla gc routine from a cron job.
The content of live site is simply the URL, including the https scheme. The thread referred to above did not yield any responses that dealt with the real issue. I have followed through the Joomla code, and also inspected the PHP variables that are set by the server. It is a simple fact that the Joomla logic WILL NOT WORK given the variables that are set by PHP-FPM. I really wish people would accept this fact and stop claiming that there should never be anything in the configuration file for live_site.
The content of live site is simply the URL, including the https scheme. The thread referred to above did not yield any responses that dealt with the real issue. I have followed through the Joomla code, and also inspected the PHP variables that are set by the server. It is a simple fact that the Joomla logic WILL NOT WORK given the variables that are set by PHP-FPM. I really wish people would accept this fact and stop claiming that there should never be anything in the configuration file for live_site.
-
- Joomla! Explorer
- Posts: 440
- Joined: Thu Jun 10, 2010 12:38 pm
Re: User login very slow
The thread referred to (as do others) made mention of a misconfigured server environment. That, and the gyrations you seem to be going through support the idea that something isn’t right with your server.
-
- Joomla! Intern
- Posts: 93
- Joined: Sun Jun 25, 2006 5:51 pm
Re: User login very slow
@gsmela I'm not going through any "gyrations". If you think the requirement for a value for live_site is caused by a misconfigured server, then please state in what respect you think it is misconfigured? Using PHP-FPM is not misconfiguration. Have you done a test using PHP-FPM? Have you read through the Joomla code? I have done that, and set up test systems, and implemented all the things that people claimed would affect the result - none did. It is absurd for people to talk about "misconfigured servers" when there is no specification for a "correctly" configured server.
The problem is that Joomla tries to find the path to the site (in effect the subdirectory, if any). It uses the PHP globals $_SERVER['PHP_SELF'] and $_SERVER['SCRIPT_NAME']. But with PHP-FPM, a reference to e.g. https://example.com/up-users/Users has both those globals set to "/up-users/Users". Joomla removes one directory level and sets the path to "/up-users".
But this is incorrect. The site is not in a subdirectory at all (neither up-users nor anything else) and the path should be empty. Because Joomla has decided there is a path, all links have "/up-users" inserted into them. They are then invalid, resulting in 404 errors.
I actually specified this problem precisely on joomla.stackexchange.com but presumably because it went unanswered, the post has been hidden. It read as follows:
I've spent a good few hours ploughing through code and setting up servers to test exactly what is goes on to cause Joomla to fail in PHP-FPM unless $live_site is correctly set.
The problem turns out to be that when $live_site is empty, Joomla will in most cases rely on the value of the PHP super global $_SERVER['SCRIPT_NAME']. In the case of a site that is installed into the document root, this will be empty when PHP is running as an Apache module, even when the URL is something like https://example.com/heading/article. (Because the actual script is the index.php in the document root).
However, if PHP is running as PHP-FPM (which is a favoured solution for high performance and for site security) then the super global will contain "/heading/article" for the example above. With this value, Joomla does not work out how to handle the request and gives a 404 error.
This can obviously be fixed by hacking Joomla, but that isn't a good solution. Is there any way to make PHP-FPM behave in the same way as PHP as an Apache module? Unless a solution is available, my feeling is that Joomla should continue to support the use of $live_site and fix problems that occur when it is set (notably in Joomla upgrades).
The problem is that Joomla tries to find the path to the site (in effect the subdirectory, if any). It uses the PHP globals $_SERVER['PHP_SELF'] and $_SERVER['SCRIPT_NAME']. But with PHP-FPM, a reference to e.g. https://example.com/up-users/Users has both those globals set to "/up-users/Users". Joomla removes one directory level and sets the path to "/up-users".
But this is incorrect. The site is not in a subdirectory at all (neither up-users nor anything else) and the path should be empty. Because Joomla has decided there is a path, all links have "/up-users" inserted into them. They are then invalid, resulting in 404 errors.
I actually specified this problem precisely on joomla.stackexchange.com but presumably because it went unanswered, the post has been hidden. It read as follows:
I've spent a good few hours ploughing through code and setting up servers to test exactly what is goes on to cause Joomla to fail in PHP-FPM unless $live_site is correctly set.
The problem turns out to be that when $live_site is empty, Joomla will in most cases rely on the value of the PHP super global $_SERVER['SCRIPT_NAME']. In the case of a site that is installed into the document root, this will be empty when PHP is running as an Apache module, even when the URL is something like https://example.com/heading/article. (Because the actual script is the index.php in the document root).
However, if PHP is running as PHP-FPM (which is a favoured solution for high performance and for site security) then the super global will contain "/heading/article" for the example above. With this value, Joomla does not work out how to handle the request and gives a 404 error.
This can obviously be fixed by hacking Joomla, but that isn't a good solution. Is there any way to make PHP-FPM behave in the same way as PHP as an Apache module? Unless a solution is available, my feeling is that Joomla should continue to support the use of $live_site and fix problems that occur when it is set (notably in Joomla upgrades).
- ceford
- Joomla! Hero
- Posts: 2979
- Joined: Mon Feb 24, 2014 10:38 pm
- Location: Edinburgh, Scotland
- Contact:
Re: User login very slow
I have been trying to understand the problem a little more. One thing that I have learned is that my previous comments were not quite right, indicating that I do not fully understand $live_site myself! However:
If you have something in $live_site the block of code referencing PHP_SAPI is not executed. So that might indicate there is something amiss with your $_SERVER['PHP_SELF'] and/or $_SERVER['SCRIPT_NAME'] variables or that Joomla is using the wrong one. Could you tell us what is in those two variables and the value of PHP_SAPI? I realise you said both are set to the same value, but what happens in the cleanup line?
If you have something in $live_site the block of code referencing PHP_SAPI is not executed. So that might indicate there is something amiss with your $_SERVER['PHP_SELF'] and/or $_SERVER['SCRIPT_NAME'] variables or that Joomla is using the wrong one. Could you tell us what is in those two variables and the value of PHP_SAPI? I realise you said both are set to the same value, but what happens in the cleanup line?
-
- Joomla! Intern
- Posts: 93
- Joined: Sun Jun 25, 2006 5:51 pm
Re: User login very slow
Provided I place the appropriate value in live_site (the URL for the site, e.g. https://www.example.com) the site works correctly.
Without a value in live_site, the site does not work for the reasons stated above: "However, if PHP is running as PHP-FPM (which is a favoured solution for high performance and for site security) then the super global will contain "/heading/article" for the example above. With this value, Joomla does not work out how to handle the request and gives a 404 error". That applies to both PHP_SELF and SCRIPT_NAME. You can say that there is "something amiss" with them if you like, but that is the actual behaviour of PHP-FPM. It is not a configurable option.
It doesn't really matter what is in PHP_SAPI since in PHP-FPM the result comes out the same either way. The cleanup doesn't make any material difference.
I have actually been aware for many years that there has been no way to determine with certainty the base directory of a PHP web application (from within the application) that will work in every implementation of PHP. The information that is needed is not provided in a fully consistent way. It is frustrating that so many Joomla people refuse to recognise this.
Without a value in live_site, the site does not work for the reasons stated above: "However, if PHP is running as PHP-FPM (which is a favoured solution for high performance and for site security) then the super global will contain "/heading/article" for the example above. With this value, Joomla does not work out how to handle the request and gives a 404 error". That applies to both PHP_SELF and SCRIPT_NAME. You can say that there is "something amiss" with them if you like, but that is the actual behaviour of PHP-FPM. It is not a configurable option.
It doesn't really matter what is in PHP_SAPI since in PHP-FPM the result comes out the same either way. The cleanup doesn't make any material difference.
I have actually been aware for many years that there has been no way to determine with certainty the base directory of a PHP web application (from within the application) that will work in every implementation of PHP. The information that is needed is not provided in a fully consistent way. It is frustrating that so many Joomla people refuse to recognise this.
- Per Yngve Berg
- Joomla! Master
- Posts: 31568
- Joined: Mon Oct 27, 2008 9:27 pm
- Location: Romerike, Norway
Re: User login very slow
Your set-up for VHOST in Apache and PHP-FPM is faulty.
-
- Joomla! Intern
- Posts: 93
- Joined: Sun Jun 25, 2006 5:51 pm
Re: User login very slow
What is your reason for claiming that? Please be specific.
-
- Joomla! Intern
- Posts: 93
- Joined: Sun Jun 25, 2006 5:51 pm
Re: User login very slow
A typical vhost entry is:
What exactly are you saying is faulty?
Code: Select all
<VirtualHost *:443>
ServerName example.com
ServerAdmin [email protected]
DocumentRoot /var/www/example/public_html
<FilesMatch \.php$>
SetHandler "proxy:unix:/run/php/${php_version}-example.sock|fcgi://example"
</FilesMatch>
Include sites-available/example.inc
SSLCertificateFile /etc/certhelper/certs/example.com/fullchain.pem
SSLCertificateKeyFile /etc/certhelper/certs/example.com/privkey.pem
</VirtualHost>
- ceford
- Joomla! Hero
- Posts: 2979
- Joined: Mon Feb 24, 2014 10:38 pm
- Location: Edinburgh, Scotland
- Contact:
Re: User login very slow
Back to understanding: if $live_site is empty one or other of these statements is used:
in libraries/src/Uri/Uri.php lines 156 and 159. For me the $_SERVER['SCRIPT_NAME'] is used. It contains "/jdm4/index.php" which is the entry point to this particular test site in a subfolder (I have lots of test sites in different subfolders). For me $_SERVER['PHP_SELF'] contains the same script name. The /index.php part is removed to obtain the $path variable (/jdm4).
If $live_site is not empty then the $script_name is not used. The $base['prefix'] and $base['path'] are obtained from the live $site_value.
You previously said:
That is not so for me. I do have my test site in a subfolder and Joomla does return the correct script name (/jdm4/index.php). If I add a dud folder name such as localhost/jdm4/dudfolder then I get a 404 Page not found error, which is what I expect.
So it appears to me that your server is not putting the correct values in $_SERVER['SCRIPT_NAME'] and $_SERVER['PHP_SELF']. They should contain /index.php.
Code: Select all
$script_name = $_SERVER['PHP_SELF'];
$script_name = $_SERVER['SCRIPT_NAME'];
If $live_site is not empty then the $script_name is not used. The $base['prefix'] and $base['path'] are obtained from the live $site_value.
You previously said:
Code: Select all
. https://example.com/up-users/Users has both those globals set to "/up-users/Users". Joomla removes one directory level and sets the path to "/up-users".
So it appears to me that your server is not putting the correct values in $_SERVER['SCRIPT_NAME'] and $_SERVER['PHP_SELF']. They should contain /index.php.
-
- Joomla! Intern
- Posts: 93
- Joined: Sun Jun 25, 2006 5:51 pm
Re: User login very slow
@ceford Yes, I understand that some PHP implementations behave as you describe (I said so above). But there isn't only one way to run PHP, and PHP-FPM behaves differently. This is well known. But given the importance of PHP-FPM as an efficient implementation of PHP and its widespread use, it isn't really helpful to describe it as not putting "correct values" in globals. In fact the values in these globals have varied between different PHP implementations for many years, not just with PHP-FPM.
Why should PHP-FPM be supported? Please see articles such as https://bobcares.com/blog/php-fpm-advantages/
Why should PHP-FPM be supported? Please see articles such as https://bobcares.com/blog/php-fpm-advantages/
- ceford
- Joomla! Hero
- Posts: 2979
- Joined: Mon Feb 24, 2014 10:38 pm
- Location: Edinburgh, Scotland
- Contact:
Re: User login very slow
Surely $_SERVER['SCRIPT_NAME'] and $_SERVER['PHP_SELF'] are populated by the Apache server. So the problem you experience should have nothing to do with PHP-FPM. There are reports of an Apache related PHP-FPM problem from many years ago. Nothing recent that I can find.
-
- Joomla! Intern
- Posts: 93
- Joined: Sun Jun 25, 2006 5:51 pm
Re: User login very slow
Saying "populated by Apache" is too vague. Yes, they are set by Apache modules (much of Apache's functionality is in its large selection of modules). But PHP-FPM doesn't use the same Apache modules as default PHP. If you don't believe me, set up a server with PHP-FPM and see for yourself. Problems of this kind have, as I said, existed for many years. See https://bugs.php.net/bug.php?id=65641 for example. That bug claims to be fixed. But it is a different case from the situation where there is no .php file specified and mod_rewrite is relied on to find a PHP file. There are ways round it, but much the simplest and most reliable solution is to set live_site in Joomla. That is why this functionality should be maintained, and why it is misleading to say that live_site should always be empty.
- Per Yngve Berg
- Joomla! Master
- Posts: 31568
- Joined: Mon Oct 27, 2008 9:27 pm
- Location: Romerike, Norway
Re: User login very slow
Nginx is a better alternative to Apache. Better performance and does not have this problem.
PHP-FPM communicate with the Web Server with a Linux Socket or TCP Port. It can then run as a different Linux User than the www-data that Apache Handler run as.
PHP-FPM communicate with the Web Server with a Linux Socket or TCP Port. It can then run as a different Linux User than the www-data that Apache Handler run as.
Advertisement