Facebook
Twitter
0
01010110
Guest
Using Frontpage 2002 to connect to a website created by PLesk 6.5.2
I have tried as admin, advanced author and author to connect via and always get the same problem. First, as expected I get the username and password dialog. After entering the correct credentials I get "You do not have permission..." (see http://walkerhosting.biz/images/noperm.gif for full message).
If I click OK the dialog comes up again with my username and password filled in. Click OK and the "You do not have permission..." error reappears.
This cycle happens up to 5 times and eventually I can see the website, BUT it doesn't show what you'd expect but something peculiar, such as:
http://domain.com/domain.com_non_ssl
As a consequence of this saving new files fail unless you put the full path in which must include the additional domain.com_non_ssl part beyond the domain name.
I spoke with an MVP and described the problem. He said the authentication issue maybe because the permissions need to be set on the root as well as the /domain.com_non_ssl part.
Has anyone worked out how to publish directly to the domain name (without having to add /domain.com_non_ssl) and how to fix the problems with the repeating cycle of username/password dialog boxes and permission errors?
Many thanks.
Martyn
I have tried as admin, advanced author and author to connect via and always get the same problem. First, as expected I get the username and password dialog. After entering the correct credentials I get "You do not have permission..." (see http://walkerhosting.biz/images/noperm.gif for full message).
If I click OK the dialog comes up again with my username and password filled in. Click OK and the "You do not have permission..." error reappears.
This cycle happens up to 5 times and eventually I can see the website, BUT it doesn't show what you'd expect but something peculiar, such as:
http://domain.com/domain.com_non_ssl
As a consequence of this saving new files fail unless you put the full path in which must include the additional domain.com_non_ssl part beyond the domain name.
I spoke with an MVP and described the problem. He said the authentication issue maybe because the permissions need to be set on the root as well as the /domain.com_non_ssl part.
Has anyone worked out how to publish directly to the domain name (without having to add /domain.com_non_ssl) and how to fix the problems with the repeating cycle of username/password dialog boxes and permission errors?
Many thanks.
Martyn
