On 2024-09-27 14:01 Tassilo Horn <tsdh@gnu.org> wrote:
t.h> FWIW, it seems to work normal when connecting with a IRC client.

It turned out that mode +D had been set on my nick upstream.

So chat.sr.ht is working as intended.

Thanks for looking into this, and apologies for the noise.

--
Joseph Koshy | <jkoshy@jkoshy.net> | https://jkoshy.net/

On 2024-09-27 14:01 Tassilo Horn <tsdh@gnu.org> wrote:
t.h> FWIW, it seems to work normal when connecting with a IRC client.

t.h> I've just tried the web interface and get immediate errors like "failed
t.h> to fetch backlock for #somechannel".  But I do see messages that are
t.h> posted just now.

These are the most recent messages that I see via the web interface
for channel #sr.ht:

  --- 22/09/2024 ---
  08:46:52 <ddevault> you'll be billed as soon as the billing cronjob kicks in today
  08:46:56 <ddevault> agreed that it's a confusing message though :)

Greetings,

chat.sr.ht seems to have stopped displaying incoming channel messages.  The most recent messages that I see are from a week ago (from around 12:00 BST on 2024-09-22).

The symptoms:
- Incoming messages on channels aren't showing up in the chat.sr.ht web interface.
- Outgoing messages on those channels sent via the web interface do reach the IRC network (Libera.Chat in this case).

Is this a known issue?

Thanks,
Joseph Koshy | <jkoshy@jkoshy.net> | https://jkoshy.net/

Greetings,

I am seeing the following error on 'hg push'es since the 5th of June:

  % hg push
  remote: added 2 changesets with 1 changes to 1 files
  remote: Server Error: invalid response from internal hook
  remote: warning: changegroup.srht hook exited with status 1

What is 'changegroup.srht', and why does it need to run on pushes?

Subsequent 'hg pull's seem to work OK so the remote repository seems fine (for now).

Should I file a bug at https://todo.sr.ht/~sircmpwn/hg.sr.ht?

> Did you publish the domain correctly with pages.sr.ht? When it works,
> curl should print a hash. Also note that you need to use an OAuth 2.0
> token, a legacy token will not work.

Yes, publishing had been successful yesterday.  I've re-run the
command again.

I needed to use -H "Authorization: Bearer $AUTH" to make it work,
(--oauth2-bearer "access token" wasn't enough).  curl did indeed
return a hash:

  % curl -H "Authorization: Bearer ${AUTHCODE}" -Fcontent=@site.tar.gz https://pages.sr.ht/publish/jkoshy.net
  3815c0d71a69d59e4425c2388dff77d77f5103afa589e98931b0eef471593bca

Greetings,

I configured a custom domain following the instructions at: https://srht.site/custom-domains, but the browsers complain when reading https://jkoshy.net (or https://www.jkoshy.net/).

The error message I get is:

  This site can’t provide a secure connection
  jkoshy.net sent an invalid response.
  ERR_SSL_PROTOCOL_ERROR

DNS lookup results: https://paste.sr.ht/~jkoshy/0cae4863861a1b497c627924f64de4bf0cb30070

On the command-line 'curl --verbose https://jkoshy.net/' aborts with an internal error ("curl: (35) error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error"): https://paste.sr.ht/~jkoshy/de0cbb33ec3e07c4c8a18c722610c5978b555e1f.