@flyqie 有想过，目前比较想实现多个网页

@TsubasaHanekaw 感觉单页面没有必要啊，本来想 Vitepress 直接工具，但又觉得没必要。Hugo+多语言主题，想想单页面又算了

@wuruxu 重整 nginx 配置，其他网站没有问题，唯独这个有问题，看日志就这个显示 502 错误，弄了好久，感觉无解

@june4 平时开车看红绿灯会不会眼睛累？会不会有点分不清？

@wuruxu 我也觉得，感谢回复，我改动试一下

@wuruxu 抱歉，忘了改动 nginx ，我重新装载 nginx 试试

@wuruxu 貌似没看到错误提示

@wuruxu * Trying 198.xx.98.xx:443... * Connected to test.xxx.com (198.xx.98.xx) port 443 (#0)
* ALPN: offers h2 * ALPN: offers http/1.1

* [CONN-0-0][CF-SSL] TLSv1.0 (OUT), TLS header, Certificate Status (22): * [CONN-0-0][CF-SSL] TLSv1.3 (OUT), TLS handshake, Client hello (1):
* [CONN-0-0][CF-SSL] TLSv1.2 (IN), TLS header, Certificate Status (22):
* [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake, Server hello (2):
* [CONN-0-0][CF-SSL] TLSv1.2 (IN), TLS header, Finished (20): * [CONN-0-0][CF-SSL] TLSv1.2 (IN), TLS header, Supplemental data (23): * [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): * [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake, Certificate (11):
* [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake, CERT verify (15):
* [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake, Finished (20):
* [CONN-0-0][CF-SSL] TLSv1.2 (OUT), TLS header, Finished (20):
* [CONN-0-0][CF-SSL] TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* [CONN-0-0][CF-SSL] TLSv1.2 (OUT), TLS header, Supplemental data (23):
* [CONN-0-0][CF-SSL] TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN: server accepted h2
* Server certificate:
* subject: CN:xxx.com
* start date: Dec 5 00:34:00 2023 GMT
* expire date: Mar 4 00:33:59 2024 GMT
* subjectAltName: host "test.xxx.com" matched cert's "*.xxx.com"
* issuer: C=US; O=Let's Encrypt; CN=E1
* SSL certificate verify ok.
* Using HTTP2, server supports multiplexing
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* [CONN-0-0][CF-SSL] TLSv1.2 (OUT), TLS header, Supplemental data (23):
* [CONN-0-0][CF-SSL] TLSv1.2 (OUT), TLS header, Supplemental data (23):
* [CONN-0-0][CF-SSL] TLSv1.2 (OUT), TLS header, Supplemental data (23):
* h2h3 [:method: GET]
* h2h3 [:path: /cr_proxy/]
* h2h3 [:scheme: https]
* h2h3 [:authority: test.xxx.com]
* h2h3 [user-agent: curl/7.87.0]
* h2h3 [accept: */*]
* h2h3 [ppurl: https://www.google.com.sg/]
* Using Stream ID: 1 (easy handle 0xb400007ccf08d800)
* [CONN-0-0][CF-SSL] TLSv1.2 (OUT), TLS header, Supplemental data (23):
> GET /cr_proxy/ HTTP/2
> Host: test.xxx.com
> user-agent: curl/7.87.0
> accept: */*
> ppurl:https://www.google.com.sg/
>
* [CONN-0-0][CF-SSL] TLSv1.2 (IN), TLS header, Supplemental data (23):
* [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* [CONN-0-0][CF-SSL] TLSv1.2 (IN), TLS header, Supplemental data (23):
* [CONN-0-0][CF-SSL] TLSv1.2 (OUT), TLS header, Supplemental data (23):
* [CONN-0-0][CF-SSL] TLSv1.2 (IN), TLS header, Supplemental data (23):
* [CONN-0-0][CF-SSL] TLSv1.2 (IN), TLS header, Supplemental data (23):
< HTTP/2 520
< date: Wed, 17 Jan 2024 05:07:23 GMT
< content-type: text/plain; charset=UTF-8
< content-length: 15
< report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=G2DMvdCp881gMb2QyFAe7nkNoIwY2ucqTBJ%2B2D3E4XqL1wHCNcqxsa%2BoKszS4hax%2Fi8LI6eOilB0BFGruIelg7biv%2Ft04%2BMXzeF4pZ67uba1QH616YeolvaTtTZAQ%2F89gQ%3D%3D"}],"group":"cf-nel","max_age":604800}
< nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
< strict-transport-security: max-age=2592000; includeSubDomains; preload
< x-content-type-options: nosniff
< x-frame-options: SAMEORIGIN
< referrer-policy: same-origin
< cache-control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
< expires: Thu, 01 Jan 1970 00:00:01 GMT
< server: cloudflare
< cf-ray: 846c13043b530e40-AMS
< alt-svc: h3=":443"; ma=86400
<
* [CONN-0-0][CF-SSL] TLSv1.2 (IN), TLS header, Supplemental data (23):
* [CONN-0-0][CF-SSL] TLSv1.2 (IN), TLS header, Supplemental data (23):
* Connection #0 to host test.xxx.com left intact

@wuruxu 如此看来就是两个问题，
1.第一次没配置证书
2.以前用两年，现在自己手撸 nginx ，刚刚试了一下反向代理自己其他服务也是提示 5xx 错误

看样子是 nginx 的配置出了问题
感谢楼主解答，我再尝试一下

@wuruxu 楼主的意思，uid 是不用自己设置的吗？

@wuruxu 我以为是自己没上证书的问题，现在看来 后面上了证书，还有存在这个问题，可能不是这个问题，还是 uid 的问题吧

@wuruxu 可能是 uid 的问题，我只是谷歌了一下 nginx 的 uid 照着自己修改的填写，不起作用，http uid 是指的哪方面的设置？

@wuruxu 加了/ 所有配置都是抄的你的，就域名换成自己的

楼主 按照你的设置，显示 502 错误

我不信，是 Go 语言才对，不信？我右上角的红星都亮了。