Hello all,
I've been using chat.sr.ht for a while now and taking advantage of the
web client. As of today (specifically, sometime in the last 12 hours
prior to 2022-03-21 04:30Z), the web client is prompting for a server
connection, rather than connecting to the bouncer, which has been the
normal behavior until now. Attempting to make a connection via this
form simply hangs.
The form prompts the following
# Connect to IRC
Nickname: 
Password:
[ ]Remember me
Advanced options
Server URL: 
Username: 
Real name: 
Server password: 
(Connect)
I am authenticated to sr.ht. If I clear browser state and navigate to
chat.sr.ht, I'm prompted with the regular sr.ht login flow. The form
prompt to connect to IRC is gated behind successful authentication.
I have replicated across two browsers. I'm happy to troubleshoot
further, but do not quite know where to start.
Thanks!
-gb
On Mon 21 Mar 2022, Greg B wrote:
> > I've been using chat.sr.ht for a while now and taking advantage of the> web client. As of today (specifically, sometime in the last 12 hours> prior to 2022-03-21 04:30Z), the web client is prompting for a server> connection, rather than connecting to the bouncer, which has been the> normal behavior until now. Attempting to make a connection via this> form simply hangs.> > The form prompts the following> > # Connect to IRC> Nickname: > Password:> [ ]Remember me> > Advanced options> Server URL: > Username: > Real name: > Server password: > > (Connect)> > > I am authenticated to sr.ht. If I clear browser state and navigate to> chat.sr.ht, I'm prompted with the regular sr.ht login flow. The form> prompt to connect to IRC is gated behind successful authentication.> > I have replicated across two browsers. I'm happy to troubleshoot> further, but do not quite know where to start.
I am unable to log in with my “native” IRC client using my token generated back in December and https://meta.sr.ht/oauth2 is returning “500 Internal Error”. It looks to me like this goes deeper than just the IRC web client at this point, but I am sure staff will get around to it once morning hits Europe in a few hours.
I've also been having this problem. trying to connect through senpai, it returns:
-- Error (code 904): Registration failed: Invalid sr.ht OAuth2 access token
-- Error (code ACCOUNT_REQUIRED): Authentication required
-- Error (code ACCOUNT_REQUIRED): Authentication required
I went to the OAuth2 dashboard[1] to figure out what happened, but that
isn't working either -- it returns a 500 error.
[1] https://meta.sr.ht/oauth2
~sfr
Confirmed working on my end. Thanks for the quick response!
-gb
On Mon, Mar 21, 2022, at 04:15, Drew DeVault wrote:
> Should be fixed now. Sorry for the disruption.