it's been fixed itself. from "Peter Pitchford":
"Its fixed but I'm not sure what was causing the problem. Some one else deleted the robots file...
left click my forum name, there is "Start a Conversion" option, it's same as vBulletin's PM(private message).
the messages in the conversation...
so you're saying the home page is not correct while other pages are ok ?
it may relate to rewrite rules in .htaccess,
you can post it here or...
can you a screenshot ? not clear the issue you talked about.
if ( strlen( $name ) > $setting->nameWidth )
$name = substr( $name, 0, $setting->nameWidth - 3 )....
no experience with this addon.
but yes, litespeed also has "full guest caching" solution for vBulletin:...
just ignore it.
litespeed web server will start lsphp5 5.6.10 to run php script, don't need php 5.4.16 on the os at all.
updated the wiki page to include this thread:...
have you audit the memory lsphp5 process(which run "Rebuild Attachment Thumbnails" script) ?
it may consume more and more memory after long time...
the issue looks complicated and not easy to answer it.
and at least I've no experience for such issue:
it's fast in both front end and backend...
great to have it fixed !
however wonder why opcache has caused 503 for this case.
you may have enabled php suExec if it's a shared host.
is csf / lfd installed ? if so, please refer...
RewriteRule admin.php - [E=noabort:1, E=noconntimeout:1]
in .htaccess, see if works.
can you be more specific ?
if looking at
there are 2 cache options: LSCache / LiteMage,
checked the domain, it's currently running apache.
is litespeed installed on this server ?
#pmap -x pid-of-lsphp5
to get more info.
from man page of pmap:
EXTENDED AND DEVICE FORMAT FIELDS
Address: start address of map...
can check with
#pmap -p pid-of-lsphp5-process
I think it depends the php script.
to measure if lsphp5 itself has consumed many memory, can test...
check the .htaccess file
if wp-login.php is not allowed to access
can you run it at command line (i.e., manually)
#/usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.23
if still fail, may be a firewall issue between...
if you have many user accounts on the server, usually you need enable php suExec.
otherwise all accounts are running as nobody:nobody or...
Separate names with a comma.