AMFPHP Help. Error 500 - Internal Server Error.

Hi,

I feel kind of stupid since Lee said it was an easy install yet I somehow found a way to get an error. Anyways, I downloaded the latests 1.9beta2, installed in root directory, and went to my test spot: http://www.mattmazzola.net/amfphp/browser/ and voila "Error 500 - Internal Service Error." I was so excited about doing this tutorial but now it seems like i'll never enjoy the amfphp . I went to the amfphp.org website to look for installation help but they seem to talk more about gateway.php configuration which lee hasn't gone over yet and didn't seem like it would help my case. Also, I called my hosting provider 1and1.com, they verified that i have PHP4 and PHP5 installed and they said I need to talk with developers to find out why the error may happen in order for them give me a good answer since it's just a generic error. It's understandable that they can't give answers for all these 3rd party applications so here I am. Anyone have any ideas? Can anyone else with a 1and1 account try to install to see if it's their servers or if it's just some weird configuration i have?

-prince

[[ Paul Ferrie ]]

error 500 explained.

Hope it helps

Yea, I actually found that same page when searching on google but when I called my hosting and told them i was trying to install AMFPHP they didn't really know what it was and didn't know why the error could have been generated and they told me my best bet would be to go on the amfphp.org forums to ask the developers what circumstances would cause this error but their forums are through sourceforge and I didn't feel like doing that. Thanks though, I'll keep messing around with it I guess.

[James]

Delete any .htaccess files in the amfphp directory (this is a common problem that will bring up a 500 error).

James- thank you. I can't believe I searched half the day for this.

Delete any .htaccess files in the amfphp directory (this is a common problem that will bring up a 500 error).

Actually don't delete anything, that file is a security file that blocks outsiders access.
It is obvious that a file like ../amfphp/browser/index.html should have some sort of protection. In order to access it you have to log through ftp , so log on thorough ftp on site, browse and open the file and it will work and safe

[James]

Actually don't delete anything, that file is a security file that blocks outsiders access.
It is obvious that a file like ../amfphp/browser/index.html should have some sort of protection. In order to access it you have to log through ftp , so log on thorough ftp on site, browse and open the file and it will work and safe

That file should be deleted. It is only meant for local testing use. htaccess files are not necessary and interfere with gateway calls. External access to the gateway via AMF can be controlled in the cross-domain policy XML file.

If you really want to keep the service browser on your production machine, then consider using htaccess for the browser directory only, but not the parent amfphp directory. However, this is still a security risk and I don't see why you would do it.