Project

General

Profile

Actions

Defect #9836

closed

403 when trying to view issues

Added by Kaspar Fischer over 13 years ago. Updated over 13 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:

100%

Estimated time:
Resolution:
Invalid
Affected version:

Description

Dear all,

I have a fresh installation of Redmine,

Redmine 1.2.2.stable (MySQL)
Default administrator account changed    (ok)
Attachments directory writable     (ok)
Plugin assets directory writable (ok)
RMagick available (optional) (no)

and am trying to access the URL https://mydomain.com/issues (I am pointed to this URL by the "View all issues" link on the Projects page). This results in a "You are not authorized to access this page." error message and the following in the log file:

Processing IssuesController#index (for MyPI at 2011-12-18 12:06:27) [GET]
  Parameters: {"action"=>"index", "controller"=>"issues"}
Rendering template within layouts/base
Rendering common/error (403)
Filter chain halted as [:authorize] rendered_or_redirected.
Completed in 76ms (View: 74, DB: 0) | 403 Forbidden [https://mydomain.com/issues]

I am logged in as administrator.

Does anybody have any idea what the problem might be?

Thanks,
Kaspar

Actions #1

Updated by Etienne Massip over 13 years ago

Maybe you have no public projects and administrator user does is not a member of any project or is member with a role that don't have the 'View issues' permission?

Actions #2

Updated by Kaspar Fischer over 13 years ago

Etienne Massip wrote:

Maybe you have no public projects and administrator user does is not a member of any project or is member with a role that don't have the 'View issues' permission?

Etienne, thanks for your answer and the tips. My project is public and the administrator is a member (Manager, Developer, and Reporter) of the project. I verified that all roles have the 'View Issues' permission. - No luck.

What helped was reinstalling Redmine.

Thanks anyway!

Actions #3

Updated by Kaspar Fischer over 13 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100
Actions #4

Updated by Etienne Massip over 13 years ago

  • Status changed from Resolved to Closed
  • Resolution set to Invalid
Actions

Also available in: Atom PDF