Cant Login to admin page after setup

[AndrewHuddleston]

Go through the setup, set the website, admin username and password, page name. All successful. Go to enter the admin username and password to login to the admin page. "Incorrect Credentials"

Ran through the setup 3 times same result and its not the wrong password. Also tried chrome and safari same result.

Setup:

• Docker compose
• Ubuntu

 statusnook:
    ports:
      - 8000:8000
    volumes:
      - /mnt/configs/statusnook:/app/statusnook-data
    restart: always
    container_name: statusnook
    image: goksan/statusnook

[goksan]

Hi @AndrewHuddleston, thanks for reaching out about this issue.

I haven't come across any similar reports yet, so it looks like we might need to do a bit of troubleshooting to figure this out.

Here are a couple of initial thoughts:

• When you're setting up Statusnook, you mentioned going to log in. Are you signing out first? Normally, you should already be logged in after setting up
• Note that the username is case-sensitive. Could you please double-check that you're entering it in exactly the same way each time?

Could you try the following:

• While creating your account, please keep the network tab open in your browser to capture the request body.
• Do the same when you attempt to log in

This will help us confirm if the username and password are exactly the same in both instances.

[chw-webops]

Same issue. Is there a limit on the number of characters allowed in the password input?

Disregard. Works for me using HTTPS.

[goksan]

Same issue. Is there a limit on the number of characters allowed in the password input?

Disregard. Works for me using HTTPS.

Hey @chw-webops, glad to hear you got it working.

There's no limit to the field on the front end, however there is a 72 character password limit on the server but that's not relevant (you'd be blocked at account creation).

It is important to use Statusnook over HTTPS, you would run into issues over HTTP (secure cookies etc). As far as I can tell so far, none of this seems connected to the "Incorrect Credentials" error.

I'd still be interested in the following regarding your case:

• Can you confirm you were also seeing the "Incorrect Credentials" error
• Are you using Docker too?
• Is this a local configuration?
• Do you have any proxying setup?

[chw-webops]

@goksan No visible error on the frontend. Looked like a redirect, which makes sense. I'm running as a Docker container behind a Nginx reverse proxy which handles the SSL.

[goksan]

@goksan No visible error on the frontend. Looked like a redirect, which makes sense. I'm running as a Docker container behind a Nginx reverse proxy which handles the SSL.

Thanks @chw-webops that's good to know.

I was able to replicate your case, there is confusing behaviour when entering a correct password over HTTP. You don't actually get logged in due to the cookie being Secure but the page looks the same minus the form getting cleared. I don't test release builds over HTTP so I hadn't encountered this before now.

l might simply address this by replacing the login form with a disclaimer over HTTP. I don't think it's unreasonable to not support HTTP outside of development.

It seems like @AndrewHuddleston's report is entirely different, I still haven't been able to replicate "Incorrect Credentials"
with valid credentials over HTTP or HTTPS.

[goksan]

Hi @AndrewHuddleston, thanks for reaching out about this issue.

I haven't come across any similar reports yet, so it looks like we might need to do a bit of troubleshooting to figure this out.

Here are a couple of initial thoughts:

* When you're setting up Statusnook, you mentioned going to log in. Are you signing out first? Normally, you should already be logged in after setting up

* Note that the username is case-sensitive. Could you please double-check that you're entering it in exactly the same way each time?

Could you try the following:

* While creating your account, please keep the network tab open in your browser to capture the request body.

* Do the same when you attempt to log in

This will help us confirm if the username and password are exactly the same in both instances.

To add to this then @AndrewHuddleston, could you also share whether you're visiting your Statusnook over HTTP or HTTPS? It sounds like you're visiting over HTTP based on you needing to log in after the set up process.