自建Piped服务时Apache反向代理出现TLS代理错误的求助

我已经被这个问题困扰好久了，实在没办法来求助大家！

我自己搭建了Piped服务，也配置好了Let's Encrypt证书，但Apache反向代理一直报TLS相关的错误。虽然Piped大部分功能都能正常使用，但没法导入列表，而且日志里的错误看着实在闹心，想把它彻底解决掉。

错误日志 #

[gnutls:error] [pid 1878860] [remote 127.0.0.1:8282] ssl_engine_set: mod_proxy requested TLS proxy, but not enabled for piped.[CENSORED].de:443

当前使用的Apache站点配置 #

<IfModule mod_ssl.c>
<VirtualHost *:443>
ServerName piped.[CENSORED].de
ServerAlias pipedapi.[CENSORED].de pipedproxy.[CENSORED].de
ServerAdmin netzmeister@[CENSORED].de

Protocols h2 h2c http/1.1

SSLProxyEngine On
ProxyPreserveHost On
ProxyPass / http://127.0.0.1:8282/
ProxyPassReverse / http://127.0.0.1:8282/
ProxyRequests Off
ProxyAddHeaders On
RequestHeader set X-Forwarded-Proto "https"

<LocationMatch "^/(/videoplayback|/api/v4/|/api/manifest/)">
Header always set Cache-Control "private"
Require all granted
</LocationMatch>

<Location "/">
Header always set Cache-Control "public, max-age=604800"
Require all granted
</Location>

Include /etc/letsencrypt/options-ssl-apache.conf
SSLCertificateFile /etc/letsencrypt/live/pipedapi.[CENSORED].de/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/pipedapi.[CENSORED].de/privkey.pem
</VirtualHost>
</IfModule>

我已经尝试过的解决方法 #

• 将SSLProxyEngine设置为Off，只保留ProxyAddHeaders On和RequestHeader set X-Forwarded-Proto "https"，但问题依旧存在
• 把Include /etc/letsencrypt/options-ssl-apache.conf移到SSLProxyEngine配置项的上方，没有任何效果
• 给ProxyPass和ProxyPassReverse中的地址加上s，改成https://127.0.0.1:8282/，结果触发了新的错误日志：

  [Sun Apr 09 19:15:35.915182 2023] [gnutls:error] [pid 1881378] [remote 127.0.0.1:8282] ssl_engine_set: mod_proxy requested TLS proxy, but not enabled for piped.[CENSORED].de:443
  [Sun Apr 09 19:15:35.915210 2023] [core:error] [pid 1881378] [remote 127.0.0.1:8282] AH01961:  failed to enable ssl support [Hint: if using mod_ssl, see SSLProxyEngine]
  [Sun Apr 09 19:15:35.915229 2023] [proxy:error] [pid 1881378] AH00961: https: failed to enable ssl support for 127.0.0.1:8282 (127.0.0.1)
  

另外我查了Piped的官方文档，上面只有Caddy和Nginx的配置示例，完全找不到Apache相关的配置参考，所以来请教各位大佬：有没有遇到过类似的问题？或者能给我一些Apache配置上的建议，帮我把这个错误彻底解决掉？

备注：内容来源于stack exchange，提问作者Johnnii360