Community Support Forums

I just went through a test purchase on a live installation using my credit card. The process worked fine until I recieved a 500 internal error after paying and after creating my own username and password. After clicking the ¨register¨¨ button on this page: http://solutionsfortrauma.com/wp-login. ... n=register

I recieved this message: Internal Server Error.The server encountered an internal error or misconfiguration and was unable to complete your request.

I get the same message when trying to manually add members. In addition, registration confirmation emails are not being sent.

Any suggestions?

My host, MediaTemple, sent this to me today:

"There was recently a change made to our server which does removes permission from the server to call external URLs with PHP. This may be a cause of your problems. You can modify your php.ini file to allow URL calling by adding the following line:

allow_url_fopen = Enabled"

Could that be the problem? I can make the change, but I don't know exactly what it means.

- Ryan
I did the above, duplicated the php.ini that was in my root etc folder with the line above. It did not help. I am still getting the server error.

I'll email Jason asking him about this.

Did the account get created despite the error?

Thanks Cristian. On the account that I created myself - yes it was created. Last night, someone purchased my product and the account was not created. Though, he or she may not have clicked through to the register page.

- Ryan

Here are my error logs. The one's that seem relevant are near then end, having to do with the headers. The first one is related to a previous error of not being able to updgrade S2MemberPRO via Wordpress admin.

"[Wed Oct 05 22:04:39 2011] [error] [client 205.186.175.217] ALERT - script tried to increase memory_limit to 268435456 bytes which is above the allowed value (attacker '205.186.175.217', file '/nfs/c09/h02/mnt/132314/domains/solutionsfortrauma.com/html/wp-content/plugins/s2member/includes/classes/auto-eots.inc.php', line 106)

[Wed Oct 05 22:06:28 2011] [error] [client 66.211.170.66] Premature end of script headers: php5
[Wed Oct 05 22:13:51 2011] [error] [client 189.215.229.45] Premature end of script headers: php5, referer: http://solutionsfortrauma.com/wp-admin/user-new.php
[Wed Oct 05 22:20:27 2011] [error] [client 189.215.229.45] Premature end of script headers: php5, referer: http://solutionsfortrauma.com/wp-admin/user-new.php

What do you think?

For reasons that I cannot fathom, everything is working now. But I am curious as to what Jason comes up with.

By the way Christian - I saw on one of your blogs that you live in Mexico. Is that current information? I am an American but live in Merida, Mexico. Eventually, I will move to DF. Curious as to where you are....

Taxco, Guerrero. Planning to move to Mexico City too.

I'm glad it's working fine too, but I'm also curious to know what Jason can say about the problem you had.

Just notating our other conversation in this thread:
viewtopic.php?f=4&t=14957&p=45083&hilit=Premature+end+of+script+headers#p45083
Related to premature end of script headers on MT (gs).

The error regarding ini_set("memory_limit", "256M"); is harmless. s2Member just tries to get as much as it can, but some hosting providers do not allow it. I'll see what we can do to avoid this issue in the error log though. We don't want any red flags going off if we can avoid that.