search

atauenis / webone

HTTP 1.x proxy that makes old web browsers usable again in the Web 2.0 world.
Other
501 stars 15 forks source link

Raspberry PI 5 #127

Open my05 opened 3 months ago

my05 commented 3 months ago

Hi,

I tried to install Webone on RPI5 but it failed (following the Ubuntu 24.4 steps). The download works, but the install gives this:

$ sudo apt install ./webone.0.17.0.linux-amd64.deb Reading package lists... Done Building dependency tree... Done Reading state information... Done Note, selecting 'webone:amd64' instead of './webone.0.17.0.linux-amd64.deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation:

The following packages have unmet dependencies: webone:amd64 : Depends: dotnet-runtime-6.0:amd64 but it is not installable Recommends: yt-dlp:amd64 but it is not installable E: Unable to correct problems, you have held broken packages.

and so i went and installed dotnet-runtime according to https://www.petecodes.co.uk/install-and-use-microsoft-dot-net-6-with-the-raspberry-pi/

rebooted

and then tried again, but still get the same error. Please advice

atauenis commented 3 months ago

As Raspberry Pi is a ARM device, it is working with arm64 or armhf packages. amd64 are for regular PCs.

my05 commented 3 months ago

Got it. Thank you :)

I seem to have it installed (and running?) but even after changing the conf-file port to 8090 i can't really see any trace of it.

pi@raspberry5:~ $ sudo apt install ./webone.0.17.0.linux-arm64.deb Reading package lists... Done Building dependency tree... Done Reading state information... Done Note, selecting 'webone' instead of './webone.0.17.0.linux-arm64.deb' webone is already the newest version (0.17.0). 0 upgraded, 0 newly installed, 0 to remove and 41 not upgraded. pi@raspberry5:~ $ sudo service webone restart pi@raspberry5:~ $ netstat -lnt Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 0.0.0.0:6379 0.0.0.0: LISTEN tcp 0 0 127.0.0.1:631 0.0.0.0: LISTEN tcp 0 0 0.0.0.0:9000 0.0.0.0: LISTEN tcp 0 0 0.0.0.0:22 0.0.0.0: LISTEN tcp6 0 0 :::6379 ::: LISTEN tcp6 0 0 :::9000 ::: LISTEN tcp6 0 0 :::22 ::: LISTEN tcp6 0 0 ::1:631 ::: LISTEN tcp6 0 0 :::5900 :::* LISTEN pi@raspberry5:~ $

I'm probably missing something obvious, but i'm not sure what that might be.

atauenis commented 3 months ago

sudo service webone status, cat /var/log/webone.log?

my05 commented 3 months ago

Starting it with just plain

webone

gives loads of output that the ca md is too weak

10.06.2024 22:19:39.761+6259 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:19:39.761+29887 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:39.761+30272 <Done (connection closed by client). 10.06.2024 22:19:42.096+12557 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:19:42.096+32556 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:42.096+33143 <Done (connection closed by client). 10.06.2024 22:19:43.512+8045 >CONNECT www.google.com:443 (192.168.0.190) 10.06.2024 22:19:43.512+87143 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:43.512+87719 <Done (connection closed by client). 10.06.2024 22:19:43.539+10135 >CONNECT www.google.com:443 (192.168.0.190) 10.06.2024 22:19:43.539+65511 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:43.539+66355 <Done (connection closed by client). 10.06.2024 22:19:44.371+10445 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:19:44.371+34745 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:44.371+35611 <Done (connection closed by client). 10.06.2024 22:19:46.682+6148 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:19:46.682+23288 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:46.682+23881 <Done (connection closed by client). 10.06.2024 22:19:48.966+6526 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:19:48.966+25852 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:48.966+26429 <Done (connection closed by client). 10.06.2024 22:19:51.340+80752 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:19:51.340+128742 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:51.340+129308 <Done (connection closed by client). 10.06.2024 22:19:53.682+11847 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:19:53.682+28704 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:53.682+29626 <Done (connection closed by client). 10.06.2024 22:19:54.726+6398 >CONNECT www.google.com:443 (192.168.0.190) 10.06.2024 22:19:54.725+10337 >CONNECT optimizationguide-pa.googleapis.com:443 (192.168.0.190) 10.06.2024 22:19:54.726+23654 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:54.726+24055 <Done (connection closed by client). 10.06.2024 22:19:54.725+28554 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:54.725+28873 <Done (connection closed by client). 10.06.2024 22:19:54.731+5914 >CONNECT fonts.gstatic.com:443 (192.168.0.190) 10.06.2024 22:19:54.731+26710 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:54.731+27020 <Done (connection closed by client). 10.06.2024 22:19:54.746+5734 >CONNECT fonts.gstatic.com:443 (192.168.0.190) 10.06.2024 22:19:54.746+21396 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:54.746+22015 <Done (connection closed by client). 10.06.2024 22:19:54.746+28523 >CONNECT optimizationguide-pa.googleapis.com:443 (192.168.0.190) 10.06.2024 22:19:54.746+43493 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:54.746+43924 <Done (connection closed by client). 10.06.2024 22:19:54.746+50086 >CONNECT www.google.com:443 (192.168.0.190) 10.06.2024 22:19:54.746+68975 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:54.746+69462 <Done (connection closed by client).

my05 commented 3 months ago

sudo service webone status gives:

WebOne HTTP Proxy Server Loaded: loaded (/etc/systemd/system/webone.service; enabled; preset: enabled) Active: inactive (dead) since Mon 2024-06-10 22:04:01 CEST; 17min ago Duration: 197ms Docs: https://github.com/atauenis/webone/wiki/ Process: 3111 ExecStart=/usr/local/bin/webone --daemon (code=exited, status=0/SUCCESS) Main PID: 3111 (code=exited, status=0/SUCCESS) CPU: 178ms

Jun 10 22:04:01 raspberry5 webone[3111]: WebOne HTTP Proxy Server 0.17.0 Jun 10 22:04:01 raspberry5 webone[3111]: https://github.com/atauenis/webone Jun 10 22:04:01 raspberry5 webone[3111]: Using configuration file /etc/webone.conf. Jun 10 22:04:01 raspberry5 webone[3111]: Using configuration file /etc/webone.conf.d/my.conf. Jun 10 22:04:01 raspberry5 webone[3111]: Using configuration file /etc/webone.conf.d/escargot.conf. Jun 10 22:04:01 raspberry5 webone[3111]: Using configuration file /etc/webone.conf.d/codepage.conf. Jun 10 22:04:01 raspberry5 webone[3111]: Using event log file /var/log/webone.log. Jun 10 22:04:01 raspberry5 webone[3111]: Using event log file /var/log/webone.log. Jun 10 22:04:01 raspberry5 webone[3111]: Error while loading configuration: An item with the same key has already been added. Key: txt Jun 10 22:04:01 raspberry5 systemd[1]: webone.service: Deactivated successfully.

and cat /var/log/webone.log gives as follows:

10.06.2024 21:49:39 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 21:49:39.438+0 Configuration file /etc/webone.conf load complete. 10.06.2024 21:49:39.438+0 Configuration file /etc/webone.conf.d/escargot.conf load complete. 10.06.2024 21:49:39.438+0 Configuration file /etc/webone.conf.d/codepage.conf load complete. 10.06.2024 21:49:39.438+0 Creating root SSL Certificate & Private Key for CA... 10.06.2024 21:49:39.438+0 CA Certificate: /etc/webone.conf.d/ssl.crt; Key: /etc/webone.conf.d/ssl.key. 10.06.2024 21:49:39.438+0 Configured to http://raspberry5:8080/, HTTP 1.1, HTTPS 1.1, CERN-compatible 10.06.2024 21:49:41.274+0 Supported protocols: HTTP, HTTPS, FTP via Web browser. 10.06.2024 21:49:39.438+0 Listening for HTTP 1.x on port 8080. 10.06.2024 21:49:39.438+0 WebOne has been exited. 10.06.2024 21:52:19.544+56546 HTTP/HTTPS/CERN Server stopped. 10.06.2024 21:52:19 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 21:52:19 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 21:52:19.653+0 WebOne has been exited due to lack of configuration. 10.06.2024 21:53:34 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 21:53:34 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 21:57:05 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 21:57:05 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 21:57:05.197+0 WebOne has been exited due to lack of configuration. 10.06.2024 21:58:08 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 21:58:08 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 21:59:33 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 21:59:33 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 22:00:22 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 22:00:22 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 22:00:24 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 22:00:24 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 22:04:01 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 22:04:01 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 22:18:36 WebOne 0.17.0 (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 22:18:36.829+0 Configuration file /home/pi/webone.conf load complete. 10.06.2024 22:18:36.829+0 Creating root SSL Certificate & Private Key for CA... 10.06.2024 22:18:36.829+0 CA Certificate: ./ssl.crt; Key: ./ssl.key. 10.06.2024 22:18:36.829+0 Configured to http://raspberry5:8090/, HTTP 1.1, HTTPS 1.1, CERN-compatible 10.06.2024 22:18:38.140+0 Supported protocols: HTTP, HTTPS, FTP via Web browser. 10.06.2024 22:18:36.829+0 Listening for HTTP 1.x on port 8090. 10.06.2024 22:18:38.427+185216 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:18:38.516+6985 >CONNECT 103.chtsite.com:8886 (192.168.0.190) 10.06.2024 22:18:38.516+36706 >Non-HTTP: 103.chtsite.com:8886 10.06.2024 22:18:38.516+321459 Tunnel established. 10.06.2024 22:18:39.139+4656129 <Done. 10.06.2024 22:18:39.139+4642187 <Return code 501. 10.06.2024 22:18:39.139+4634369 Cannot made SSL connection: System.ArgumentException: An item with the same key has already been added. Key: CN=auth.gog.com at System.Collections.Generic.Dictionary2.TryInsert(TKey key, TValue value, InsertionBehavior behavior) at System.Collections.Generic.Dictionary2.Add(TKey key, TValue value) at WebOne.CertificateUtil.MakeChainSignedCert(String certSubject, X509Certificate2 issuerCertificate, HashAlgorithmName certHashAlgorithm) at WebOne.HttpSecureServer..ctor(HttpRequest Request, HttpResponse Response, LogWriter Logger) at WebOne.HttpTransit.ProcessTransit() 10.06.2024 22:18:39.139+7196 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:18:38.427+8489735 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:18:38.427+8520000 <Done (connection closed by client). 10.06.2024 22:18:42.357+16049 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:18:42.357+101528 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:18:42.357+102898 <Done (connection closed by client). 10.06.2024 22:18:42.666+10106 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:18:42.666+36437 !SSL Handshake failed: Received an unexpected EOF or 0 bytes from the transport stream. (-2146232800) 10.06.2024 22:18:42.666+37230 <Done (connection closed by client). 10.06.2024 22:18:44.262+8386 >CONNECT ssl.gstatic.com:443 (192.168.0.190) 10.06.2024 22:18:44.679+8374 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:18:44.679+124147 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:18:44.679+126552 <Done (connection closed by client). 10.06.2024 22:18:44.977+4891 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:18:44.977+46436 !SSL Handshake failed: Received an unexpected EOF or 0 bytes from the transport stream. (-2146232800) 10.06.2024 22:18:44.977+47052 <Done (connection closed by client). 10.06.2024 22:18:44.262+5911093 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:18:44.262+5911792 <Done (connection closed by client). 10.06.2024 22:18:45.465+4799 >CONNECT ssl.gstatic.com:443 (192.168.0.190) 10.06.2024 22:18:45.465+26633 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:18:45.465+27029 <Done (connection closed by client). 10.06.2024 22:18:46.935+9819 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:18:46.935+73774 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:18:46.935+74336 <Done (connection closed by client). 10.06.2024 22:18:47.257+18898 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:18:47.257+72510 !SSL Handshake failed: Received an unexpected EOF or 0 bytes from the transport stream. (-2146232800) 10.06.2024 22:18:47.257+73279 <Done (connection closed by client). 10.06.2024 22:18:49.237+9511 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:18:49.237+26174 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:18:49.237+26827 <Done (connection closed by client). 10.06.2024 22:18:49.282+16644 >CONNECT play.google.com:443 (192.168.0.190) 10.06.2024 22:18:49.282+4815818 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:18:49.282+4817210 <Done (connection closed by client). 10.06.2024 22:18:50.256+5871 >CONNECT play.google.com:443 (192.168.0.190) 10.06.2024 22:18:50.256+24319 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:18:50.256+25278 <Done (connection closed by client). 10.06.2024 22:18:51.555+6629 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:18:51.555+78940 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:18:51.555+80046 <Done (connection closed by client). 10.06.2024 22:18:51.857+4935 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:18:51.857+24823 !SSL Handshake failed: Received an unexpected EOF or 0 bytes from the transport stream. (-2146232800) 10.06.2024 22:18:51.857+25962 <Done (connection closed by client). 10.06.2024 22:18:53.843+5235 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:18:53.843+77444 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:18:53.843+78615 <Done (connection closed by client). 10.06.2024 22:18:54.142+4919 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:18:54.142+42264 !SSL Handshake failed: Received an unexpected EOF or 0 bytes from the transport stream. (-2146232800) 10.06.2024 22:18:54.142+43107 <Done (connection closed by client). 10.06.2024 22:18:56.147+14111 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:18:56.147+33141 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:18:56.147+34263 <Done (connection closed by client). 10.06.2024 22:18:58.413+6273 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:18:58.413+69386 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:18:58.413+69997 <Done (connection closed by client). 10.06.2024 22:18:58.748+6562 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:18:58.748+44758 !SSL Handshake failed: Received an unexpected EOF or 0 bytes from the transport stream. (-2146232800) 10.06.2024 22:18:58.748+45323 <Done (connection closed by client). 10.06.2024 22:19:00.751+12241 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:19:00.751+33705 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:00.751+34355 <Done (connection closed by client). 10.06.2024 22:19:03.022+6415 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:19:03.022+32597 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:03.022+33143 <Done (connection closed by client). 10.06.2024 22:19:03.278+7126 >CONNECT www.youtube.com:443 (192.168.0.190) 10.06.2024 22:19:03.278+5220957 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:03.278+5221533 <Done (connection closed by client). 10.06.2024 22:19:04.327+5887 >CONNECT www.youtube.com:443 (192.168.0.190) 10.06.2024 22:19:04.327+19686 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:04.327+20225 <Done (connection closed by client). 10.06.2024 22:19:05.319+9406 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:19:05.319+36223 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:05.319+36676 <Done (connection closed by client). 10.06.2024 22:19:07.619+5643 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:19:07.619+71088 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:07.619+71640 <Done (connection closed by client). 10.06.2024 22:19:07.928+4754 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:19:07.928+32775 !SSL Handshake failed: Received an unexpected EOF or 0 bytes from the transport stream. (-2146232800) 10.06.2024 22:19:07.928+33242 <Done (connection closed by client). 10.06.2024 22:19:09.949+6534 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:19:09.949+27335 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:09.949+27897 <Done (connection closed by client). 10.06.2024 22:19:12.218+7085 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:19:12.218+53491 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:12.218+54247 <Done (connection closed by client). 10.06.2024 22:19:14.461+6900 >CONNECT stackabuse.com:443 (192.168.0.190) 10.06.2024 22:19:14.504+7077 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:19:14.504+73048 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:14.504+73886 <Done (connection closed by client). 10.06.2024 22:19:14.802+17026 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:19:14.802+36671 !SSL Handshake failed: Received an unexpected EOF or 0 bytes from the transport stream. (-2146232800) 10.06.2024 22:19:14.802+37818 <Done (connection closed by client). 10.06.2024 22:19:15.013+5340 >CONNECT www.google.com:443 (192.168.0.190) 10.06.2024 22:19:14.461+9564592 <Done (connection closed by client). 10.06.2024 22:19:14.461+9564119 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:16.374+59645 <Done (connection closed by client). 10.06.2024 22:19:16.374+58613 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:16.374+4481 >CONNECT stackabuse.com:443 (192.168.0.190) 10.06.2024 22:19:15.962+4086 >CONNECT api.msn.com:443 (192.168.0.190) 10.06.2024 22:19:15.255+4785 >CONNECT spclient.wg.spotify.com:443 (192.168.0.190) 10.06.2024 22:19:16.387+67443 <Done (connection closed by client). 10.06.2024 22:19:16.387+66484 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:16.387+10749 >CONNECT stackabuse.com:443 (192.168.0.190) 10.06.2024 22:19:16.402+19485 <Done (connection closed by client). 10.06.2024 22:19:16.402+18762 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:16.402+4180 >CONNECT stackabuse.com:443 (192.168.0.190) 10.06.2024 22:19:15.013+7412955 <Done (connection closed by client). 10.06.2024 22:19:15.013+7411547 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:15.255+6200856 <Done (connection close). 10.06.2024 22:19:15.255+6199451 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:16.410+66372 >CONNECT optimizationguide-pa.googleapis.com:443 (192.168.0.190) 10.06.2024 22:19:16.496+4320 >CONNECT fonts.gstatic.com:443 (192.168.0.190) 10.06.2024 22:19:16.501+24438 <Done (connection closed by client). 10.06.2024 22:19:16.501+23904 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:16.501+7696 >CONNECT www.google.com:443 (192.168.0.190) 10.06.2024 22:19:16.796+64902 <Done (connection closed by client). 10.06.2024 22:19:16.796+63980 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:16.796+4267 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:19:17.099+417972 <Done (connection closed by client). 10.06.2024 22:19:17.099+417070 !SSL Handshake failed: Received an unexpected EOF or 0 bytes from the transport stream. (-2146232800) 10.06.2024 22:19:17.099+397082 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:19:15.962+6481317 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:15.962+6481820 <Done (connection closed by client). 10.06.2024 22:19:15.962+6486801 >CONNECT safebrowsing.google.com:443 (192.168.0.190) 10.06.2024 22:19:17.534+23892 <Done (connection closed by client). 10.06.2024 22:19:17.534+22963 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:17.534+4372 >CONNECT www.google.com:443 (192.168.0.190) 10.06.2024 22:19:17.545+29991 <Done (connection closed by client). 10.06.2024 22:19:17.545+29088 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:17.545+8422 >CONNECT www.google.com:443 (192.168.0.190) 10.06.2024 22:19:16.496+5672112 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:16.496+5672589 <Done (connection closed by client). 10.06.2024 22:19:16.496+5677158 >CONNECT www.google.com:443 (192.168.0.190) 10.06.2024 22:19:16.496+5697357 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:16.496+5706575 <Done (connection closed by client). 10.06.2024 22:19:17.647+19209 <Done (connection closed by client). 10.06.2024 22:19:17.647+18967 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:17.647+3954 >CONNECT fonts.gstatic.com:443 (192.168.0.190) 10.06.2024 22:19:17.642+22588 <Done (connection closed by client). 10.06.2024 22:19:17.642+22312 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:17.642+4075 >CONNECT www.google.com:443 (192.168.0.190) 10.06.2024 22:19:17.637+26345 <Done (connection closed by client). 10.06.2024 22:19:17.637+25927 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:17.637+4864 >CONNECT fonts.gstatic.com:443 (192.168.0.190) 10.06.2024 22:19:17.657+19463 <Done (connection closed by client). 10.06.2024 22:19:17.657+19166 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:17.657+3967 >CONNECT fonts.gstatic.com:443 (192.168.0.190) 10.06.2024 22:19:16.410+6907412 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:16.410+6907908 <Done (connection closed by client). 10.06.2024 22:19:17.797+7893 >CONNECT optimizationguide-pa.googleapis.com:443 (192.168.0.190) 10.06.2024 22:19:17.797+26320 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:17.797+26612 <Done (connection closed by client). 10.06.2024 22:19:15.962+11256948 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:15.962+11257434 <Done (connection closed by client). 10.06.2024 22:19:18.219+12953 >CONNECT safebrowsing.google.com:443 (192.168.0.190) 10.06.2024 22:19:18.219+63076 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:18.219+63337 <Done (connection closed by client). 10.06.2024 22:19:18.382+4118 >CONNECT www.google.com:443 (192.168.0.190) 10.06.2024 22:19:18.382+21980 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:18.382+22277 <Done (connection closed by client). 10.06.2024 22:19:18.391+4019 >CONNECT www.google.com:443 (192.168.0.190) 10.06.2024 22:19:18.391+16967 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:18.391+17276 <Done (connection closed by client). 10.06.2024 22:19:19.108+5094 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:19:19.108+22935 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:19.108+23250 <Done (connection closed by client). 10.06.2024 22:19:19.599+11654 >CONNECT optimizationguide-pa.googleapis.com:443 (192.168.0.190) 10.06.2024 22:19:19.601+3963 >CONNECT www.google.com:443 (192.168.0.190) 10.06.2024 22:19:19.601+23364 <Done (connection closed by client). 10.06.2024 22:19:19.599+32433 <Done (connection closed by client). 10.06.2024 22:19:19.601+22393 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:19:19.599+31446 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087)

atauenis commented 3 months ago

Seems that latest Raspbian have same bug as Debian 12. Its OpenSSL have permanently broken support for pre-SHA2 certificates.

Try to change SslHashAlgorithm=SHA1 to SslHashAlgorithm=SHA256, clear contents of /etc/webone.conf.d/ssl.crt & /etc/webone.conf.d/ssl.key, and restart WebOne service.

my05 commented 3 months ago

Made the change to /etc/webone.conf.d/my.conf as well as any webone.conf i had in /etc.

This is the output i get (same issue):

pi@raspberry5:/etc/webone.conf.d $ ls codepage.conf escargot.conf my.conf openssl_webone.cnf pi@raspberry5:/etc/webone.conf.d $ sudo service webone restart pi@raspberry5:/etc/webone.conf.d $ sudo service webone status ○ webone.service - WebOne HTTP Proxy Server Loaded: loaded (/etc/systemd/system/webone.service; enabled; preset: enabled) Active: inactive (dead) since Mon 2024-06-10 22:40:41 CEST; 9s ago Duration: 197ms Docs: https://github.com/atauenis/webone/wiki/ Process: 3783 ExecStart=/usr/local/bin/webone --daemon (code=exited, status=0/SUCCESS) Main PID: 3783 (code=exited, status=0/SUCCESS) CPU: 165ms

Jun 10 22:40:41 raspberry5 webone[3783]: WebOne HTTP Proxy Server 0.17.0 Jun 10 22:40:41 raspberry5 webone[3783]: https://github.com/atauenis/webone Jun 10 22:40:41 raspberry5 webone[3783]: Using configuration file /etc/webone.conf. Jun 10 22:40:41 raspberry5 webone[3783]: Using configuration file /etc/webone.conf.d/my.conf. Jun 10 22:40:41 raspberry5 webone[3783]: Using configuration file /etc/webone.conf.d/escargot.conf. Jun 10 22:40:41 raspberry5 webone[3783]: Using configuration file /etc/webone.conf.d/codepage.conf. Jun 10 22:40:41 raspberry5 webone[3783]: Using event log file /var/log/webone.log. Jun 10 22:40:41 raspberry5 webone[3783]: Using event log file /var/log/webone.log. Jun 10 22:40:41 raspberry5 webone[3783]: Error while loading configuration: An item with the same key has already been added. Key: txt Jun 10 22:40:41 raspberry5 systemd[1]: webone.service: Deactivated successfully. pi@raspberry5:/etc/webone.conf.d $ cat /var/log/webone.log 10.06.2024 21:49:39 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 21:49:39.438+0 Configuration file /etc/webone.conf load complete. 10.06.2024 21:49:39.438+0 Configuration file /etc/webone.conf.d/escargot.conf load complete. 10.06.2024 21:49:39.438+0 Configuration file /etc/webone.conf.d/codepage.conf load complete. 10.06.2024 21:49:39.438+0 Creating root SSL Certificate & Private Key for CA... 10.06.2024 21:49:39.438+0 CA Certificate: /etc/webone.conf.d/ssl.crt; Key: /etc/webone.conf.d/ssl.key. 10.06.2024 21:49:39.438+0 Configured to http://raspberry5:8080/, HTTP 1.1, HTTPS 1.1, CERN-compatible 10.06.2024 21:49:41.274+0 Supported protocols: HTTP, HTTPS, FTP via Web browser. 10.06.2024 21:49:39.438+0 Listening for HTTP 1.x on port 8080. 10.06.2024 21:49:39.438+0 WebOne has been exited. 10.06.2024 21:52:19.544+56546 HTTP/HTTPS/CERN Server stopped. 10.06.2024 21:52:19 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 21:52:19 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 21:52:19.653+0 WebOne has been exited due to lack of configuration. 10.06.2024 21:53:34 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 21:53:34 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 21:57:05 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 21:57:05 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 21:57:05.197+0 WebOne has been exited due to lack of configuration. 10.06.2024 21:58:08 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 21:58:08 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 21:59:33 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 21:59:33 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 22:00:22 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 22:00:22 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 22:00:24 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 22:00:24 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 22:04:01 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 22:04:01 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 22:18:36 WebOne 0.17.0 (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 22:18:36.829+0 Configuration file /home/pi/webone.conf load complete. 10.06.2024 22:18:36.829+0 Creating root SSL Certificate & Private Key for CA... 10.06.2024 22:18:36.829+0 CA Certificate: ./ssl.crt; Key: ./ssl.key. 10.06.2024 22:18:36.829+0 Configured to http://raspberry5:8090/, HTTP 1.1, HTTPS 1.1, CERN-compatible 10.06.2024 22:18:38.140+0 Supported protocols: HTTP, HTTPS, FTP via Web browser. 10.06.2024 22:18:36.829+0 Listening for HTTP 1.x on port 8090. 10.06.2024 22:18:38.427+185216 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:18:38.516+6985 >CONNECT 103.chtsite.com:8886 (192.168.0.190) 10.06.2024 22:18:38.516+36706 >Non-HTTP: 103.chtsite.com:8886 10.06.2024 22:18:38.516+321459 Tunnel established. 10.06.2024 22:18:39.139+4656129 <Done. 10.06.2024 22:18:39.139+4642187 <Return code 501. 10.06.2024 22:18:39.139+4634369 Cannot made SSL connection: System.ArgumentException: An item with the same key has already been added. Key: CN=auth.gog.com at System.Collections.Generic.Dictionary2.TryInsert(TKey key, TValue value, InsertionBehavior behavior) at System.Collections.Generic.Dictionary2.Add(TKey key, TValue value) at WebOne.CertificateUtil.MakeChainSignedCert(String certSubject, X509Certificate2 issuerCertificate, HashAlgorithmName certHashAlgorithm) at WebOne.HttpSecureServer..ctor(HttpRequest Request, HttpResponse Response, LogWriter Logger) at WebOne.HttpTransit.ProcessTransit() 10.06.2024 22:18:39.139+7196 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:18:38.427+8489735 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:18:38.427+8520000 <Done (connection closed by client). 10.06.2024 22:18:42.357+16049 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:18:42.357+101528 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:18:42.357+102898 <Done (connection closed by client). 10.06.2024 22:18:42.666+10106 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:18:42.666+36437 !SSL Handshake failed: Received an unexpected EOF or 0 bytes from the transport stream. (-2146232800) 10.06.2024 22:18:42.666+37230 <Done (connection closed by client). 10.06.2024 22:18:44.262+8386 >CONNECT ssl.gstatic.com:443 (192.168.0.190) 10.06.2024 22:18:44.679+8374 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:18:44.679+124147 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:18:44.679+126552 <Done (connection closed by client). 10.06.2024 22:18:44.977+4891 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:18:44.977+46436 !SSL Handshake failed: Received an unexpected EOF or 0 bytes from the transport stream. (-2146232800) 10.06.2024 22:18:44.977+47052 <Done (connection closed by client). 10.06.2024 22:18:44.262+5911093 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:18:44.262+5911792 <Done (connection closed by client). 10.06.2024 22:18:45.465+4799 >CONNECT ssl.gstatic.com:443 (192.168.0.190) 10.06.2024 22:18:45.465+26633 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:18:45.465+27029 <Done (connection closed by client). 10.06.2024 22:18:46.935+9819 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:18:46.935+73774 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:18:46.935+74336 <Done (connection closed by client). 10.06.2024 22:18:47.257+18898 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:18:47.257+72510 !SSL Handshake failed: Received an unexpected EOF or 0 bytes from the transport stream. (-2146232800) 10.06.2024 22:18:47.257+73279 <Done (connection closed by client). 10.06.2024 22:18:49.237+9511 >CONNECT auth.gog.com:443 (192.168.0.190) 10.06.2024 22:18:49.237+26174 !SSL Handshake failed: Using SSL certificate failed with OpenSSL error - ca md too weak. (-2146233087) 10.06.2024 22:18:49.237+26827 <Done (connection closed by client).

etc...

atauenis commented 3 months ago

What's really inside ssl.crt? Can you view it by any X509 certificate viewer? Does it really have SHA256 format, or it's still not SHA256 certificate? The log also looks very strange, like the Pi is buggy or too overclocked (works unstable).

my05 commented 3 months ago

that is a mystery. Because even if the log output says

"Jun 10 22:40:41 raspberry5 systemd[1]: webone.service: Deactivated successfully. pi@raspberry5:/etc/webone.conf.d $ cat /var/log/webone.log 10.06.2024 21:49:39 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 https://github.com/atauenis/webone/pull/1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 10.06.2024 21:49:39.438+0 Configuration file /etc/webone.conf load complete. 10.06.2024 21:49:39.438+0 Configuration file /etc/webone.conf.d/escargot.conf load complete. 10.06.2024 21:49:39.438+0 Configuration file /etc/webone.conf.d/codepage.conf load complete. 10.06.2024 21:49:39.438+0 Creating root SSL Certificate & Private Key for CA... 10.06.2024 21:49:39.438+0 CA Certificate: /etc/webone.conf.d/ssl.crt; Key: /etc/webone.conf.d/ssl.key. 10.06.2024 21:49:39.438+0 Configured to http://raspberry5:8080/, HTTP 1.1, HTTPS 1.1, CERN-compatible 10.06.2024 21:49:41.274+0 Supported protocols: HTTP, HTTPS, FTP via Web browser."

when checking inside the "webone.conf.d" folder i have only this:

pi@raspberry5:/etc/webone.conf.d $ ls -lag total 60 drwxr-xr-x 2 root 4096 Jun 14 19:18 . drwxr-xr-x 139 root 12288 Jun 14 19:25 .. -rw-r--r-- 1 root 1690 Dec 20 20:18 codepage.conf -rw-r--r-- 1 root 3597 Oct 23 2023 escargot.conf -rw-r--r-- 1 root 3785 May 17 13:04 openssl_webone.cnf -rw-r--r-- 1 root 31102 Jun 14 19:17 webone.conf

no ssl files in sight.

atauenis commented 3 months ago

Try reinstall OS on Pi's SD card from scratch. I've tested with Raspbian 11 (and partially 10, 12).

my05 commented 3 months ago

I will do that, thx :)

Some background: got delivery of this thing a few months back and installed (and updated everything) before installing an m.2 hat with nvme on it.

but i will check what is needed to make it from scratch again.

I'll report back.

thx

my05 commented 3 months ago

Before having reinstalled, i tried to simply execute it on the command-line with "webone" and this way it works perfectly fine

"pi@raspberry5:~ $ webone WebOne HTTP Proxy Server 0.17.0 https://github.com/atauenis/webone

Using configuration file webone.conf. Using event log file /var/log/webone.log. Configuration load complete. Supported protocols: HTTP, HTTPS, FTP via Web browser. Listening for HTTP 1.x on port 8090."

Log output:

16.06.2024 18:01:09 WebOne 0.17.0 (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 16.06.2024 18:01:09.647+0 Configuration file /home/pi/webone.conf load complete. 16.06.2024 18:01:09.647+0 Using as SSL Certificate Authority: ./ssl.crt, ./ssl.key. 16.06.2024 18:01:09.647+0 Configured to http://raspberry5:8090/, HTTP 1.1, HTTPS 1.1, CERN-compatible 16.06.2024 18:01:10.548+0 Supported protocols: HTTP, HTTPS, FTP via Web browser. 16.06.2024 18:01:09.647+0 Listening for HTTP 1.x on port 8090.

Trying to start it as a service gives:

16.06.2024 18:02:28 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 16.06.2024 18:02:29 WebOne 0.17.0 --daemon (Linux 6.6.28+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) Arm64, Runtime 6.0.30 Arm64) log started. 16.06.2024 18:02:28.888+0 WebOne has been exited due to lack of configuration.

Looking at the status:

"○ webone.service - WebOne HTTP Proxy Server Loaded: loaded (/etc/systemd/system/webone.service; enabled; preset: enabled) Active: inactive (dead) since Sun 2024-06-16 18:02:29 CEST; 57s ago Duration: 193ms Docs: https://github.com/atauenis/webone/wiki/ Process: 3128 ExecStart=/usr/local/bin/webone --daemon (code=exited, status=0/SUCCESS) Main PID: 3128 (code=exited, status=0/SUCCESS) CPU: 173ms

Jun 16 18:02:28 raspberry5 webone[3128]: https://github.com/atauenis/webone Jun 16 18:02:28 raspberry5 webone[3128]: Using configuration file /etc/webone.conf. Jun 16 18:02:28 raspberry5 webone[3128]: Using configuration file /etc/webone.conf.d/webone.conf. Jun 16 18:02:28 raspberry5 webone[3128]: Using configuration file /etc/webone.conf.d/my.conf. Jun 16 18:02:28 raspberry5 webone[3128]: Using configuration file /etc/webone.conf.d/escargot.conf. Jun 16 18:02:28 raspberry5 webone[3128]: Using configuration file /etc/webone.conf.d/codepage.conf. Jun 16 18:02:28 raspberry5 webone[3128]: Using event log file /var/log/webone.log. Jun 16 18:02:29 raspberry5 webone[3128]: Using event log file /var/log/webone.log. Jun 16 18:02:29 raspberry5 webone[3128]: Error while loading configuration: An item with the same key has already been added. Key: txt Jun 16 18:02:29 raspberry5 systemd[1]: webone.service: Deactivated successfully."

(on the side, i tried lthe same on the rPI4 and there also it starts when executed directly. But when starting it as a service, it complains about the /etc/webone directory being read-only)

atauenis commented 3 months ago

Try 0.16.3 for compare. I've using it on RPi 1 (ARMv6) with fresh install of Raspbian 10,11,12 without problems. Haven't tested with 0.17 currently (no enough free time).

Raspbian 10 and 11 are running on a 4GB MicroSD card, 12 is on 32GB card. So 10 is a "standard" install, 11 is a "lite", and 12 is again "standard". Used regular RasPi Imager tool to flash, so all systems are default.

There are no problems as listed in this bug report. Working just like on a regular x86_64 Debian system.