newb2seo
05-16-2009, 06:11 AM
Hi. I'm having a problem using an add-on domain.
I first added the domain.
Then removed that sub folder.
And set a symbolic link to point to an upper directory... same level as public_html.
This way I can have all my domains on the same level and its easier to backup just one directory/domain etc instead of having all the add-ons inside of the main public_html.
This is all pretty standard.
But right now, I can't get php to work inside that new domain.
It works when I use the .html on a file. But nothing with .php works.
I asked support and they said this:
I apologize for the problem you are experiencing.
This evening, we rolled out an update to one of the database backends we offer. We had updated several servers before we realized that the update had modified the Apache configuration file incorrectly, and broken certain php libraries. As a result, any php file that tries to access those libraries generates the 500 Internal Server Error you are seeing.
Our Admins have identified the issue, and are working to restore the affected servers as quickly as possible. Be assured that no files or account data were affected - only the servers ability to display the information was impaired.
We should have your site back up shortly.
I'm just wondering if anyone else has this same problem or if the problem is more due to how I have mine set up.
I guess time will tell.
Any advice is appreciated.
Thanks.
-newb
I first added the domain.
Then removed that sub folder.
And set a symbolic link to point to an upper directory... same level as public_html.
This way I can have all my domains on the same level and its easier to backup just one directory/domain etc instead of having all the add-ons inside of the main public_html.
This is all pretty standard.
But right now, I can't get php to work inside that new domain.
It works when I use the .html on a file. But nothing with .php works.
I asked support and they said this:
I apologize for the problem you are experiencing.
This evening, we rolled out an update to one of the database backends we offer. We had updated several servers before we realized that the update had modified the Apache configuration file incorrectly, and broken certain php libraries. As a result, any php file that tries to access those libraries generates the 500 Internal Server Error you are seeing.
Our Admins have identified the issue, and are working to restore the affected servers as quickly as possible. Be assured that no files or account data were affected - only the servers ability to display the information was impaired.
We should have your site back up shortly.
I'm just wondering if anyone else has this same problem or if the problem is more due to how I have mine set up.
I guess time will tell.
Any advice is appreciated.
Thanks.
-newb