Support

 Hello,

I recently built a site and installed a GoDaddy SSL certificate. Once successfully installing the certificate and applying it to the "Entire Site" with the global configuration, I'm getting "JFTP" errors on article pages and when I go to "Fix Permissions." I need to be able to fix the ownership and permissions before I can launch this site.

I read the documentation where is says that you need to make sure your host supports the CHMOD command. I called them and confirmed that they do support the CHMOD command.

When I turn the FTP layer "Off" in the global config, the errors go away and Admin Tools allows me to "Fix Permissions," but after "fixing" them, when I look in Direct Admin, all the file permissions are still set to 777 when I opened them up for development work.

Any thoughts on how to resolve this? I feel like the SSL certificated added the wrinkle that is causing the issue. Like I said, I'm basically ready to launch my clients site, but can't until I can "Fix Permissions." Thanks in advance. -SL

1. The JFTP errors suggest that you don't have the FTP layer set up properly.
2. The Fix Permissions button applies the settings set up in the Permissions Configuration button. If the defaults somehow were changed to 777 then everything is working just not how we want it to. Please check the Permissions Configuration, the "normal" settings are 755 for Directories and 644 for files.

Hey Dale,

My FTP credentials did change when we went to a dedicated IP. I updated the FTP layer in the global config accordingly. Also, I double checked, on your recommendation, the permissions configuration page and they are set to 755 and 644 for directories and files respectively.

When I enable the FTP layer and try to fix permissions, I get JFTP :chmod : Bad response.

My site lives in the private_html folder. The log, tmp, and FTP paths all point to private_html so it shouldn't be an issue, right? -SL

Can the FTP user that you have set up in the FTP layer access your private_html folder?

You can usually change permissions with your FTP client too. Just use 755 for everything, the difference for the files is not significant for php files. There is usually a check box on the permissions page in FTP to change all subfolders too.

If the private_html folder is not web accessible, then no, it doesn't make a lot of difference.

That was a good thought. I double checked and my FTP user for the FTP layer does have access to the private_html folder.

The private_html folder is web accessible.

I used the host panel to set my permissions to 755 and opened the directories specific to Joomla that need to be open. This is a good interim fix, but I'd love to get Admin Tools "fix permissions" feature working again. I use it all the time and it's extremely helpful.

With the FTP layer enabled, the admin side of Joomla is throwing errors saying I can't write to my config file. Again, all these problems started happening after I installed an SSL certificate.

Your thoughts?

Maybe Nicholas will chime in too. :-) -SL

Something just dawned on me. Since the SSL install, I haven't tried uploading any new extensions. I just tried and here is the error I got with FTP layer enabled.

JLIB_CLIENT_ERROR_JFTP_STORE_BAD_RESPONSE

JLIB_FILESYSTEM_ERROR_WARNFS_ERR02

There was an error uploading this file to the server.

Maybe this will help track down the issue. -SL

It has to be a problem with the setup of your FTP layer. I think the certificate is just a red herring, FTP wouldn't make use of it in most circumstances.

The user and password are easy, where things get messed up is in the FTP root or path. What you need there is the path from the lowest folder that the FTP user can see to the root of your site. If that path is not right, you will get errors from the FTP layer.

I think we came to the same conclusion and I got it working!

My FTP user did have access to the public_html folder, it access a few levels higher up, and even though I had changed the path to /private_html in the FTP layer, that FTP user was looking at the wrong root.

What I did was create a new FTP user and set the path in the host panel for that user directly to private_html and set the path in the FTP layer in the global config to "/" and the Fix Permissions worked!

Thanks for helping me think this one through Dale! -SL

You're welcome! I'm glad you got it working.