Solved: 2 Weeks, 5 Days, 9 Hours ago 403 Error When Posting New Threads
#1
Solved: 2 Weeks, 5 Days, 9 Hours ago
Users trying to post new threads through a browser are receiving a 403 Forbidden message.

They can reply to existing threads.
New threads can be created through the Tapatalk app.

The problem is not browser-specific (we have tested in Brave, Chrome, and Edge).
We have made no updates.

https://amblesideonline.org/forum/index.php

Test account: testmybb
Test password: AOmybb

When trying to set up this test account, I was able to create the account, but when I tried to set it to Moderated status, I received the same 403 Forbidden error when I went to save the settings.

We are running 1.8.36.

   

We cannot edit existing threads either.
Reply
#2
Solved: 2 Weeks, 5 Days, 9 Hours ago
PHP is having problems today, globally. I bet that's what is causing this problem.
Reply
#3
Solved: 2 Weeks, 5 Days, 9 Hours ago
Are you running a version that is patched for PHP2Shell? If not, some server admin might have kludged something up for your protection. The vulnerability has been fixed in PHP versions 8.2.35, 8.3.36, 8.4.27, and 8.5.12.
Reply
#4
Solved: 2 Weeks, 5 Days, 9 Hours ago
Thank you! I will check on that.
Reply
#5
Solved: 2 Weeks, 5 Days, 9 Hours ago
Our forum installation will not work with a newer version of PHP. We tried updating our PHP, and that crashed everything.
Reply
#6
Solved: 2 Weeks, 5 Days, 9 Hours ago
What version of PHP are you running? 1.8.36 is fairly new, so I would expect it to work with any of those. Some warnings may be generated, but you can (and should) set warnings to be logged to a file rather than displayed to users.

So I would assume it is some extension that doesn't run. ?? If you look in your server log, you should find an error message or two that tells you where the problematic file is.
Reply
#7
Solved: 2 Weeks, 5 Days, 9 Hours ago
We're upgrading our MyBB to the newest version.

We have been trying to find the server log. We're not really usually in the innards like this, as you can probably tell.
Reply
#8
Solved: 2 Weeks, 5 Days, 9 Hours ago
Another way to narrow down which plug-in is to deactivate them all (on the old PHP version) and add them back one at a time (on the new PHP version).

The server log may be somewhere in your admin panel, assuming you have one of those.
Reply
#9
Solved: 2 Weeks, 5 Days, 9 Hours ago
I think we're making progress.  We were able to upgrade the forum software, and now we were able to upgrade the PHP without everything breaking.

We're getting these warnings at the top of the screen now though.

   

We did disable all of our plugins.

Even with the plugins disabled, we still don't have PHP working in the forum software.
Reply
#10
Solved: 2 Weeks, 5 Days, 9 Hours ago
You're on PHP 8.2.34 which is a vulnerable version. You want to be on 8.2.35.

The errors can be kept off screen. Go to ACP -> Configuration -> Server and Optimization and set Error Type Medium to Hide Errors and Warnings. You probably should also set Error Logging Medium to Log Errors, and set Error Logging Location to someplace handy. It's worth looking at those warnings - those are not warnings that appear in my logs. You may have some outdated templates.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)