Forum Replies Created

Viewing 10 replies - 1 through 10 (of 10 total)
  • Thread Starter Jennifer

    (@ratgurrl)

    Thank you! ??

    Thread Starter Jennifer

    (@ratgurrl)

    I figured it out.

    I had to manually create a folder called “aiowps_backups” in the wp-content folder, then chmod to 777 — I was then able to do a backup.

    I looked at a backup of an old install from 2019 and saw that I had that folder created in the install. Since it seems to require 777 permissions, I’m going to make a symlink to a directory outside of my webroot.

    It must be something with how the server is setup — possibly ownership of the directories (owned by my user from manual upload, rather than httpd user, perhaps).

    Thanks for your assistance and suggestions.

    Jen

    Thread Starter Jennifer

    (@ratgurrl)

    I’m going to give up, and just do manual backups if/as needed. However, I’m Happy to do more troubleshooting if it will be helpful.

    Thread Starter Jennifer

    (@ratgurrl)

    There are 3 critical errors found:

    Error #1: I have FTP disabled on my server and use only SSH

    Background updates are not working as expected Security
    Background updates ensure that WordPress can auto-update if a security update is released for the version you are currently using.

    Warning Could not confirm that the wp_version_check() filter is available.
    Passed No version control systems were detected.
    Error Your installation of WordPress prompts for FTP credentials to perform updates. (Your site is performing updates over FTP due to file ownership. Talk to your hosting company.)

    Error# 2:

    The REST API encountered an error Performance
    The REST API is one way WordPress, and other applications, communicate with the server. One example is the block editor screen, which relies on this to display, and save, your posts and pages.

    The REST API request failed due to an error.
    Error: [] cURL error 60: SSL certificate problem: unable to get local issuer certificate

    Error #3:

    Your site could not complete a loopback request Performance
    Loopback requests are used to run scheduled events, and are also used by the built-in editors for themes and plugins to verify code stability.

    The loopback request to your site failed, this means features relying on them are not currently working as expected.
    Error encountered: (0) cURL error 60: SSL certificate problem: unable to get local issuer certificate

    Need to update my php.ini file with th CA to get rid of the Curl error, but otherwise nothing that looks related to file/folder permissions.

    *scratching head*

    Thread Starter Jennifer

    (@ratgurrl)

    Running the health check plugin now.

    Thread Starter Jennifer

    (@ratgurrl)

    I just did a brand new clean installation of WordPress and the AIO plugin. AOI is the only plugin enabled, and there are no other plugins or themes installed/activated. I’m still getting the same error(s).

    I tried installing as mydomain.tld/wordpress, and also in the root of mydomain.tdl

    Cannot backup .htaccess file
    Cannot backup database

    All folders are set to 755 and all files are set to 644

    Running WP 5.5.3
    AIO 4.4.4

    Jen

    Thread Starter Jennifer

    (@ratgurrl)

    Hi! Thanks for checking in. Due to the holiday, I haven’t had an opportunity to futz with it further. I’m taking another look at it this evening and will follow up!

    Thread Starter Jennifer

    (@ratgurrl)

    I will try the health plugin you recommended and will report back with any additional info. Thank you!

    I’m running a QNAP NAS and have had it for about 7 years. No issues.

    Thread Starter Jennifer

    (@ratgurrl)

    Thanks for the reply. I’m running this myself on my own server, so I am my own host ??

    The only plug-in I have enabled is the Akismet as this is a fresh install to troubleshoot/replicate the issue I was having on the live site.

    I’ll try turning that off, since I haven’t done that yet.

    I’m baffled as to how there could be a permissions error, since I’ve checked everything multiple times (and have reinstalled the entire WordPress installation from scratch 3 times).

    It makes no sense! I’v used previous versions of this plugin/Wordpress without issue. If anyone has any ideas at all, I would be most grateful for suggestions.

    I’m going to try a 100% clean install once more. ????

    Thread Starter Jennifer

    (@ratgurrl)

    Yeah, that would be an issue on a large database, I didn’t think about that. However, could it be an admin option? Default would be off, but for those who have a small database could activate the option (with a warning that it would slow performance).

Viewing 10 replies - 1 through 10 (of 10 total)