Phplist Admin Internal Server Error
Contents |
Reminder: this page is to propose solutions to common problems. If you want to report a problem, please look in the forums first, or use the bug tracker. Do not report a problem here: your phplist 500 internal server error question will remain unanswered! Error messages Error: please make sure that
Phplist Installation Guide
index.php is your default document for a directory. If you have just installedphpListand get this message, make sure
Phplist Download
that the DirectoryIndex setting of your Apache configuration has somewhere index.php index.html, and check that index.php is mentioned before index.html. For other webservers please consult your manual to find
Could Not Instantiate Mail Function
how to make index.php the default document for a directory. Alternatively you can delete the file "index.html" in the lists directory of phpList. Error: IMAP is not included in your PHP installation, cannot continue. There is a major confusion that has been caused by the PHP developers naming a PHP module the IMAP module, even though it is used for more than just IMAP. phpList needs the IMAP functions in PHP in order to connect to the mailbox that will hold the bounces. The mailbox itself is a POP3 mailbox, or you can configure it to be a local mailbox files, but whatever the situation, the IMAP functions are necessary. IMAP functions in PHP have nothing to do with the actual IMAP protocol (at least not as far asphpListis concerned). You should be able to solve this issue by installing (and compiling) the IMAP module into PHP. If you are on a shared hosting account, you should contact your hosting provider. Fatal Error: Cannot connect to database, access denied. Please contact the administrator This error indicates there is something wrong with your database connection details. A Database connection requires four things, and they are very sensitive to errors (just one little typo and it won't work): 1) a database host (the name of the server, in many cases "localhost" works, but not always), 2) a database "user" the name of the user who
version roll out and QA » phpList, maintainer needed » UI lite phpList plugins » phpList API » rssmanager phpList.org My View | View Issues | Change Log | RoadmapView Issue Details[Jump to Notes] [Print] IDProjectCategoryView StatusDate SubmittedLast Update0009937phplistConfigurationpublic08-05-07 11:3704-06-13 22:26ReporterTki2000PrioritynormalSeverityminorReproducibilityalwaysStatusresolvedResolutionfixedPlatformOSOS VersionProduct Version2.10.3Target VersiondocumentationFixed in VersionSummary0009937: Internal Server Error (.htaccess file problems with Apache configurations)DescriptionThis issue will give you an "Internal Server Error" page. There are troubles with .htaccess files in phplist and Apache configurations if your Apache is not configured with "AllowOverride All" in httpd.conf file. Another configuration I found working is "AllowOverride Options AuthConfig Indexes Limit" but this is only possible if you have http://docs.phplist.com/PhplistTroubleshooting.html access to the Apache server config file and this is probably not possible. A quick FIX is to TAKE AWAY the .htaccess files in dirs "/lists" and "/admin" (and probably in any other dir where .htaccess may reside), but it will open some security related issues. If this is the case, try to use the .htaccess files to authenticate the users that may have access to files and not to https://mantis.phplist.org/view.php?id=9937 deny the files.TagsNo tags attached.Attached Files Relationships child of0010998newEnhance security Relationships Notes (0051609) michiel (manager) 23-05-12 14:23 bit of a catch 22. I'd rather not remove the .htaccess files, and open up the system, but yes, it's awkward that it causes the 500 errors. I guess this should be clearly documented with options what to do about it, and what impact that has. (0051618) raynau (reporter) 23-05-12 23:50 Solution is given in forum and is very simple and clear. 1°) Last line of the htaccess must be commented and becomes : #php_flag magic_quotes_gpc on 2°) You must create or do a php.ini with these two lines at the root (same place than the htaccess : php_flag magic_quotes_gpc=on magic_quotes_gpc=1 it works perfectly and the security is still on. (0051619) michiel (manager) 24-05-12 00:37 well, that may work in some cases, but it's possible the other directives in the file cause a 500 as well. (0051621) raynau (reporter) 24-05-12 00:49 This fits for Apache GCI which from what I have read are more protected. Most servers are set on that way now on the Continent and all big hosting-compagnies are using Apache CGI because it is more protected. So there is not to delete or change any htacess in o
whatever came with MySQL 5.5.4] Architecture x86_64 Operating System linux I installed phpList 3.2.4 (Release http://discuss.phplist.org/t/could-not-login-500-internal-server-error-phplist-3-2-4/1286 Date : 08 dec 2015) for the very first time using softaculous. I kept all the default options the same. I got a 500 internal server error when accessing my webpage /lists and /lists/admin index pages. So I have yet to actually log into phpList ever. I asked my web internal server host about this and they looked at some logs and they said: The issue appears to be with the script, since it's complaining about the missing module while it's actually installed (MySQLi): [Mon Dec 28 22:33:25 2015] [error] [client 216.123.4.567] malformed header from script. Bad header=Mysqli functionality missing: index.php[Mon Dec internal server error 28 22:33:25 2015] [error] [client 216.123.4.567] File does not exist: /home/public_html/500.shtml I can only advise you to try contacting the developer and let us know if they need any configuration updates from our end. Any suggestions on what modifications need to be done. I checked your manual documentation but it does not mention the 500 error. I thought the softaculous auto-detected and installed everything correctly. EDIT: the web host upgraded my server to php 5.5 and then it seems like now everything loads, no more 500 server error. So I have at least been able to login to the admin panel Since I already typed this maybe it will help someone. I'll probably just upgrade to php 5.6 to be a little more future-proof. [any harm in doing that?] Home Categories FAQ/Guidelines Terms of Service Privacy Policy Powered by Discourse, best viewed with JavaScript enabled back to phpList.org