[News]

News: Welcome to Hostpapa Forums!

[scott]

I registered my website today and then followed the instructions to use the Soholaunch.   I went to the Cpanel, clicked on fantastico, and then loaded the pro edition software.   I received my login instructions by email and then nothing.   I can't seem to access the sohoadmin page of my website or do anything else.   I thought this was suppose to be simple!!  Did I miss something?  Can anyone explain what to do next?

[Darryl]

The most common problem here, is after you install it, you don't know that the url to actually build your site is http://yourdomain.com/sohoadmin.  Go there, and a popup window asks you to log in.

Your Login Information email from us has this, I believe, but we know it's a long email, and it's easy to miss something like that. 

I hope that helps!

[jenniferlucking]

Why is it that when I go to http://yourdomain.com/sohoadmin (using my domain name of course), I get the following error message???

500 Internal Server Error

The page cannot be displayed.




I've tried uninstalling and reinstalling and it keeps doing this. I've never been able to log in to soho.

[HelpingHand]

Go into cPanel > Error Logs and it will tell you why you are getting the internal server error. Usually it has to do with folder and file permissions or incorrect statements in your .htaccess file. Post the error log entries here or contact live support and they might, 'might', be able to help.

[HelpingHand]

The permissions are wrong on your public_html folder. Go into cPanel and click File Manager. Select Home Directory and click Go. Look at the list of folders and the public_html folder will most likely say 775 to the right of it. Select the public_html folder and click Change Permissions. Uncheck the very middle box (under Group and in the Write row). The permission should now say 755 instead of 775. Click Change Permissions to save the change. Now your public_html folder is no longer 'writable by group' and you should be able to get into sohoadmin. If you still have the error, but on a different folder or subfolder, I would submit a ticket to support and ask them to 'recursively change permissions on all folders to 755.' Hope this helps.