|
amp
|
 |
« on: September 11, 2006, 09:11:49 AM » |
|
Hello all, I've been a customer for about 24 hours! Basic www hosting on 80 works fine... now trying to add one of these blog scripts... so far I've installed wordpress and nucleus. Both have errored out. The install goes fine... but when I try to access the directory/program, I get error 403 , forbidden. I checked the permissions and all looks good.... not sure what I'm missing here.
Any tips would be great... Thanks!
|
|
|
|
|
Logged
|
|
|
|
|
fretnmore
|
|
« Reply #1 on: September 11, 2006, 10:36:39 AM » |
|
Did you get a new domain name from LP, or are you pointing an older domain name or one purchased elsewhere to LP? It can take up to 72 hours for domain changes to propogate and in the meantime, php code will not resolve. If you purchased a new domain name from LP, then I would suggest writing to support@lunarpages.com with your problem. You can write to support@lunarpages.com and request a temporary subdomain in order to test everything until propogation completes. I hope that this is helpful. |
|
|
|
|
Logged
|
|
|
|
|
amp
|
|
« Reply #2 on: September 11, 2006, 11:01:53 AM » |
|
Thanks... I'll write them. This is a new domain name with LP... all brand new with them.
|
|
|
|
|
Logged
|
|
|
|
|
MrPhil
|
|
« Reply #3 on: September 11, 2006, 12:41:43 PM » |
|
Hello all, I've been a customer for about 24 hours!
Welcome aboard!  Is your domain name resolving correctly, or are you still using the temporary access name they give you? I think some stuff (PHP scripts?) doesn't work on the temporary access domain. That might explain problems with PHP-based blog scripts and such. when I try to access the directory/program, I get error 403 , forbidden. I checked the permissions and all looks good.... not sure what I'm missing here.
What do you mean by "looks good"? Are all directories properly located ( under public_html/) and permission 755? Are all the scripts 755? Phil |
|
|
|
|
Logged
|
|
|
|
|
amp
|
|
« Reply #4 on: September 11, 2006, 05:37:03 PM » |
|
Thanks for the reply and welcome! Yes, everything resolves correctly... as far as I can tell... I can browse the html of the site as normal using the dns name. I've tried installing all 3 blog scripts... the install seems fine... all 3 steps of the install proceed fine.. no errors... the mysql accounts are created... the folder and file permissions are fine... 755 on everything... but when I try to access the admin page of the blog, I get 403... so , I'm stumped... for example: http://mysite.com/nucleus or http://mysite.com/word/wp-adminWas there anything I was supposed to do before running these scripts? Keep in mind this is a brand new account... but I do have 'some' hosting knowledge... |
|
|
|
|
Logged
|
|
|
|
|
amp
|
|
« Reply #5 on: September 12, 2006, 08:52:02 AM » |
|
Ok... I have a major update to this problem. If I install the scripts in the root (html_public) , it works. However, when I specifiy a folder other than root, it does not work.
Why is that?
|
|
|
|
|
Logged
|
|
|
|
|
MrPhil
|
|
« Reply #6 on: September 12, 2006, 10:57:16 AM » |
|
Ok... I have a major update to this problem. If I install the scripts in the root (html_public) , it works. However, when I specifiy a folder other than root, it does not work.
Why is that?
Hmm. You install the products in public_html/, and they work fine. You install them in directorie(s) below public_html/ (e.g., public_html/blogstuff/) and you get 403 errors? And all directory and executable script permissions are 755? You're not putting them above public_html/ (e.g., /home/<acct_name>/blogstuff/), by any chance? All I can think of is to look in the scripts and see if there is any hardcoded configuration stuff that you need to update (i.e., the blog script expected to be installed in public_html/, and is setting the absolute path to various things based on that). In that case, the installation instructions would likely either warn you to install only in root ( public_html/), or that you will need to update some path information somewhere. I would think a 404 error would be more likely in such a case, but you never know... Are you getting the 403 errors on the main entry point script, or on some script or directory down inside the blog software? Are you completely removing all traces of the stuff installed in public_html/ before reinstalling in another directory? Phil |
|
|
|
|
Logged
|
|
|
|
|
amp
|
|
« Reply #7 on: September 12, 2006, 11:29:20 AM » |
|
These are the instructions regarding the install directory: "Leave empty to install in the root directory of the domain (access example: http://domain/). Enter only the directory name to install in a directory (for http://domain/name/ enter name only). This directory SHOULD NOT exist, it will be automatically created!" So I was entering in 'blog' - because I didn't want all of the script files on my root... So it would make the folder and copy all the files into 'blog', but nothing would work from http://mysite.com/blog - however, all scripts work fine if I do not specify a directory and just let it install on the root... which I don't really like... but oh well. |
|
|
|
|
Logged
|
|
|
|
|
MrPhil
|
|
« Reply #8 on: September 12, 2006, 12:07:57 PM » |
|
Well, it sounds like you did everything right on your end. There was no public_html/blog/, you entered "blog", it created public_html/blog/ and loaded everything into it, but the scripts don't work ( http://mysite.com/blog/script_name). All I can guess is there's a bug in the install process that isn't setting some path or absolute address correctly (check if the products update .htaccess, as well as internally to scripts). It's always possible that someone made "a tiny little insignificant fix" somewhere and didn't bother to test it with a non-root location (everyone who's done something like that in their career raise your hand  ). Are there any boards to discuss the two products, either here (LF) or elsewhere? If no answer, is there a place to report bugs? If they work when both are installed in the root ( public_html/), it doesn't sound like they're stepping on each other. Dunno, I'm fresh out of bullets here. Phil |
|
|
|
|
Logged
|
|
|
|
|
amp
|
|
« Reply #9 on: September 12, 2006, 12:32:54 PM » |
|
yeah, I've got an open ticket with support, so we'll see if / when they get back with me... For now, I'm not too worried about it... at least I can get the scripts working. I was just getting a little frustrated... Thanks for helping me out!
|
|
|
|
|
Logged
|
|
|
|
|
Lupine1647
|
|
« Reply #10 on: September 12, 2006, 04:39:33 PM » |
|
Hello,
I looked up your ticket and it looks like everything has been resolved.
|
|
|
|
|
Logged
|
|
|
|
|
amp
|
|
« Reply #11 on: September 12, 2006, 06:04:03 PM » |
|
Thanks for the reply.... although, I just don't understand... I tried installing the 'wordpress' blog into a folder named "blog" on the root.... again it doesn't work. I must be missing something  |
|
|
|
|
Logged
|
|
|
|
|
RandyT
Guest
|
|
« Reply #12 on: September 12, 2006, 06:08:36 PM » |
|
Were you using ftp to upload the wordpress files to that "blog" folder ? You need to check the files that are there against the ones you downloaded to your local machine to make sure none were left out during the upload. That happens sometimes. Also make sure your ftp is set to "auto" mode. Then there is the permission settings, 755 with LP. Other than that, as long as the database info is entered correctly in the config.php file it should work. I just added WP to my site without a hitch. Post back if you still need help and we will try and get is sorted out.
Hope this helps,
RandyT
|
|
|
|
|
Logged
|
|
|
|
|
amp
|
|
« Reply #13 on: September 13, 2006, 05:17:22 AM » |
|
Hi there, Thanks for the reply....
I'm not using FTP... just trying to run the fantastico script. Again, it'll work if I don't specify an install folder and let it use the root... but if I do specify an install folder "blog" for example, it will not work.
Can you try the fantastico install on your system? And specify an install folder....
|
|
|
|
|
Logged
|
|
|
|
|
amp
|
|
« Reply #14 on: September 14, 2006, 04:11:46 PM » |
|
Just thought I'd follow this up.... Turns out my problem was a "mod_security issue" - - a server tech changed whatever it was and now everything is fine. - - talk about a frustrating 3 days!
|
|
|
|
|
Logged
|
|
|
|
|
