Critical error when...
 
Notifications
Clear all

[Solved] Critical error when clicking "Sign Up" button on MemberPress registration page

4 Posts
2 Users
3 Reactions
308 Views
Posts: 8
Topic starter
(@kthoven)
Active Member
Joined: 4 years ago

When users sign up for courses on my site, they are automatically assigned a "bbp_participant" role, which is the criteria for MemberPress to allow them access to my site's WpForo forums. When WpForo was updated to version 2.2.4 yesterday (Nov. 22, 2023), suddenly when users tried to sign up for new courses through MemberPress, they were given a WordPress critical error message. When I disabled WpForo, the users were then able to sign up for courses again. Please let me know how we might go about fixing this issue. Many thanks!

3 Replies
Posts: 8
Topic starter
(@kthoven)
Active Member
Joined: 4 years ago

Here are the error logs from today (Nov. 23, 2023). I've also attached yesterday's logs to give you more information.

[Thu Nov 23 06:01:03.811251 2023] [autoindex:error] [pid 1185:tid 140300297094912] [client 194.169.175.92:58000] AH01276: Cannot serve directory /home/virtual/site212/fst/var/www/html/wp-content/uploads/: No matching DirectoryIndex (index.php,index.htm,index.html,default.htm,default.html,lithium.php) found, and server-generated directory index forbidden by Options directive
[Thu Nov 23 06:01:10.488266 2023] [authz_core:error] [pid 31919:tid 140300229953280] [client 194.169.175.92:60568] AH01630: client denied by server configuration: /home/virtual/site212/fst/var/www/html/.well-known
[Thu Nov 23 06:07:01.577568 2023] [authz_core:error] [pid 31968:tid 140300204775168] [client 66.249.89.134:49312] AH01630: client denied by server configuration: /home/virtual/site212/fst/var/www/html/.well-known
[Thu Nov 23 08:11:10.320591 2023] [authz_core:error] [pid 31757:tid 140300154418944] [client 66.249.93.41:65317] AH01630: client denied by server configuration: /home/virtual/site212/fst/var/www/html/.well-known
[Thu Nov 23 09:07:26.257378 2023] [authz_core:error] [pid 31853:tid 140300280309504] [client 94.156.69.36:60391] AH01630: client denied by server configuration: /home/virtual/site212/fst/var/www/html/.xas.php, referer: www.google.com
[Thu Nov 23 09:07:35.813510 2023] [authz_core:error] [pid 31757:tid 140300213167872] [client 94.156.69.36:58407] AH01630: client denied by server configuration: /home/virtual/site212/fst/var/www/html/.xas.php, referer: www.google.com
[Thu Nov 23 09:13:02.317917 2023] [authz_core:error] [pid 31853:tid 140300162811648] [client 66.249.93.32:61064] AH01630: client denied by server configuration: /home/virtual/site212/fst/var/www/html/.well-known
[Thu Nov 23 11:18:14.102181 2023] [autoindex:error] [pid 31919:tid 140300280309504] [client 194.169.175.92:61601] AH01276: Cannot serve directory /home/virtual/site212/fst/var/www/html/wp-content/uploads/: No matching DirectoryIndex (index.php,index.htm,index.html,default.htm,default.html,lithium.php) found, and server-generated directory index forbidden by Options directive
[Thu Nov 23 11:18:18.332062 2023] [authz_core:error] [pid 31919:tid 140300146026240] [client 194.169.175.92:54560] AH01630: client denied by server configuration: /home/virtual/site212/fst/var/www/html/.well-known
[Thu Nov 23 12:15:05.061520 2023] [authz_core:error] [pid 31853:tid 140300204775168] [client 45.158.77.134:63960] AH01630: client denied by server configuration: /home/virtual/site212/fst/var/www/html/.env
[Thu Nov 23 12:41:40.731446 2023] [authz_core:error] [pid 1074:tid 140300196382464] [client 37.221.92.68:56545] AH01630: client denied by server configuration: /home/virtual/site212/fst/var/www/html/.tmb
[Thu Nov 23 12:41:40.961826 2023] [authz_core:error] [pid 1074:tid 140300171204352] [client 37.221.92.68:56545] AH01630: client denied by server configuration: /home/virtual/site212/fst/var/www/html/.well-known

 

Robert
Posts: 10549
Admin
(@robert)
Support Team
Joined: 8 years ago

@kthoven,

The error logs has nothing to do with wpForo. Also the bbp_participant role is not wpForo role, if you don't use wpForo please inform me.

Otherwise you should update wpForo to 2.2.5 version. Lots of issues and errors are fixed in this version.

Posts: 8
Topic starter
(@kthoven)
Active Member
Joined: 4 years ago

Hi Robert,

Ah, updating to version 2.2.5 (which seems to have just come out today) did the trick! I still have no idea what caused the issue exactly, but it seems you guys fixed it with this latest release. Thank you for the very quick and helpful response, Robert. Very much appreciated!