By marknt15 on

Hi,

I transferred my project to Windows 7 64 Bit using WAMP. My drupal version is 5. The problem is, when I load the page then firefox keeps showing the 'The connection was reset'. I already increased my memory_limit to 2048 in my php.ini but it still shows the same error.

If I created a new install of drupal 5 then it will work fine.

What do you think might be causing it?

Thanks in advance :)

-Mark

⋅ Categories: Drupal 5.x

Comments

matt_harrold’s picture

matt_harrold commented

Total guess work here ... treat with caution.

I reckon you've got an "issue" with Apache ... possibly something to do with the .htaccess file associated with your old site.

Are you using mod_rewrite?

If you run out of memory you'll get a white screen of death ... not a Connection was Reset error ... so you could probably wind your memory setting back to 96M .. 2G is a whopping amount to allocate.

Have a look at your .htaccess files side by side (old/new) ... see if the problem jumps out of the screen.

rubenvarela’s picture

rubenvarela commented

Where do you have the WAMP folder? If it's not in the root of the drive (C:\WAMP), it could be that the path changed and it's looking for something in a folder that is not there anymore.

What where you using before Win7?

marknt15’s picture

marknt15 commented

I am using it in Snow Leopard 10.6.2 before. My WAMP folder is in its default place.

daveparrish’s picture

daveparrish commented

I was getting the same thing with Drupal 6. I found out it had to do with the Optimize CSS files in the performance options. When Optimize CSS files is turned on I get a connection reset error. I had to remove my theme directories to see the website at all and then I could change the settings. Then once that setting was changed I could turn the themes back on. I hope that helps.

marknt15’s picture

marknt15 commented

Hhmm my drupal version is 5.2 but I will try what you said. Thanks :)

selwynpolit’s picture

selwynpolit commented

Thanks for the suggestion.

I just installed Windows 7 on my laptop, latest WAMP (WAMPSERVER) and can run a new drupal 6 just fine but when I try to run a fully configured Drupal 6 site and try to go to the home page I get the error "Connection was reset" in Firefox and Chrome. Curiously, it works fine to go to a page like localhost/mysite/admin. The answer was to disable the css optimization at admin/settings/performance

Can anyone suggest to me why this should be failing? I'm just curious (and relieved now that I don't have to reinstall an older version of WAMP)

Selwyn

Selwyn Polit
https://www.drupalatyourfingertips.com/

bob.hinrichs’s picture

bob.hinrichs commented

Win 7, Drupal 6, css preprocessing on creates the the connection reset error. Same thing on my drupal 5 site running off the same machine. Apache 2.2, PHP 5.2.13. Mysql 5.1.44. Turning off CSS, the sites run again. My site has lots of RAM allocated.

I did some sleuthing and found that PHP 5.3 has caused connection reset issues (downgrading was the solution for these folks), and several other connection reset problems including one with mysql_close().

But it turns out this is a flaw in drupal's css optimizer, in the replacement pattern that replaces comments in your css files. A patch/hack can fix this-- or, maybe, taking comments with this pattern out of your css.
See http://drupal.org/node/331915 and http://drupal.org/node/444228 for a solution.

FYI I just found, apparently, that the reset error no longer occurred when this commented code was removed from the stylesheet. This pattern must have somehow caused a fault in the preg_match. So check your stylesheets and see if you have any odd comments, clear your caches and see what happens.
/* NOT NEEDED -- styles for list should be like all the others
#toolbelt .content #block-menu-menu-cool-sites .top { display: block; }
#toolbelt .content #block-menu-menu-cool-sites ul li { margin-top: .3em; margin-bottom: 0; }
#toolbelt .content #block-menu-menu-cool-sites .ext { background: none; }
#toolbelt .content #block-menu-menu-cool-sites h2 { font-weight:bold; }
*/