Project

General

Profile

Bug #124

IPv6 issues on https

Added by Woozle Hypertwin almost 6 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
High
Assignee:
Woozle Hypertwin
Start date:
05/31/2018
Due date:
% Done:

100%

Spent time:
0.30 h

Description

See this

History

#1 Updated by Woozle Hypertwin almost 6 years ago

  • Status changed from New to Feedback
  • Assignee set to Woozle Hypertwin
  • % Done changed from 0 to 100

Problem reproduced:

root@cloud5:~# wget https://toot.cat
--2018-05-31 11:26:57--  https://toot.cat/
Resolving toot.cat (toot.cat)... 2604:a880:2:d0::205e:5001, 138.68.60.118
Connecting to toot.cat (toot.cat)|2604:a880:2:d0::205e:5001|:443... connected.
Unable to establish SSL connection.
root@cloud5:~#

Solution: There needs to be an IPv6 line in every server{} block of the config, or IPv6 will fail whenever that section is hit. The following line was missing from the main/first https section: listen [::]:443 ssl; (typically goes right after listen 443 ssl;).

The above test now returns:

root@cloud5:~# wget https://toot.cat
--2018-05-31 11:29:22--  https://toot.cat/
Resolving toot.cat (toot.cat)... 2604:a880:2:d0::205e:5001, 138.68.60.118
Connecting to toot.cat (toot.cat)|2604:a880:2:d0::205e:5001|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://toot.cat/about [following]
--2018-05-31 11:29:22--  https://toot.cat/about
Reusing existing connection to [toot.cat]:443.
HTTP request sent, awaiting response... 200 OK

(etc.)

Confirming with user that it's fixed at their end as well.

#2 Updated by Woozle Hypertwin almost 6 years ago

  • Status changed from Feedback to Closed
$ curl -6 https://toot.cat/@news/100121888892093312 > /dev/null
$ echo $?
0

Also available in: Atom PDF