I activated the contact module on my site tonight and for some reason I can't get it to work. Everything seemed to be going well until I actually tried to send a message from mydomain.com/contact and then in Firefox (mac) I got a white screen with the same url showing in the address bar. No e-mail was sent.

In Safari I got a page saying Safari can’t open the page “http://mydomain.com/contact” because the server unexpectedly dropped the connection

In Opera it says: You tried to access the address http://mydomain.com/contact, which is currently unavailable. Please make sure that the Web address (URL) is correctly spelled and punctuated, then try reloading the page.

Any ideas on what I could try?

Comments

joshmv’s picture

joshmv commented
Title: Contact form gives me a WSOD after hitting "send" » Getting WSOD On Contact Forms & User Registrations
Component: contact.module » base system

Just noticed I'm getting the same thing on new user registrations. The users are actually getting registered in the system but right after they register it's going to a WSOD. It doesn't seem to be a module issue since I deactivated all of them and the issue was still there. I also got the error log from my server and there was nothing from the domain the drupal installation is on.

Today I installed a fresh copy of drupal on a different domain but on the same server and it's doing the same thing so I'm pretty positive its on the server side. Unfortunately I'm not seeing anything in the error logs so I'm not sure where to start.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Status: Active » Postponed (maintainer needs more info)

Hard to help without more information. See http://drupal.org/node/158043 on debugging WSOD's.

joshmv’s picture

joshmv commented
Status: Postponed (maintainer needs more info) » Closed (fixed)

Hey Dave,

Thanks for the reply. After spending hours trying to figure it out, finally my web host figured out it was something on their end with the mail system and it was holding drupal up.