Jump to content

Featured Replies

Posted

The upgrade installed fine; and the community is viewable, however, No users are able to login into the community forums after the upgrade. Users are receiving a blank screen after entering the username and password while logging in. Additionally, the admin console is returning a 400 bad request error.

How can I troubleshoot this?

5 minutes ago, Jeffrey Roberts said:

Additionally, the admin console is returning a 400 bad request error.

The reason for this type of error is typically due to malformed request syntax, invalid request message framing, or deceptive request routing

5 minutes ago, Jeffrey Roberts said:

Users are receiving a blank screen after entering the username and password while logging in.

Can you check your server error log page and see if there are any recent messages logged in there pertaining to this?

What version did you upgrade from btw and what is your php version?

Edited by Miss_B

  • Author

I turned PHP errors on and found that a custom add-on application has an error. I renamed that application so that it couldn't load and I can now login.

The error was "PHP Fatal error:  Class IPS\sparkpost\_SparkPost contains 1 abstract method and must therefore be declared abstract or implement the remaining methods (IPS\_Email::isUsable) in /home/customer/www/ibspatient.org/public_html/community/applications/sparkpost/sources/SparkPost.php on line 0"

I am still receiving a 400 bad request error when trying to access admin and there are no other errors.

My community was current so whatever version was prior to 4.7.20 was running without issues.

I am running PHP 8.1.31

  • Author

I should add that I use Cloudflare to proxy the site. I have tried turning proxy'ing off. The 400 bad request seems to be coming from Cloudflare.

My admin login does have 2FA turned on, but I don't seem to be able to get that far

https://www.ibspatient.org/community/admin/:

Screenshot 2025-01-30 at 10.36.45 AM.png

1 minute ago, Jeffrey Roberts said:

I should add that I use Cloudflare to proxy the site. I have tried turning proxy'ing off. The 400 bad request seems to be coming from Cloudflare.

Can you disable the Cloudfare and see if that will make the error go away?

  • Author

I have tried that. 🙁 No change.

  • Author

Further troubleshooting, the error seems to be caused by this line in admin/index.php as the index.php will be executed up until that line.

\IPS\Dispatcher\Admin::i()->run();

Edited by Jeffrey Roberts

  • Author

I decided to give this some time to see if this was a local server cache issue or a Cloudflare cache issue and apparently it was.

I can access the Admin console again.

Glad to see that it has been sorted out.

Recently Browsing 0

  • No registered users viewing this page.