Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

An error occurred in the web application: Invalid username or password.



  • An error occurred in the web application: Invalid username or password.

    We recently upgraded to 5.3.21 and when we try to install choco we get the following error and the install script bombs out. We noticed that Anonymous user no longer shows up under Users like it does in our old lab version, we tried setting up a use but get the same error.


  • inedo-engineer

    Hi Jeff,

    Could you please provide a screenshot of what you are referring to with the Anonymous user no longer shows up under Users? Anonymous should be a built-in account and you should be able to add it to any task. Although being a free user, you do not have the ability to have feed level support. In that case, if you set anonymous globally, then all feeds will have anonymous access.

    What version were you using in your lab that worked previously?

    Thanks,
    Rich



  • 5.2 is in the lab. We understand we are limited with the Free version but we need to get it working before we can get approval for purchasing.
    Under users tab in 5.2 Anonymous user shows up, in 5.3 is not listed under user tab, when we test privileges, and choose Anonymous it says: No privileges for the specified context.
    It doesnt matter which Feed we try and under Tasks View & Download Packages Scope: All Feeds, Users and Groups has Anonymous listed.


  • inedo-engineer

    Hi Jeff,

    The anonymous user has been moved to a built-in account in ProGet now, so it will not show up under the Users tab now. But, you should still be able to add Anonymous to tasks on the Tasks tab. I would recommend removing the anonymous permission you had set up on any task previously and re-add them. When you start to type Anonymous, you should see it pop up as an available user to select. Can you try that?

    Thanks,
    Rich



  • We have done that several times and still no luck. We reverted back to 5.3.11 and so far we it appears to be working.


  • inedo-engineer

    Hi @Jeff-West_5638,

    Do you see the error in your Diagnostics Center under Administration? Could you please post that error stack trace here?

    Thanks,
    Rich



  • So downgrading to 5.3.11 that error went away. Here it is.
    An error occurred in the web application: Invalid username or password.
    URL: http://ourserver/endpoints/Chocolatey/content/chocolatey.license.xml
    Referrer: (not set)
    User: (unknown)
    User Agent: Mozilla/5.0 (Windows NT; Windows NT 10.0; en-GB) WindowsPowerShell/5.1.17763.1490
    Stack trace: at Inedo.Web.InedoHttpModule.AuthenticateRequestAsync(HttpApplication app)
    at Inedo.Web.InedoHttpModule.ProcessBegin(Object sender, EventArgs e, AsyncCallback cb, Object extraData)
    at System.Web.HttpApplication.AsyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
    at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)
    at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)


  • inedo-engineer

    That URL is a bit strange, and I wouldn't expect it to work.

    What is /endpoints/Chocolatey/content/chocolatey.license.xml? If you visit in your browser, what happens?



  • I created an account to +1 this issue. We recently upgraded to 5.3.24 and started seeing the same errors.

    Proget: 5.3.24
    Category: Web
    Message: An error occurred in the web application: Invalid username or password.
    Details: URL: https://our-host/nuget/our-org/
    Referrer: (not set)
    User: (unknown)
    User Agent: NuGet Command Line/5.8.1 (Microsoft Windows NT 10.0.19041.0)
    Stack trace: at Inedo.Web.InedoHttpModule.AuthenticateRequestAsync(HttpApplication app)
    at Inedo.Web.InedoHttpModule.ProcessBegin(Object sender, EventArgs e, AsyncCallback cb, Object extraData)
    at System.Web.HttpApplication.AsyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
    at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)
    at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

    The worst part is the errors are not actually 'logged'. They are written to proget's database which only retains the last 1000 entries per category. Extremely hard to debug on our end.


Log in to reply
 

Inedo Website HomeSupport HomeCode of ConductForums GuideDocumentation