frontpage ext still not work

[iyan]

helo,

i have read all about frontpage problem here, but still not work,

1. disable frontpage ext
2. delete all files in public_html,

rm * -rf
rm * .htacess

3. enable frontpage again

but when i open web from frontpage editor, the error is always said :

The folder "http://www.domain.com/ isn't accessible. Folder may be located in an unavailaible location, protected with a password, or the filename contains a / or \.

need solution

regards

[DirectAdmin Support]

Hello,

I'm quite sure where you are typing that, but try removing the / from the end of the domain. If you accidently deleted the public_html directory, you'll need to recreate it...

John

[iyan]

Sorry, wrong room last :)

Helo,

still not work

1. disable frontpage by user

cd /home/user/domains/
rm -rf *
mkdir -p domains/domain.com/public_html
chown user.user domains -R

2. enable frontpage again
3. open frontpage editor
4. still got same error,

regards
IYAN

[DirectAdmin Support]

Hello,

I can't say for sure why it's doing that. If you send us your ip and account info (and root if you have it) we'll have a look.

John

[iyan]

Dear John,

the server using DA is not publish yet, we still do migrating all of user data, because of the old production server have same IP Address with this DA server,

the only problem is frontpage ext, i will contact u soon if the server is publish,

I have to say that DA is Wonderfull !

Regards
IYAN

[Andrax]

I thought that the domain had to be live before FP /extensions would work anyway....

[iyan]

Helo John,

i have setup 1 DA dan 1 windows pc client, and just only 2 connected, client can surf DA server, i point dns to DA, and everything fine, client can mail, surf, etc.

ok, until now i don't understand why the problem is, in my old server frontpage work fine,

ok, no problem ... i will publish the server soon and u can check it, the user data still in migration progress.

Thanks alot john

[DirectAdmin Support]

Hello,

I've fixed one frontpage problem by changing the user/group that apache runs as... previously, it was running as "apache/apache". I checked the frontpage logs (/var/log/httpd/fpexec_log) and it was complaining that apache wasn't "nobody"... so I changed the main httpd.conf to use nobody/nobody instead and that seemed to fix it. I'm a bit confused as this is the first time this error has popped up... I'll see about recompiling frontpage to use "apache/apache" instead of nobody because there are other files (webmail) that currently use the "apache" user/group.

John

[iyan]

Helo john,

sorry before, i didn't check frontpage logs :),

the frontpage is working now! thanks

regards
IYAN