Thomas@iThemes

Actually, hosting bandwidth is the capacity of the connection at any given time. You can read more about hosting bandwidth here:
https://www.betterhostreview.com/what-is-web-hosting-bandwidth.html

But like previously mentioned, there may be more to it with your hosting provider. So contacting them is usually the best route as they have complete access to your server and might be able to determine if something is not right.

• This reply was modified 5 years, 6 months ago by Andrew Nevins.

You might want to also check the time at which the memory error occurred as that may reveal additional information on what might be happening and other options that you may need to take in order to resolve the issue. Especially if the site is running into that memory error during database queries, etc.

For example, the site could be hitting that memory issue if a plugin/theme is doing a database dump, for backup purposes, etc. And if so, could indicate an issue with the server configuration. Especially if the server is using MariaDB and PHP 7.x+ and doesn’t have it patched (set up correctly) for that configuration.

• This reply was modified 5 years, 6 months ago by Andrew Nevins.

I know this ticket is over two months old (and resolved), but if anyone else comes across this thread and gets that message from BackupBuddy, it means they are using a very, very old version of BackupBuddy and that they’ll need to update BackupBuddy to the latest version.

• This reply was modified 5 years, 6 months ago by Andrew Nevins.

Have you tried another browser? As the home page looks fine to me.

Though my browser’s web developer tools are reporting a 404 for this CSS file:
https://cdn-5d32bce3f911c80ef4a25649.closte.com/wp-content/plugins/soliloquy-lightbox/themes/style.css

But everything else is reporting 200’s and 304’s. So if you’re still experiencing issues, it might have something to do with the CDN your site is using.

• This reply was modified 5 years, 6 months ago by Andrew Nevins.

Have you tried Simple Press:
https://simple-press.com/

Though I’m not sure exactly what you’re wanting to achieve. As Simple Press is a Forum plugin (like bbPress), while it seems like you’re just wanting a more robust commenting system.

If the later is what you’re seeking, please see the link below:
https://www.wpbeginner.com/wp-tutorials/how-to-add-bbpress-forum-wordpress-posts-comments/

• This reply was modified 5 years, 6 months ago by Andrew Nevins.

Not sure if this helps, but when I tried to look up that domain to see where it was being hosted (to see if that would help provide any clues on what’s happening), it reports an issue with SSL. So you may want to follow up on that as well as it’s getting a 500 response error:
https://whois.domaintools.com/worldbicyclerelief.org

• This reply was modified 5 years, 6 months ago by Andrew Nevins.

Okay, I had a bit of time to test this today on one of my test sites. And this is what worked.

I created a directory in my /wp-content/uploads/ directory named /private/

And I created an .xls file named test.xls and uploaded it to that /private/ directory.

I also create an .htaccess file with the following contents:

# BEGIN file lock-downs
<ifModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{SCRIPT_FILENAME} .+\.xls [NC]  
RewriteCond %{HTTP_COOKIE} !wordpress_logged_in_  
RewriteRule ^ - [F]
</ifModule>
# END file lock-downs

And I also placed it in the /private/ directory along with the test.xls file.

Since I was already logged into this WordPress site, I went directly to the test.xls file in that directory:
https://example.com/wp-content/uploads/private/test.xls

And it let me download the file.

I then opened up a new private window (incognito in Google Chrome – or you could just try to open it up in a new browser where you haven’t logged into the site). And tried again, but this time it presented me with a 403 Forbidden page. So the above worked as expected on my test site.

If that presents a problem with your site, it’s possible there is an issue/conflict somewhere else. So you might try removing the ifModules as they are just there for portability. The ifModules just tell the server if that module is not activated or doesn’t exist, please die silently.

# BEGIN file lock-downs
RewriteEngine On
RewriteCond %{SCRIPT_FILENAME} .+\.xls [NC]  
RewriteCond %{HTTP_COOKIE} !wordpress_logged_in_  
RewriteRule ^ - [F]
# END file lock-downs

Also, please remember this separate .htaccess file needs to go in the directory with the files that you are trying to restrict access to.

If your server allows using .htaccess files in directories further from the root, they should override what’s in the root .htaccess file.

Also, I need to mention, you don’t want to do it like this:

RewriteCond %{SCRIPT_FILENAME} /wp-content/uploads/Private/.+\.xls [NC]
RewriteCond %{REQUEST_FILENAME} /wp-content/uploads/Private/.+\.xls [NC]

As that says, this condition AND this condition must be met. You only want to try one or the other condition for this operation and for what you are trying to achieve. I just wasn’t sure which condition might work better.

So your root .htaccess file would like like so:

# BEGIN WordPress
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
# END WordPress

# BEGIN file lock-downs
RewriteCond %{SCRIPT_FILENAME} /wp-content/uploads/Private/.+\.xls [NC]  
RewriteCond %{HTTP_COOKIE} !wordpress_logged_in_  
RewriteRule ^ - [F]
# END file lock-downs

And I placed that in my site for my root .htaccess file and it worked as well. Please note, when trying to access the file directly in your browser, it makes a difference if the ‘p’ in /Private/ is lower case or upper case, so please make sure it’s how you have it set up when placing the URL in a browser. (I always just make sure that all letters in my directory names are always lower case so that I don’t have to worry about that.)

• This reply was modified 5 years, 6 months ago by Andrew Nevins.

You could use something like the following in the site’s root .htaccess file (one created by WordPress):

# BEGIN file lock-downs
<ifModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{SCRIPT_FILENAME} /wp-content/uploads/Private/.+\.xls [NC]  
RewriteCond %{HTTP_COOKIE} !wordpress_logged_in_  
RewriteRule ^ - [F]
</ifModule>
# END file lock-downs

What it does is require a visitor to be logged into the site in order to be able to access that directory. Of course it can be bypassed if someone knows you’re doing that and they know how to spoof a cookie (which isn’t hard to do).

I haven’t actually tested that, so if that doesn’t work, you might try changing the “SCRIPT_FILENAME” to “REQUEST_FILENAME”

So now it looks like:

# BEGIN file lock-downs
<ifModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} /wp-content/uploads/Private/.+\.xls [NC]  
RewriteCond %{HTTP_COOKIE} !wordpress_logged_in_  
RewriteRule ^ - [F]
</ifModule>
# END file lock-downs

But that may help get you down the route you’re trying to achieve. You could actually use it in combination with other directives and not just cookies.

I need to mention that I tried to provide something within .htaccess that might do what you are trying to achieve with just .htaccess. As someone else mentioned, it would be better to do a combination check with .htaccess and a PHP script as that would be more secure (harder to spoof). But until then, that .htaccess snippet, might get you started.

• This reply was modified 5 years, 6 months ago by Andrew Nevins.

I know this thread is old, but if anyone else encounters a similar issue with BackupBuddy and exceeding the max execution time, BackupBuddy has an option to try and help with that located here in the plugin’s settings:
BackupBuddy -> Settings -> Advanced Settings/Troubleshooting -> Basic Operation -> Attempt to override PHP max execution time ->
Just check that, then save settings and try again.

However most hosts don’t allow a PHP script to override server settings like that. So you may wish to contact your host so you can adjust/increase it at the server level.
https://ithemes.com/custom_php_ini/

• This reply was modified 5 years, 6 months ago by Andrew Nevins.