[Resolved] FrontPage Instructions for LiteSpeed + cPanel

[tina]

We tried running the following which you recommended:

sed -rie 's/(safe_)?chmod\(( )?0600,( )?("\$\{myuid\}",)?( )?"\$(\{)?homedir(\})?\/public_html\$\{subweb\}\/_vti_pvt\/service.pwd"( )?\);/\1chmod(\20644,\3\4\5"$\6homedir\7\/public_html${subweb}\/_vti_pvt\/service.pwd"\8);/' /scripts/fp-auth /usr/local/frontpage/version5.0/apache-fp/fp-auth /usr/local/cpanel/bin/convertfppassthrough /scripts/fixfrontpageperm

But users are still unable to publish using FrontPage.

Is this still the correct command to run on the latest stable cPanel 11.25.0-S44718 ?

[tina]

We found that running the above command followed by /scripts/fixfrontpageperm does not actually chmod or chown the service.pwd files.

When we manually changed service.pwd with the correct ownership and permissions, it works for the user, but the ownership and permissions keep getting changed back (not during cPanel updates).

We are guessing that they are somehow automatically changed back every time the user publishes using FrontPage.

Surely there are many other LiteSpeed + cPanel users running into this problem with FrontPage?

[Tony]

It has been fine for us since 4.0.5 when they did this:

Added support for mod_auth_passthrough to seamlessly integrate with cPanel FrontPage extension.


We just enable frontpage in the lsws panel and it all works for the users.

[tina]

Thanks Tony, does that mean that your service.pwd files are still at cPanel's default ownership user:user and permissions 0600, and it still works perfectly?

[Tony]

Originally Posted by tina

Thanks Tony, does that mean that your service.pwd files are still at cPanel's default ownership user:user and permissions 0600, and it still works perfectly?

Yep that's right. Previously it involved those commands and some other things to get it to work for a user which broke after every cPanel update. Since that change everything worked fine with the default permissions.

[tina]

Originally Posted by Tony

Yep that's right. Previously it involved those commands and some other things to get it to work for a user which broke after every cPanel update. Since that change everything worked fine with the default permissions.

Understood; thanks again for your very kind responses.