+- CodeIgniter Forums (https://forum.codeigniter.com)
+-- Forum: Using CodeIgniter (https://forum.codeigniter.com/forumdisplay.php?fid=5)
+--- Forum: General Help (https://forum.codeigniter.com/forumdisplay.php?fid=24)
+--- Thread: my website - currently unable to handle this request (/showthread.php?tid=67836)
my website - currently unable to handle this request - cndunga - 04-16-2017
Recently something went wrong with my domain hosting and the ISP had to recreate my domain again. Once it was done I copied back my codeigniter website but since then I am getting the following error message - examprep.co.ke is currently unable to handle this request. HTTP ERROR 500.
Could someone assist me please.
RE: my website - currently unable to handle this request - Paradinight - 04-16-2017
(04-16-2017, 06:58 AM)cndunga Wrote: Recently something went wrong with my domain hosting and the ISP had to recreate my domain again. Once it was done I copied back my codeigniter website but since then I am getting the following error message - examprep.co.ke is currently unable to handle this request. HTTP ERROR 500.
Could someone assist me please.
check the error log
RE: my website - currently unable to handle this request - cndunga - 04-16-2017
(04-16-2017, 07:05 AM)Paradinight Wrote:Dear Paradinight,(04-16-2017, 06:58 AM)cndunga Wrote: Recently something went wrong with my domain hosting and the ISP had to recreate my domain again. Once it was done I copied back my codeigniter website but since then I am getting the following error message - examprep.co.ke is currently unable to handle this request. HTTP ERROR 500.
Could someone assist me please.
check the error log
Thanks for the quick response. Kindly guide me on how to check on the error log. I still learning .........
RE: my website - currently unable to handle this request - Paradinight - 04-16-2017
(04-16-2017, 07:31 AM)cndunga Wrote:(04-16-2017, 07:05 AM)Paradinight Wrote:Dear Paradinight,(04-16-2017, 06:58 AM)cndunga Wrote: Recently something went wrong with my domain hosting and the ISP had to recreate my domain again. Once it was done I copied back my codeigniter website but since then I am getting the following error message - examprep.co.ke is currently unable to handle this request. HTTP ERROR 500.
Could someone assist me please.
check the error log
Thanks for the quick response. Kindly guide me on how to check on the error log. I still learning .........
Do you have ssh?
RE: my website - currently unable to handle this request - cndunga - 04-16-2017
(04-16-2017, 08:27 AM)Paradinight Wrote:(04-16-2017, 07:31 AM)cndunga Wrote:(04-16-2017, 07:05 AM)Paradinight Wrote:Dear Paradinight,(04-16-2017, 06:58 AM)cndunga Wrote: Recently something went wrong with my domain hosting and the ISP had to recreate my domain again. Once it was done I copied back my codeigniter website but since then I am getting the following error message - examprep.co.ke is currently unable to handle this request. HTTP ERROR 500.
Could someone assist me please.
check the error log
Thanks for the quick response. Kindly guide me on how to check on the error log. I still learning .........
Do you have ssh?
No I do not have ssh
RE: my website - currently unable to handle this request - cndunga - 04-17-2017
Managed to generate the error log .
<?php if ( ! defined('BASEPATH')) exit('No direct script access allowed'); ?>
ERROR - 2017-04-17 04:40:40 --> 404 Page Not Found --> index
DEBUG - 2017-04-17 04:41:59 --> Config Class Initialized
DEBUG - 2017-04-17 04:41:59 --> Hooks Class Initialized
DEBUG - 2017-04-17 04:41:59 --> Utf8 Class Initialized
DEBUG - 2017-04-17 04:41:59 --> UTF-8 Support Enabled
DEBUG - 2017-04-17 04:41:59 --> URI Class Initialized
DEBUG - 2017-04-17 04:41:59 --> Router Class Initialized
DEBUG - 2017-04-17 04:41:59 --> No URI present. Default controller set.
DEBUG - 2017-04-17 04:41:59 --> Output Class Initialized
DEBUG - 2017-04-17 04:41:59 --> Security Class Initialized
DEBUG - 2017-04-17 04:41:59 --> Input Class Initialized
DEBUG - 2017-04-17 04:41:59 --> CRSF cookie Set
DEBUG - 2017-04-17 04:41:59 --> Global POST and COOKIE data sanitized
DEBUG - 2017-04-17 04:41:59 --> Language Class Initialized
DEBUG - 2017-04-17 04:41:59 --> Loader Class Initialized
DEBUG - 2017-04-17 04:41:59 --> Helper loaded: url_helper
DEBUG - 2017-04-17 04:41:59 --> Helper loaded: file_helper
DEBUG - 2017-04-17 04:41:59 --> Helper loaded: form_helper
DEBUG - 2017-04-17 04:41:59 --> Language file loaded: language/english/auth_lang.php
DEBUG - 2017-04-17 04:41:59 --> Language file loaded: language/english/ion_auth_lang.php
DEBUG - 2017-04-17 04:41:59 --> Database Driver Class Initialized
DEBUG - 2017-04-17 04:42:00 --> Config Class Initialized
DEBUG - 2017-04-17 04:42:00 --> Hooks Class Initialized
DEBUG - 2017-04-17 04:42:00 --> Utf8 Class Initialized
DEBUG - 2017-04-17 04:42:00 --> UTF-8 Support Enabled
DEBUG - 2017-04-17 04:42:00 --> URI Class Initialized
DEBUG - 2017-04-17 04:42:00 --> Router Class Initialized
DEBUG - 2017-04-17 04:42:00 --> No URI present. Default controller set.
DEBUG - 2017-04-17 04:42:00 --> Output Class Initialized
DEBUG - 2017-04-17 04:42:00 --> Security Class Initialized
DEBUG - 2017-04-17 04:42:00 --> Input Class Initialized
DEBUG - 2017-04-17 04:42:00 --> CRSF cookie Set
DEBUG - 2017-04-17 04:42:00 --> Global POST and COOKIE data sanitized
DEBUG - 2017-04-17 04:42:00 --> Language Class Initialized
DEBUG - 2017-04-17 04:42:00 --> Loader Class Initialized
DEBUG - 2017-04-17 04:42:00 --> Helper loaded: url_helper
DEBUG - 2017-04-17 04:42:00 --> Helper loaded: file_helper
DEBUG - 2017-04-17 04:42:00 --> Helper loaded: form_helper
DEBUG - 2017-04-17 04:42:00 --> Language file loaded: language/english/auth_lang.php
DEBUG - 2017-04-17 04:42:00 --> Language file loaded: language/english/ion_auth_lang.php
DEBUG - 2017-04-17 04:42:00 --> Database Driver Class Initialized
DEBUG - 2017-04-17 04:42:05 --> Config Class Initialized
DEBUG - 2017-04-17 04:42:05 --> Hooks Class Initialized
DEBUG - 2017-04-17 04:42:05 --> Utf8 Class Initialized
DEBUG - 2017-04-17 04:42:05 --> UTF-8 Support Enabled
DEBUG - 2017-04-17 04:42:05 --> URI Class Initialized
DEBUG - 2017-04-17 04:42:05 --> Router Class Initialized
DEBUG - 2017-04-17 04:42:05 --> No URI present. Default controller set.
DEBUG - 2017-04-17 04:42:05 --> Output Class Initialized
DEBUG - 2017-04-17 04:42:05 --> Security Class Initialized
DEBUG - 2017-04-17 04:42:05 --> Input Class Initialized
DEBUG - 2017-04-17 04:42:05 --> CRSF cookie Set
DEBUG - 2017-04-17 04:42:05 --> Global POST and COOKIE data sanitized
DEBUG - 2017-04-17 04:42:05 --> Language Class Initialized
DEBUG - 2017-04-17 04:42:05 --> Loader Class Initialized
DEBUG - 2017-04-17 04:42:05 --> Helper loaded: url_helper
DEBUG - 2017-04-17 04:42:05 --> Helper loaded: file_helper
DEBUG - 2017-04-17 04:42:05 --> Helper loaded: form_helper
DEBUG - 2017-04-17 04:42:05 --> Language file loaded: language/english/auth_lang.php
DEBUG - 2017-04-17 04:42:05 --> Language file loaded: language/english/ion_auth_lang.php
DEBUG - 2017-04-17 04:42:05 --> Database Driver Class Initialized
Can someone tell me where the problem is?
RE: my website - currently unable to handle this request - GGitzOle - 04-17-2017
Check your database credentials to make sure they're 100% correct.
Also,since your web host recreated the domain, check your config values are correct, particularly base_url. And then finally take a look at your .htaccess file to make sure it is correct.
RE: my website - currently unable to handle this request - InsiteFX - 04-17-2017
500 INTERNAL SERVER ERROR MESSAGE
OVERVIEW:
500 Internal Server Error is a generic error message, given when no more specific message is suitable.
There are a number of causes for a 500 Internal Server Error to display in a web browser.
CHECK THE ERROR LOGS!
With any error message, particularly one as broad as the 500 Internal Server Error,
you will first want to check any Apache and PHP error logs for your server.
These logs can provide valuable context related to any code failures or other potential
causes of a site failure.
ERROR WITH AN .HTACCESS FILE:
If you are using a .htaccess on your site, it may be interfering with the web page you
are trying to load into your browser. Please double check the .htaccess configuration.
Any syntax errors will cause a 500 Internal Server Error message to be displayed instead of your website.
To confirm whether a misconfiguration .htaccess is the cause of the 500 Internal Server error,
either remove or rename the .htaccess file temporarily and then try to reload the page.
PHP CODING TIMING OUT:
If your PHP script makes external network connections, the connections may time out.
If too many connections are attempted and time out, this will cause a "500 Internal Server Error."
To prevent these time outs and errors, you'll want to make sure that PHP scripts be coded with
some timeout rules. Typically, however, catching a timeout error when connecting to a database or
externally to remote resources (example: RSS feeds) are difficult. They, in effect, freeze the
script from continuing to run.
Removing any external connections can increase both the performance of your website and decrease
the chances of you receiving a "500 Internal Server Error."
SYNTAX OR CODING ERRORS IN YOUR CGI/PERL SCRIPT:
If it is a web page ending in .cgi or .pl that is producing the error, check your script for errors.
When editing your CGI script, use a plain text editor - a program that saves the file as a 'text file'
type. DO NOT use Wordpad that comes with Microsoft Windows because it doesn't save files in pure ASCII
text format. Use Notepad instead to edit files.
Upload your CGI scripts in ASCII mode into the cgi-bin directory.
Set the file permissions on the CGI script file and directories to be chmod 755. If you use an FTP program
to transfer files, right-click on the file and select change file attributes. See Using FTP and SFTP.
Double-check that the Perl modules you require for your script is supported.