Create project in Jira, Mostly get a 401 This resource requires WebSudo

[Brian Ballard]

I'm set up as jira administrator, and trying to build out a demo environment to internally sell this as a solution to my team (historically I have administored jira at other companies). However I have successfully created some projects, but 90% of the time I get

" Error creating project, 401This resource requires WebSudo.". Then I try again a minute later and occasionally it works, or I add a different project and it works. ive checked the logs and so far nothing looks obvious.

System details: Windows server 2008, external SQL server 2008 DB, Jira demo install. using AD for authentication only.

[Benjamin Klatt · Accepted solution]

We faced a similar error with the latest Jira 6.0.7. The only thing that worked for us was to trigger a re-index in the Jira System administration.

- Benjamin

[Aleksandr Zabotin]

Thanks, it's work!

[Muhammad Rizwan]

Worked for us

[Philip van Veen]

works as a workaround, but it is really annoying. Re-indexing works for a while but sooner or later the same problem occurs. It seems that jira looses some cookies or whatever which causes jira to revoke your admin rights

[Lorenzo]

Works here too

[laguiz]

Thank you for this one!

[Khayrat Glende]

As @Elvar posted: just relogin is fine.

[Jon Frampton]

Worked for me today!

[Elvar Bjarki Böðvarsson]

This can happen if you have the additional login prompt enabled for config changes (is by default). When you are going to do an action tha requires those rights (websudo) but the login has timed out the interface does not tell you. When trying to take that action without the websudo rights results in this error. Just clicking something to trigger the login and logging in again, and then do what you were originally trying to do will work.

[Nic Brough -Adaptavist-]

I think it's a bit vague. Websudo rights can be lost if you have network problems, or you're doing odd things in the browser, or if the server is experiencing problems, or if the authentication stuff is set up badly.

I suspect more looking at the logs may be needed, along with details about the browser and authentication setup.

[Brian Cummings]

I have the same issue. I recently migrated the database to Postgres, and now, 100% of the time when I try to create projects, I get: Error creating project, 401 This resource requires websudo. JIRA and Postgres are both located on the same system. I can see my existing projects and data, but just can't create a new project. Any ideas why?

Brian

[Nic Brough -Adaptavist-]

I'm afraid it's the same answer. You'll need to do some debugging yourself - look in the logs for errors or mention of websudo, check your installation is done correctly and you haven't missed anything in the setup. Try a different browser and a different machine. Check your network logs.

[Lorenzo]

Hmm interesting thoughts. My atlassian suite is indeed behind a HTTP reversed proxy with SSL on using a self generetad certificate.

[Nic Brough -Adaptavist-]

Sadly, "indexing fixes it" is the wrong answer. I suspect it works because triggering the indexing process goes through something that refreshes or renews your session, and hence keeps the websudo, but as the index has *no* session data in it, the re-index itself is not the answer.

[swapnakumarv]

 re-indexing works...any specific root cause for this?

[Hauke Fuhrmann]

I had this issue with Google Chrome as browser. I did not find a way to get rid of the Websudo error message, although initiating creation of a new project always triggered the additional Admin credential confirmation.

When I changed the browser to firefox, it worked out-of-the-box with no further changes (i.e. no reindexing).

[Lorenzo]

Just had the same shit; I re-indexed and hey, it worked. Thanks Benjamin!

[Leena Agrawal]

I faced similar issue, this is due to session timeout you can logout and login again.

[Li Zhang]

Reindexing works.

[tbuckland]

I reindexed from within Jira admin, and also reindexed the db directly in postgres. After that it worked.

[Ash Ebrahim]

re-index worked for me too

[John Price]

I got this error on 6.1.5 with a fresh test install on Windows. A re-index (of the zero issues and projects!) fixed it. Not the best user experience ... I've been a Jira admin for 8 years and I had no idea what "websudo" meant in the context of Jira, although I know sudo is the Linux command for elevating user privileges.

[Mark]

I reindexed with a Postgre install on Win64 and it worked fine after that.

Start with reindex first.

[Brian Ballard]

Actually to feedback on this. I solved it by creating a new local account with admin rights and removing any association with my original acount and then deleted it. As no other user account I had created seemed to have trouble. I did also trigger a re-index at a later date so this might have work if I had done that before the account add/delete. But for me it was just removing the affected user.

[rafaferreira]

No coments for this yet? I have the same issue here, no news???