Could Not Access Filesystem

Have you tried putting the firewall into learning mode and seeing if automatic updates work then? Can you ask if there is a way for them to push an update out so you can test? The learning mode should whitelist the action going forward and fix the issue if that was the problem.

tim

Tim, thanks for the feedback. Yes it is in Learning Mode. I’d been experimenting with a few items which were rejected until I used the Learning Mode and it was in that mode during the last attempted update.

It just seems strange, the automatic update attempts constantly fail on the theme, every few hours but works immediately when I click the manual Update button. It feels like my level of access is higher than the applications so I thought there may be a setting or a security log I could setup/examine to see why the fs_unavailable message occurred.

What do you think?

Thanks, Len

Hi @eon123!
I just want to check to make sure, if you disable Wordfence altogether, do the updates work then? If the Firewall is in Learning mode it wouldn’t be blocking anything so I’m a bit at loss here how Wordfence would be involved at all. Just curious to hear how you figured out that Wordfence caused it. It will help me understand the situation.

Thanks!

I’m concerned about disabling Wordfence as despite the fact this is a new site and I have search engines scan turned off, Wordfence is showing it blocked over 7000 brute force attempts from over 9 countries so far this month.

So I’ll wait until the next set of theme update failures then turn Wordfence off for 24 hours and hope my site isn’t hacked in that period. However that should confirm if some Wordfence setting is impacting the security of the theme files.

I was hoping to avoid disabling Wordfence, thinking there was a WordPress log somewhere which would identify which application and reasoning for this filesystem access failure but if not possible then disabling Wordfence is my only option.

kind Regards.

Hi @eon123!

I understand your concern with disabling Wordfence. What I’m curious to know is what made you suspect Wordfence is causing the problem with EASY Update Manager (EUM) and Thrive Themes.

There is some information online that may help.

This page and this page seem to indicate it could be caused by WPML

Here is an old bug from WP Core about the same issue. Should not apply if you are using the newest version of WordPress.

Instead of deactivating Wordfence you can also try disabling other plugins to scratch them off your list of probable suspects. You can also reach out to EASY Update Manager (EUM) and Thrive Themes to see which debugging methods they have available.

We haven’t seen this issue before so I suspect it’s not related to Wordfence which makes it hard for us to debug. If you do find any indication that it is Wordfence, please get back to us with that information and we will of course look in to it.

Thanks!

Thanks you your idea. Next time the theme updates I’ll experiment as you suggested. Thanks again. Len