CodeIgniter works on any virtual hosting service but IPOWER???

Question

I've been working on a case using Pyrocms, a CI-based CMS, on my local WAMP server for couple months. Recently, I'm starting to deploy on client's webhosting server of IPOWER (www.ipower.com).

The installation process stops after step one. And the error message is below.

ON CHROME

Error 101 (net::ERR_CONNECTION_RESET)

I've also tried on IE, Firefox, and they all stops on step one.

So, I've began a LONG investigation, I've found several CodeIgniter-based CMS can NOT work well on IPOWER. They all show the Error 101 in Chrome. That's why I start to wonder is there something wrong on the setting of IPOWER web hosting. Then I've check all the setting, including .htaccess / sessions / rewrite mod...etc, none of them have problem. I don't know if this is another ignorantly frustrating.

Would somebody help me? Or any possible suggestion will be much appreciated.

Answer 1

Have you set the cookie settings in the config.php file?

This one:

$config['cookie_domain'] = ".your-domain.com";

Answer 2

I'm curious, and thinking out loud here -- betting it's not on the dev side, actually more suited for ServerFault, being sort of a networking problem?

I say so not to discourage your question, but perhaps help you think outside of the usual suspects.

So this is a stab in the dark, but given that you're firing this off from a browser, I'd guess you could also do it with Wget?

I've run some HTTP requests that are coded properly and as a safeguard should exit after 1000 or so iterations, but for whatever reason they do not (even modifying the FF config for it).

However, running same HTTP request from Wget works like a champ.

From the Wikipedia entry on Wget:

Wget has been designed for robustness over slow or unstable network connections. If a download does not complete due to a network problem, Wget will automatically try to continue the download from where it left off, and repeat this until the whole file has been retrieved. It was one of the first clients to make use of the then-new Range HTTP header to support this feature.

What do you think? I don't offer this with conviction, but on a hunch. If I'm wrong, maybe it's a step outside the box, closer to the solution? Good luck fixing it! I'm eager to know what it is. :)

Answer 3

OK, I've found the answer. The problem is solved by enable the following setting in config.php. And you need to create a table to hold the sessions as well. I don't understand why this is so. But it totally solves my problem, so I just write down here and hope someone like me could get help by reading this.

$config['sess_use_database'] = TRUE;

$config['sess_table_name'] = 'ci_sessions';