Thanks a lot for your help and input. The issue is fixed, here was their reply:

Thank you for the update.

I was able to resolve the issue by updating the path in your .user.ini file as well and the notice is no longer present.

I would kindly ask you to verify the results on your side as well.

Could someone give me a dumbed-down explanation of what they fixed? I'm learning as I go, every time a website breaks down I learn a bit more 

@robert

I disabled wpForo so that I could get into the admin panel, and my backup plugins are not working correctly. UpDraft plus just completed a backup no problem on Saturday, but now it's hitting a hiccup. And Duplicator can't finish at all. 

STRANGELY, some of my users are still commenting and using the forum. I'm going to have to assume it's because they never got logged out!

This is what I'm sending SiteGround:

Hello,

I do not think that the issue is with the plugin - it looks like something changed on the server side which is impacting the website.

I say this because:
1. No changes were made to the website or plugins for weeks before it went down, and I didn't personally make any changes to the server recently either.
2. After disabling the wpForo plugin, I got into the admin panel and attempted to do backups of the website with Updraft Plus and Duplicator. These two plugins have been making weekly backups no problem for months, but now they're hitting errors when trying to do the backup. Duplicator says:
Host Build Interrupt
This server cannot complete the build due to host setup constraints.
To get past this hosts limitation consider the options below by clicking each section.

It never had this problem before with my backup plugins. Just this Saturday Updraft completed an automatic backup with no hiccups - so something likely changed Sunday/Monday

I've attached a debug log, and also put up a notice on the website that the forum may be down - so if you need to temporarily disable wpforo by renaming the plugin folder please go ahead. It'll get you to the admin console at least. 

Please let me know if there is anything I can do to aid you.

 

<!-- This website is like a Rocket, isn't it?

should appear at the very end of the page. And in your case it is not. There are some scripts AFTER the signature (meaning the end of the cached page). That is strange, unless wp-rocket works like that, mixing things (i doubt it).

@anonymous20

This is awkward, but could you send me that debug log if you still have it on file? Or let me know how to get it?

I'm trying to convince siteground that something happened on the server end and needs correction. And maybe the log will help them figure it out

https://the-great-work.org/wp-content/debug.log

log files, .ht*** files and other files should be automatically blocked (403) not by you but from the hosting setup. Unless you manage your server, then it is your fault.

As for your support guys whereever you host, they have no idea what they are talking about. Sorry, but that is the truth.

Saying for example that wpForo version is not compatible/updated and things like that.

Ask for your problem to be escalated to a proper support team.

You've updated server PHP and the session folder is changed or the folder permission is not 755 / 777. So wpForo can't initiate PHP session. This is not wpForo Issue. This is a BIG problem of your server PHP and session directory. Please contact to your hosting support and ask them to fix PHP Session issue as soon as possible. There is no any issue from wpForo and there is no any solution from wpForo side.

Similar situation in web: https://forums.cpanel.net/threads/cpanel-whm-64-php-session-path-errors.596863/

I just checked folder permissions, they are 755

@robert did the response from siteground support tell you anything?

@Anonymous20

I've knocked out pretty much every other plugin (that was active) one by one and the issues hasn't gone away

@anonymous20

Changed to 644, error codes didn't change. It's the same 7 on the login, same 2 across the website

EDIT: NVM I figured out how to disable. Rename folder

It is the same error as here:

https://wpforo.com/community/how-to-and-troubleshooting-2/warning-message/

and also a LOT of same problem if you search the internet. Related either to hosting (tmp path) or a plugin.

Try to disable one by one your plugins. If everything is disabled (except wpForo) and you didn't find the cause, then i guess it is a hosting problem, or a Cpanel problem.

Changed to 644, error codes didn't change. It's the same 7 on the login, same 2 across the website

EDIT: NVM I figured out how to disable. Rename folder

Posted by: @anonymous20

@tgw Can you see/check what is the FILE permission of wp-config.php ? Is it 644 or 600 ?

 

It's 600. Pic attached

Should I delete the rocketcache folder and see if that fixes it? I can delete all caching plugings to see if it helps. I do have a website backup from this weekend just incase.

To  be honest I knew that an error code was popping up for a few months now, but it used to go away with a page refresh and the website ran fine. I don't know what happened suddenly today to cause it to become a major issue

Can you make the wp-config.php 644 and see if the error is gone ?

And try things ONE BY ONE. Not all at once. No need to delete Rocket cache, just disable it.

@tgw Can you see/check what is the FILE permission of wp-config.php ? Is it 644 or 600 ?

@anonymous20

It's 600. Pic attached. I have no idea what 600 means, I'm in over my head when it comes to server stuff

Posted by: @anonymous20

Also, i found your error (not exactly but most of it) in Wordpress.org, in two different caching plugins forums.

I see you run Rocket cache ? Could your problems be related to Rocket cache ?

Should I delete the rocketcache folder and see if that fixes it? I can delete all caching plugings to see if it helps. I do have a website backup from this weekend just incase.

 I knew that an error code was popping up for a few months now, but it used to go away with a page refresh and only showed up very rarely. And the website ran fine. I don't know what happened today to cause it to become a major issue