I can’t log into the player - but i can log into the profile and forum sections fine. (BTW it is pretty confusing having three separate logins for essentially one site)
The login page giving me problems is this one: Resonate
it will only accept my email address , not my username
when I attempt to log in it says “La patience est une vertu…”
then after a bit says “If you just signed up or changed your password, please try again in a few seconds…”
nothing I do will get me past that point.
my password is quite long, but is purely alphanumeric characters, I’m using the same password on the other sections of the site without problems.
I had earlier changed my password for a shorter one in the player only - is there a character limit that could have been causing the problem? Even so I still wasn’t able to log in until just now.
Password length shouldn’t be an issue unless it were like 70 chars or something. We’re doing regular updates during our migration to our new infrastructure, so it is possible something just got updated or synced while you were waiting.
I had had this problem for some time, over a week. So if there were updates today that might have fixed it but couldn’t have caused it. I will check how it goes over the next few days and report back here if it re-occurs.
I have recently signed up for a listener account and am facing the same problem.
I’ve waited more than a few seconds so I don’t think that’s it
I had previously declined cookies, then accepted them but no change.
The account was created on https://resonate.is and i can sign in fine there.
Details:
The POST request to https://stream.resonate.coop/api/v1/oauth2/password with
I tried resetting my password to only alphanumeric as well. It kind of solved the initial problem, i.e. I am forwarded to the player. However it doesn’t look like I am logged in there, it still says “Log in to listen to full song” at the bottom of the screen.
What would be a good process to establish for this going forward? It seems unfair that this all falls on your shoulders @auggod, and I don’t think we’re currently in a situation (or have capacity really) where we need things like this to be fixed in a shorter timespan than 24 hours (please pitch in if you think differently).
At companies I’ve worked at in the past we have rotations for being “on call”, and we only escalate it up the on call chain after certain conditions have been met. I’m not sure how that combines with a volunteer organization. To me it seems like a lot to expect one person to be able to respond whenever, on their weekend.
I could have received a warning for this server on Sunday afternoon. Ping + Https check was not running on cloudradar.io (we’re using this to track our cloud servers). Last week when making sure certs were up to date, i forgot to reload a specific webserver (nginx). All certs for our domains are not renewed automatically. I still regularly check and also receive emails when a cert is close to expiration date.