• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Frontpage does not..

A

anton_latvia

Guest
Hi, I have problem with frontpage.
One of clients decided to use Frontpage and I have enabled it (also with Frontpage authoring). Icon FPWebadmin has become available and if I click there - it asks for username and password. If I specify it, it comes up with an error page 404 Page not found! (http://www.domain.com/_vti_bin/_vti_adm/fpadmcgi.exe?page=webadmin.htm)

And also it is not possible to connect to it through Fronpage. How can I fix this problem?

Thanks!
 
What OS and Plesk versions are you running?

After enabling FP, did you then also restart the apache service from the Server / Service Management screen?
 
I am running RedHat 9.0, Plesk 7.5.2. I did apache restart from shell.
 
2 suggestions: first re-install the FP rpm, then reboot the whole box.
 
I'm having this problem on FSBD 4.9. I've tried restarting apache and uninstalling and reinstalling FP on the site in question. Any help would be appreciated. Thanks
 
I have solved this problem with the following steps:
1. reinstall FP
2. restart server
3. disable FP for this domain
4. restart apache
5. enable FP for this domain
6. restart apache.
 
Back
Top