QUIC works only locally!

Help
1

Hi there!
I am using Caddy 0.9.4 for a test server and I want to use QUIC feature.

when I run caddy on my site with:
caddy -quic

using one computer with quic flag enabled on chrome, if I connect to the internet locally (from any ethernet on the same internal network) and try to reach my web site, inspecting the web site in chrome on security section I can see :
Protocol : quic
…
I can even easily confirm with wireshark the quic protocol.

But, when I try to reach my website (not touching the server side) from out side the network in which my server is not located, the protocol switches to TLS 1.2!!!

Where is the problem, and how can I solve it?

More info:
Caddyfile:
https://mysite.com
errors caddy-error.log # I do not get any error on this file

log caddy-logs.log # : some of it:
5.170.21.214 - [16/Jan/2017:17:32:36 +0100] “GET / HTTP/2.0” 304 0
10.79.1.236 - [16/Jan/2017:17:32:50 +0100] “GET / HTTP/2.0” 304 0
10.79.1.236 - [16/Jan/2017:17:32:54 +0100] “GET /testfiles/filetest5mb.test HTTP/2.0” 200 5242880
10.79.1.236 - [16/Jan/2017:17:33:15 +0100] “GET /testfiles/filetest50mb.test HTTP/2.0” 200 52428800
10.79.1.236 - [16/Jan/2017:17:33:46 +0100] “GET / HTTP/2.0” 200 578
10.79.1.236 - [16/Jan/2017:17:33:46 +0100] “GET /quicdeibDiag.png HTTP/2.0” 200 14408
10.79.1.236 - [16/Jan/2017:17:33:46 +0100] “GET /style.css HTTP/2.0” 200 138
10.79.1.236 - [16/Jan/2017:17:33:54 +0100] “GET / HTTP/2.0” 304 23
5.170.21.214 - [16/Jan/2017:17:35:01 +0100] “GET / HTTP/1.1” 200 578
5.170.21.214 - [16/Jan/2017:17:35:01 +0100] “GET /style.css HTTP/1.1” 200 138
5.170.21.214 - [16/Jan/2017:17:35:01 +0100] “GET /quicdeibDiag.png HTTP/1.1” 200 14408
5.170.21.214 - [16/Jan/2017:17:35:01 +0100] “GET /transpicon.ico HTTP/1.1” 200 318
5.170.21.214 - [16/Jan/2017:17:35:45 +0100] “GET /testfiles/filetest100mb.test HTTP/1.1” 200 22020096
5.170.21.214 - [16/Jan/2017:17:39:59 +0100] “GET /testfiles/filetest50mb.test HTTP/2.0” 200 28606464
93.47.224.30 - [16/Jan/2017:17:57:32 +0100] “GET /filetest10mb.test HTTP/2.0” 404 14
93.47.224.30 - [16/Jan/2017:17:57:32 +0100] “GET /favicon.ico HTTP/2.0” 404 14

2

Quite possibly some external network blocking UDP on that port. Google has reported this was a minor, but one of the more significant barriers, to QUIC adoption. Fortunately, TLS 1.3 + HTTP/2 are fast TCP alternatives.

3

Is there anyway on server side to have quic running? like using alternative ports?

How can I use TLS 1.3? is it standardized yet? can we run HTTP/2.0 + TLS 1.3 on Caddy now?

4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.