~sircmpwn/sr.ht-discuss

5 3

Re: [pages] Custom domains

Details
Message ID
<620933810.132916.1614457532383@office.mailbox.org>
DKIM signature
missing
Download raw message
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.

What am I doing wrong?

Thanks,
Joseph Koshy

Re: [pages] Custom domains

Details
Message ID
<C9KLLGBXOQ5D.34YV1NA1MLKN@taiga>
In-Reply-To
<620933810.132916.1614457532383@office.mailbox.org> (view parent)
DKIM signature
missing
Download raw message
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.

Re: [pages] Custom domains

Details
Message ID
<247252270.133071.1614459480626@office.mailbox.org>
In-Reply-To
<C9KLLGBXOQ5D.34YV1NA1MLKN@taiga> (view parent)
DKIM signature
missing
Download raw message
> 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

This is the same hash as returned by yesterday's upload.

As of now 'curl https://jkoshy.net' has started working, which is
great.  'curl https://www.jkoshy.net' however continues to report
the SSL error.

Thanks,
Joseph Koshy

Re: [pages] Custom domains

Details
Message ID
<C9KM6AKSCTOF.24UTJ2LZZ2UF3@taiga>
In-Reply-To
<247252270.133071.1614459480626@office.mailbox.org> (view parent)
DKIM signature
missing
Download raw message
On Sat Feb 27, 2021 at 3:58 PM EST,  wrote:
> As of now 'curl https://jkoshy.net' has started working, which is
> great. 'curl https://www.jkoshy.net' however continues to report
> the SSL error.

These are treated as separate sites, and you need to publish them
separately. I disrecommend using www. in $CURRENTYEAR, though.

Re: [pages] Custom domains

Details
Message ID
<87lfb95exo.fsf@nyarlathotep>
In-Reply-To
<C9KM6AKSCTOF.24UTJ2LZZ2UF3@taiga> (view parent)
DKIM signature
missing
Download raw message
Drew DeVault <sir@cmpwn.com> writes:

> On Sat Feb 27, 2021 at 3:58 PM EST,  wrote:
>> As of now 'curl https://jkoshy.net' has started working, which is
>> great. 'curl https://www.jkoshy.net' however continues to report
>> the SSL error.
>
> These are treated as separate sites, and you need to publish them
> separately. I disrecommend using www. in $CURRENTYEAR, though.

curious about recommending against 'www.': why?

Re: [pages] Custom domains

Details
Message ID
<C9KNXGWF10UM.VZ83HS1QDL1@taiga>
In-Reply-To
<87lfb95exo.fsf@nyarlathotep> (view parent)
DKIM signature
missing
Download raw message
It's $CURRENTYEAR. No one needs to specify the protocol for every
subdomain.
Reply to thread Export thread (mbox)