The following warnings occurred:
Warning [2] Undefined variable $unreadreports - Line: 26 - File: global.php(961) : eval()'d code PHP 8.2.25 (Linux)
File Line Function
/global.php(961) : eval()'d code 26 errorHandler->error
/global.php 961 eval
/showthread.php 28 require_once





× This forum is read only. As of July 23, 2019, the UserSpice forums have been closed. To receive support, please join our Discord by clicking here. Thank you!

  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Forbidden after update from 4.2 -> 4.3.2
#1
Hi,

After I updated userspice I get:
Forbidden

You don't have permission to access /ota/dev/am/users/admin_verify.php?actual_link=http://mysite/ota/dev/am/users/admin_permissions.php&page=users/admin_permissions.php on this server.

Because I use SSL I altered the url into https, but it results in the same issue.

Does anyone have an idea what is wrong?

Kind regards,
nessinits
  Reply
#2
Just to confirm you are getting 403 Forbidden Codes?

You'll need to check your file permissions. I run mine as 644 I think.
  Reply
#3
That doesn't seem the issue. All my files are 644.
  Reply
#4
Are all of your files giving you 403 Errors?

Is there anything in the error logs? I wonder if one specific file that is required (init or a helper or something) has bad permissions and it is causing the error.

It could also be a file ownership problem although that should produce a 500 error instead.
  Reply
#5
The issue is with all admin pages. All my regular projectpages are accessible.

I think it's an admin-rights issue, but I don't know where to start looking ...
  Reply
#6
Backup your DB and then run this query:
UPDATE pages SET re_auth = 0 WHERE re_auth=1;

Let me know if that fixes the issue.
  Reply
#7
That solved it. What's wrong? What should I do now?
  Reply
#8
That to me would indicate an issue with admin_verify.php. Check the permissions on this file. Also make sure it is in your DB (pages), users/admin_verify.php, should be private with a re_auth value of 0, and then have a corresponding page_permission_matches. Let me know.
  Reply
#9
Permissions are correct. DB-pages users/admin_verify.php is private and re_auth is 0.

I've added manually users/admin_verify.php to pages and given permission to my admin group. The result stays the same.
  Reply
#10
As an addition ... When I make the actual link blank it returns the admin_verify.php page.
  Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)