Bug 267492 - net/v2ray: service startup: panic: qtls.ClientHelloInfo doesn't match
Summary: net/v2ray: service startup: panic: qtls.ClientHelloInfo doesn't match
Status: Open
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-ports-bugs (Nobody)
URL: https://www.freshports.org/net/v2ray/
Keywords: crash
Depends on:
Blocks:
 
Reported: 2022-11-01 12:51 UTC by August M.H.
Modified: 2024-12-11 18:51 UTC (History)
6 users (show)

See Also:
grahamperrin: maintainer-feedback? (shen.elf)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description August M.H. 2022-11-01 12:51:16 UTC
When starting v2ray, it panics on startup.

Steps to reproduce
Start v2ray with 'service v2ray start'

Actual Results
v2ray crashes with the following error message
'panic: qtls.ClientHelloInfo doesn't match'

Expected Results
v2ray starts normally.
Comment 1 Graham Perrin freebsd_committer freebsd_triage 2022-11-01 23:59:55 UTC
(In reply to August M.H. from comment #0)

Which version of FreeBSD, exactly? 

Packages from latest, or quarterly?

freebsd-version -kru ; uname -aKU

pkg -vv | grep -e url -e enabled -e priority


----

A general hint, for the future: at the FreshPorts page for a port, the second of the two bug icons should place the required prefix (in this case: net/v2ray) in the summary line of a new bug report.
Comment 2 Jaskie 2023-01-02 08:23:10 UTC
Hi I am seeing this too. System info:

13.1-RELEASE-p3
13.1-RELEASE-p3
13.1-RELEASE-p5
FreeBSD freebsd.asus 13.1-RELEASE-p3 FreeBSD 13.1-RELEASE-p3 GENERIC amd64 1301000 1301000
    url             : "pkg+http://mirrors.ustc.edu.cn/freebsd-pkg/FreeBSD:13:amd64/latest",
    enabled         : yes,
    priority        : 0,


v2ray info: v2ray-4.36.2_7 from pkg.
Comment 3 kjkszpj32767 2023-05-12 08:55:36 UTC
This is probably due to version conflict. The qtls-go that v2ray depends on requires go-1.15, while go version in the ports is go-1.20.
Comment 4 Zsolt Udvari freebsd_committer freebsd_triage 2024-12-11 18:51:51 UTC
Is it still relevant?