I am getting the following error messages showing and wondered if you could advise how to resolve this?
Warning: mkdir(): Permission denied in /…/public_html/wp-content/plugins/amazon-auto-links/include/core/_common/utility/file/AmazonAutoLinks_VersatileFileManager.php on line 48
Warning: file_put_contents(/tmp/WPAAL/4b44c2a77edcfec14e519e515e2cb8af/versatile/AAL_LOCK_PAAPI_REQUEST_UK_062b37cc782aa5f72a70784fc9152013.txt): failed to open stream: No such file or directory in /…/public_html/wp-content/plugins/amazon-auto-links/include/core/_common/utility/file/AmazonAutoLinks_VersatileFileManager.php on line 89
]]>Unable to create directory wp-content/uploads/2019/05. Is its parent directory writable by the server?
I’ve never before gotten a message like this, and every media upload has been trouble free. And there’s nothing at all unusual about the jpg image that I’m attempting to upload.
I have the Health-Check plugin installed, but it’s not telling me anything.
Any suggestions?
Best regards,
John Drew
]]>How or where do I fix that. I have already tried disabling and re-enabling as well as uninstalling and re-installing it as suggested. Nothing worked.
]]>Could not write to file. Please check filesystem permissions. Filename: /home/content/a2pewpnaspod04_data04/34/41290634/html/wp-content/gallery/teset3/…..
When I try to create a new gallery, the image UL fails and the screen just fades and clears. The gallery was previously working fine and I have several working galleries on the site.
I have tried the following steps:
1. Ensured both /wp-content directory and gallery folder have proper permissions
2. Reset WordPress permalinks
3. Shut off all other plugins to ensure no interference
4. Cleared browser cache and Nextgen cache
5. Tried default WP theme
6. WP and all plugins are 100% up to date
7. I have run a malware scan
8. I have checked the php.ini and its set to 128mb memory
I can’t think of anything else to try, any thoughts?
I upgraded to WordFence 6.1.1 this morning, but trying to configure its firewall displays:
“We were unable to write to ~/wp-content/wflogs/ which the WAF uses for storage. Please update permissions on the parent directory so the web server can write to it.”
There are no additional buttons or other options on this screen.
I tried deactivating two other plugins that potentially conflict with WordFence (NinjaFirewall and Sucuri), changing the Upload setting in NinjaFirewall to allow file uploads, updating to the 6.1.2 version of Wordfence, and uninstalling & reinstalling WordFence: No change.
Interestingly, the WordFence firewall configures OK on some other sites I manage, just not this one – and those other sites have NinjaFirewall and Sururi configured similarly to this one.
I’d be happy to manually configure some permissions, but it’s not clear from the error message precisely which directory is “the parent directory”, or what permissions WordFence needs. I did note, however, that the wflogs directory has “the usual” files in it, so WordFence is able to write to that directory:
# ls -al /ReadyNAS-Volume/public_html/wp-content/wflogs
total 88
drwxr-xr-x+ 1 admin admin 128 Apr 12 10:40 .
drwxrwxrwx+ 1 guest guest 142 Apr 12 09:35 ..
-rw-rw-rw-+ 1 admin admin 40083 Apr 12 09:35 attack-data.php
-rw-------+ 1 root root 711 Apr 12 10:40 config.php
-rw-rw-rw-+ 1 admin admin 133 Apr 12 09:35 .htaccess
-rw-rw-rw-+ 1 admin admin 51 Apr 12 09:35 ips.php
-rw-rw-rw-+ 1 admin admin 18457 Apr 12 09:35 rules.php
-rw-rw-rw-+ 1 admin admin 13814 Apr 12 09:35 wafRules.rulesAny ideas?
Thanks.
https://www.ads-software.com/plugins/wordfence/
]]>I am getting a 403 Forbidden error and Incorrect file/directory permissions: Below 644 for all my domains. This is of probably because of some settings in .htaccess and I wonder if you know of this issues and how to solve it?
Here is a copy of the htaccess file:
# BEGIN All In One WP Security
#AIOWPS_BLOCK_WP_FILE_ACCESS_START
<Files license.txt>
order allow,deny
deny from all
</files>
<Files wp-config-sample.php>
order allow,deny
deny from all
</Files>
<Files readme.html>
order allow,deny
deny from all
</Files>
#AIOWPS_BLOCK_WP_FILE_ACCESS_END
#AIOWPS_BASIC_HTACCESS_RULES_START
<Files .htaccess>
order allow,deny
deny from all
</Files>
ServerSignature Off
LimitRequestBody 10240000
<Files wp-config.php>
order allow,deny
deny from all
</Files>
#AIOWPS_BASIC_HTACCESS_RULES_END
#AIOWPS_PINGBACK_HTACCESS_RULES_START
<Files xmlrpc.php>
order deny,allow
deny from all
</Files>
#AIOWPS_PINGBACK_HTACCESS_RULES_END
#AIOWPS_DISABLE_INDEX_VIEWS_START
Options -Indexes
#AIOWPS_DISABLE_INDEX_VIEWS_END
#AIOWPS_DISABLE_TRACE_TRACK_START
RewriteEngine On
RewriteCond %{REQUEST_METHOD} ^(TRACE|TRACK)
RewriteRule .* – [F]
#AIOWPS_DISABLE_TRACE_TRACK_END
#AIOWPS_FORBID_PROXY_COMMENTS_START
RewriteCond %{REQUEST_METHOD} =POST
RewriteCond %{HTTP:VIA}%{HTTP:FORWARDED}%{HTTP:USERAGENT_VIA}%{HTTP:X_FORWARDED_FOR}%{HTTP:PROXY_CONNECTION} !^$ [OR]
RewriteCond %{HTTP:XPROXY_CONNECTION}%{HTTP:HTTP_PC_REMOTE_ADDR}%{HTTP:HTTP_CLIENT_IP} !^$
RewriteCond %{REQUEST_URI} !^/(wp-login.php|wp-admin/|wp-content/plugins/|wp-includes/).* [NC]
RewriteRule .* – [F,NS,L]
#AIOWPS_FORBID_PROXY_COMMENTS_END
#AIOWPS_DENY_BAD_QUERY_STRINGS_START
RewriteCond %{QUERY_STRING} tag= [NC,OR]
RewriteCond %{QUERY_STRING} ftp: [NC,OR]
RewriteCond %{QUERY_STRING} http: [NC,OR]
RewriteCond %{QUERY_STRING} https: [NC,OR]
RewriteCond %{QUERY_STRING} mosConfig [NC,OR]
RewriteCond %{QUERY_STRING} ^.*(globals|encode|localhost|loopback).* [NC,OR]
RewriteCond %{QUERY_STRING} (\;|’|\”|%22).*(request|insert|union|declare|drop) [NC]
RewriteRule ^(.*)$ – [F,L]
#AIOWPS_DENY_BAD_QUERY_STRINGS_END
#AIOWPS_ADVANCED_CHAR_STRING_FILTER_START
<IfModule mod_alias.c>
RedirectMatch 403 \,
RedirectMatch 403 \:
RedirectMatch 403 \;
RedirectMatch 403 \=
RedirectMatch 403 \@
RedirectMatch 403 \[
RedirectMatch 403 \]
RedirectMatch 403 \^
RedirectMatch 403 \`
RedirectMatch 403 \{
RedirectMatch 403 \}
RedirectMatch 403 \~
RedirectMatch 403 \”
RedirectMatch 403 \$
RedirectMatch 403 \<
RedirectMatch 403 \>
RedirectMatch 403 \|
RedirectMatch 403 \.\.
RedirectMatch 403 \%0
RedirectMatch 403 \%A
RedirectMatch 403 \%B
RedirectMatch 403 \%C
RedirectMatch 403 \%D
RedirectMatch 403 \%E
RedirectMatch 403 \%F
RedirectMatch 403 \%22
RedirectMatch 403 \%27
RedirectMatch 403 \%28
RedirectMatch 403 \%29
RedirectMatch 403 \%3C
RedirectMatch 403 \%3E
RedirectMatch 403 \%3F
RedirectMatch 403 \%5B
RedirectMatch 403 \%5C
RedirectMatch 403 \%5D
RedirectMatch 403 \%7B
RedirectMatch 403 \%7C
RedirectMatch 403 \%7D
# COMMON PATTERNS
Redirectmatch 403 \_vpi
RedirectMatch 403 \.inc
Redirectmatch 403 xAou6
Redirectmatch 403 db\_name
Redirectmatch 403 select\(
Redirectmatch 403 convert\(
Redirectmatch 403 \/query\/
RedirectMatch 403 ImpEvData
Redirectmatch 403 \.XMLHTTP
Redirectmatch 403 proxydeny
RedirectMatch 403 function\.
Redirectmatch 403 remoteFile
Redirectmatch 403 servername
Redirectmatch 403 \&rptmode\=
Redirectmatch 403 sys\_cpanel
RedirectMatch 403 db\_connect
RedirectMatch 403 doeditconfig
RedirectMatch 403 check\_proxy
Redirectmatch 403 system\_user
Redirectmatch 403 \/\(null\)\/
Redirectmatch 403 clientrequest
Redirectmatch 403 option\_value
RedirectMatch 403 ref\.outcontrol
# SPECIFIC EXPLOITS
RedirectMatch 403 errors\.
RedirectMatch 403 config\.
RedirectMatch 403 include\.
RedirectMatch 403 display\.
RedirectMatch 403 register\.
Redirectmatch 403 password\.
RedirectMatch 403 maincore\.
RedirectMatch 403 authorize\.
Redirectmatch 403 macromates\.
RedirectMatch 403 head\_auth\.
RedirectMatch 403 submit\_links\.
RedirectMatch 403 change\_action\.
Redirectmatch 403 com\_facileforms\/
RedirectMatch 403 admin\_db\_utilities\.
RedirectMatch 403 admin\.webring\.docs\.
Redirectmatch 403 Table\/Latest\/index\.
</IfModule>
#AIOWPS_ADVANCED_CHAR_STRING_FILTER_END
#AIOWPS_FIVE_G_BLACKLIST_START
# 5G BLACKLIST/FIREWALL (2013)
# @ https://perishablepress.com/5g-blacklist-2013/
# 5G:[QUERY STRINGS]
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{QUERY_STRING} (\”|%22).*(<|>|%3) [NC,OR]
RewriteCond %{QUERY_STRING} (javascript:).*(\;) [NC,OR]
RewriteCond %{QUERY_STRING} (<|%3C).*script.*(>|%3) [NC,OR]
RewriteCond %{QUERY_STRING} (\\|\.\./|`|=’$|=%27$) [NC,OR]
RewriteCond %{QUERY_STRING} (\;|’|\”|%22).*(union|select|insert|drop|update|md5|benchmark|or|and|if) [NC,OR]
RewriteCond %{QUERY_STRING} (base64_encode|localhost|mosconfig) [NC,OR]
RewriteCond %{QUERY_STRING} (boot\.ini|echo.*kae|etc/passwd) [NC,OR]
RewriteCond %{QUERY_STRING} (GLOBALS|REQUEST)(=|\[|%) [NC]
RewriteRule .* – [F]
</IfModule>
# 5G:[USER AGENTS]
<IfModule mod_setenvif.c>
# SetEnvIfNoCase User-Agent ^$ keep_out
SetEnvIfNoCase User-Agent (binlar|casper|cmsworldmap|comodo|diavol|dotbot|feedfinder|flicky|ia_archiver|jakarta|kmccrew|nutch|planetwork|purebot|pycurl|skygrid|sucker|turnit|vikspider|zmeu) keep_out
<limit GET POST PUT>
Order Allow,Deny
Allow from all
Deny from env=keep_out
</limit>
</IfModule>
# 5G:[REQUEST STRINGS]
<IfModule mod_alias.c>
RedirectMatch 403 (https?|ftp|php)\://
RedirectMatch 403 /(https?|ima|ucp)/
RedirectMatch 403 /(Permanent|Better)$
RedirectMatch 403 (\=\\\’|\=\\%27|/\\\’/?|\)\.css\()$
RedirectMatch 403 (\,|\)\+|/\,/|\{0\}|\(/\(|\.\.\.|\+\+\+|\||\\\”\\\”)
RedirectMatch 403 \.(cgi|asp|aspx|cfg|dll|exe|jsp|mdb|sql|ini|rar)$
RedirectMatch 403 /(contac|fpw|install|pingserver|register)\.php$
RedirectMatch 403 (base64|crossdomain|localhost|wwwroot|e107\_)
RedirectMatch 403 (eval\(|\_vti\_|\(null\)|echo.*kae|config\.xml)
RedirectMatch 403 \.well\-known/host\-meta
RedirectMatch 403 /function\.array\-rand
RedirectMatch 403 \)\;\$\(this\)\.html\(
RedirectMatch 403 proc/self/environ
RedirectMatch 403 msnbot\.htm\)\.\_
RedirectMatch 403 /ref\.outcontrol
RedirectMatch 403 com\_cropimage
RedirectMatch 403 indonesia\.htm
RedirectMatch 403 \{\$itemURL\}
RedirectMatch 403 function\(\)
RedirectMatch 403 labels\.rdf
RedirectMatch 403 /playing.php
RedirectMatch 403 muieblackcat
</IfModule>
# 5G:[REQUEST METHOD]
<ifModule mod_rewrite.c>
RewriteCond %{REQUEST_METHOD} ^(TRACE|TRACK)
RewriteRule .* – [F]
</IfModule>
#AIOWPS_FIVE_G_BLACKLIST_END
#AIOWPS_ENABLE_BRUTE_FORCE_PREVENTION_START
RewriteEngine On
RewriteCond %{REQUEST_URI} (wp-admin|wp-login)
RewriteCond %{REQUEST_URI} !(wp-admin/admin-ajax.php)
RewriteCond %{HTTP_COOKIE} !7bxXr589= [NC]
RewriteCond %{HTTP_COOKIE} !aiowps_cookie_test_xw9llhxsiz= [NC]
RewriteRule .* https://en.wikipedia.org/wiki/Anonymous_%28group%29 [L]
#AIOWPS_ENABLE_BRUTE_FORCE_PREVENTION_END
#AIOWPS_BLOCK_SPAMBOTS_START
<IfModule mod_rewrite.c>
RewriteCond %{REQUEST_METHOD} POST
RewriteCond %{REQUEST_URI} ^(.*)?wp-comments-post\.php(.*)$
RewriteCond %{HTTP_REFERER} !^http(s)?://cumbuco\.net [NC,OR]
RewriteCond %{HTTP_USER_AGENT} ^$
RewriteRule .* https://127.0.0.1 [L]
</IfModule>
#AIOWPS_BLOCK_SPAMBOTS_END
#AIOWPS_LOGIN_WHITELIST_START
<FilesMatch “^(wp-login\.php)”>
Order Allow,Deny
Allow from cumbuco.net
Allow from 181.224.135.99
Allow from 94.191.184.195
</FilesMatch>
#AIOWPS_LOGIN_WHITELIST_END
#AIOWPS_PREVENT_IMAGE_HOTLINKS_START
<IfModule mod_rewrite.c>
RewriteEngine on
RewriteCond %{HTTP_REFERER} !^$
RewriteCond %{REQUEST_FILENAME} -f
RewriteCond %{REQUEST_FILENAME} \.(gif|jpe?g?|png)$ [NC]
RewriteCond %{HTTP_REFERER} !^http(s)?://cumbuco\.net [NC]
RewriteRule \.(gif|jpe?g?|png)$ – [F,NC,L]
</IfModule>
#AIOWPS_PREVENT_IMAGE_HOTLINKS_END
# END All In One WP Security
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
# compress text, html, javascript, css, xml:
<IfModule mod_deflate.c>
AddOutputFilterByType DEFLATE text/plain
AddOutputFilterByType DEFLATE text/html
AddOutputFilterByType DEFLATE text/xml
AddOutputFilterByType DEFLATE text/css
AddOutputFilterByType DEFLATE application/xml
AddOutputFilterByType DEFLATE application/xhtml+xml
AddOutputFilterByType DEFLATE application/rss+xml
AddOutputFilterByType DEFLATE application/javascript
AddOutputFilterByType DEFLATE application/x-javascript
AddType x-font/otf .otf
AddType x-font/ttf .ttf
AddType x-font/eot .eot
AddType x-font/woff .woff
AddType image/x-icon .ico
AddType image/png .png
</IfModule>
## EXPIRES CACHING ##
<IfModule mod_expires.c>
ExpiresActive On
ExpiresByType image/jpg “access 1 year”
ExpiresByType image/jpeg “access 1 year”
ExpiresByType image/gif “access 1 year”
ExpiresByType image/png “access 1 year”
ExpiresByType text/css “access 1 month”
ExpiresByType application/pdf “access 1 month”
ExpiresByType text/x-javascript “access 1 month”
ExpiresByType application/x-shockwave-flash “access 1 month”
ExpiresByType image/x-icon “access 1 year”
</IfModule>
## EXPIRES CACHING ##
https://www.ads-software.com/plugins/all-in-one-wp-security-and-firewall/
]]>The following is the directory listing for the data directory for WP Google Maps:
drwxrwsr-x 2 apache apache 4096 Jul 18 10:37 wp-google-maps
As you can see, it’s writable by “apache”, yet the plug-in complains, “File permissions:2775 – The plugin does not have write access to this folder. Please CHMOD this folder to 755 or 777, or change the location”.
I’ve seen other posts which suggest CHMODing to 777, but this is an insecure cop-out. Is WP Google Maps actually trying to write and failing, or is it just reading the permissions and not smart enough to realise it can actually write to the directory?
Thanks in advance.
Craig
https://www.ads-software.com/plugins/wp-google-maps/
]]>I am working with a client who’s security is above and beyond the normal set-up.
I just attempted to install WP and kept getting into issues with permission settings on directories and the .htaccess file on the root.
Is there anything with my “requirements” I am providing to the ultra-tight IT department that should be removed?
Anything you recommend I add in order to have a fully supportive environment for the WP install? (We are running multi-site.)
And, yes, I already stepped of on the wrong foot with IT. (long story)
TIA,
Greg
Server Requirements for WordPress
Server requirements
? WordPress server requirements for Version 3.2:
o PHP version 5.2.4 or greater
o MySQL version 5.0.15 or greater
o Apache mod_rewrite module (for clean URIs known as Permalinks)
It is also essential that the server allows remote connections, for many of the WordPress features to work. If outgoing HTTP connections are blocked, many parts of the WordPress will not function.
We need a user account that allows us to “read”, “write” and “execute” on all files within the website’s root. We also need an account with which we can change permissions on all directories and files created within the WP set-up.
One of WordPress’ functions is the ability to update and install new plug-ins. These are installed via zipped folders that WP unpacks and installs properly – changing the Db as needed as well.
]]>So I’ve recently moved the files of this site to the live domain and I can do everything but upload media. I have tried changing permissions to 777, checked the options folder in my database for the wrong directory and even tried to uncheck the option to organise files into month and year folders but have had no luck. At first the upload progress bar didn’t move and now it is loading the whole way through and then showing this error:
Unable to create directory wp-content/uploads/2013/06. Is its parent directory writable by the server?
I have no idea what else to do and this is driving me nuts!
I have had to include the permalinks code into my .htaccess file to run with %postname% and am wondering if maybe there is something more I need to add to this file?
Thanks
]]>Everything I upload (files&folders) via FTP belongs to owner user1686 and group users. Permissions are 755 for dirs and 644 for files.
When I first time try to upload media files, WP tries to create uploads folder under wp-content and fails. It’s logical because WP scripts run under wwwrun/nobody owner/group.
To solve this, I changed wp-content permissions for 777 temporary, but now uploads folder (and its subfolders/files) belongs to wwwrun/nobody user.
Is there any way to keep every file&folder under FTP users ownership?
(Nice solution for this is the upload of themes and plugins as FTP user from WP script.)
Anyway, which WP directories should be writable/executable by WP script (which at me runs under wwwrun/nobody user)?
It’s strange not to find any info about this on the net…
]]>