Hello, I've been using chat.sr.ht for the past few weeks as part of the closed beta. However, since this morning (apparently coinciding with the announcement of chat.sr.ht going public), I've been unable to connect to the server using a local IRC client (~taiite/senpai). The hosted gamja session at https://chat.sr.ht still appears to work. I have tried on two machines but am unable to connect. I just wanted to check if any of the configuration/URLs/credentials changed when the service went public, or if any existing accounts were deleted, or something? It is possible but unlikely that anything changed locally for me, I'm using the same configuration and senpai build as yesterday, and nmap shows that port 6697 is open (as it should be). Any suggestions would be appreciated. Thanks, Kalyan Sriram
What happens when you try to connect? What do you see?
Are you using the latest senpai commit? It contains a bug fix for SASL authentication.
On Tue Nov 30, 2021 at 12:55 AM PST, Simon Ser wrote: > Are you using the latest senpai commit? It contains a bug fix for SASL > authentication. Thanks for this! That appeared to be the issue. I updated senpai to the latest commit on my laptop and it's connecting now. Will try on my desktop at home later. Sorry for the trouble! Kalyan
It appears as though I'm getting similar issues with senpai when connecting to chat.sr.ht to use the bouncer to access the irc.libera.chat and irc.tilde.chat networks. On Tue Nov 30, 2021 at 12:55 AM PST, Simon Ser wrote: > Are you using the latest senpai commit? It contains a bug fix for SASL > authentication. I'm using what appears to be the most recent available commit (3904c91). Both networks tell me: Error (code 904): Registration failed: SASL authentication failed Above that error, libera.chat also gives me: * SaslServ: <Unknown user on molybdenum.libera.chat (via SASL):user/akspecs> failed to login to akspecs. There has been 1 failed login attempt since your last successful login. The number of failed attempts will vary between how many times I've re-launched senpai, and if I've used the gamja web interface in-between. I don't appear to be having any issues when using gamja on chat.sr.ht Interestingly enough, I was able chat with another user in #senpai through senpai despite those errors. With `senpai -debug', I am able to see: IN -- :chat.sr.ht 903 akspecs :SASL authentication successful Is this something I could ignore? Thanks, akspecs
This error suggests an issue authenticating with LiberaChat SASL, rather than authenticating with chat.sr.ht directly. It seems to be attempting to register as "user/akspecs" rather than "akspecs" as it ought to. Try /msg BouncerServ network update irc.libera.chat -username akspecs
Still getting: Error (code 904): Registration failed: SASL authentication failed On Wed Dec 1, 2021 at 1:09 AM PST, Drew DeVault wrote: > It seems to be attempting to register as "user/akspecs" rather than > "akspecs" as it ought to. user/username is the generic user cloak for LiberaChat . > Try /msg BouncerServ network update irc.libera.chat -username akspecs I tried this, and LiberaChat will accept the auto-forwarded password after running that -- but nothing changes with the failed SASL authentication. In fact, after attempting to update my username and relaunching senpai, the same `<Unkown user on ...libera.chat (via SASL):user/akspecs>' persists as well. : https://libera.chat/guides/cloaks#generic-user-cloaks
On Wednesday, December 1st, 2021 at 10:09, Drew DeVault <firstname.lastname@example.org> wrote: > Try /msg BouncerServ network update irc.libera.chat -username akspecs This "username" is the IRC-level one, not the SASL-level one. To set the SASL username and password, use: /msg BouncerServ sasl set-plain irc.libera.chat akspecs <password>
For future reference: this is fixed with a senpai patch . : https://lists.sr.ht/~taiite/public-inbox/patches/27015