Lots of client "Bad Response code for GET" as well as SSL errors

Seafile Client
,
1

Hi there,

my SeaDrive client is spitting out a lot of GET errors despite, from what I can tell, functioning completely fine. I can download and sync all my files yet I keep getting some errors in the logs. The SSL error even shows up as a regular windows notification:

This is the client seafile log:

[12/27/21 11:44:00] Starting SeaDrive client 2.0.18
[12/27/21 11:44:00] rpc server started.
[12/27/21 11:44:02] start to serve on pipe client
[12/27/21 11:44:03] start to serve on pipe client
[12/27/21 11:44:03] switching account to https://seafile.example.com REDACTED@gmail.com.
[12/27/21 11:44:03] start to serve on pipe client
[12/27/21 11:44:03] start to serve on pipe client
[12/27/21 11:44:04] switching account to https://seafile.example.com REDACTED@gmail.com.
[12/27/21 11:44:04] Bad response code for GET https://seafile.example.com/seafhttp/protocol-version: 404.
[12/27/21 11:44:14] Bad response code for GET https://seafile.example.com/seafhttp/protocol-version: 404.
[12/27/21 11:44:24] Bad response code for GET https://seafile.example.com/seafhttp/protocol-version: 404.
[12/27/21 11:44:34] Bad response code for GET https://seafile.example.com/seafhttp/protocol-version: 404.
[12/27/21 11:44:46] Bad response code for GET https://seafile.example.com/seafhttp/protocol-version: 404.
[12/27/21 11:44:54] Bad response code for GET https://seafile.example.com/seafhttp/protocol-version: 404.
[12/27/21 11:45:00] cache size limit is 10000000000
[12/27/21 11:45:04] Bad response code for GET https://seafile.example.com/seafhttp/protocol-version: 404.
[12/27/21 11:45:14] Bad response code for GET https://seafile.example.com/seafhttp/protocol-version: 404.
[12/27/21 11:45:24] Bad response code for GET https://seafile.example.com/seafhttp/protocol-version: 404.
[12/27/21 11:45:34] Bad response code for GET https://seafile.example.com/seafhttp/protocol-version: 404.
[12/27/21 11:45:44] Bad response code for GET https://seafile.example.com/seafhttp/protocol-version: 404.
[12/27/21 11:45:54] Bad response code for GET https://seafile.example.com/seafhttp/protocol-version: 404.
[12/27/21 11:46:04] Bad response code for GET https://seafile.example.com/seafhttp/protocol-version: 404.
[12/27/21 11:46:14] Bad response code for GET https://seafile.example.com/seafhttp/protocol-version: 404.
[12/27/21 11:46:24] Bad response code for GET https://seafile.example.com/seafhttp/protocol-version: 404.
[12/27/21 11:46:34] Bad response code for GET https://seafile.example.com/seafhttp/protocol-version: 404.
[12/27/21 11:46:45] Bad response code for GET https://seafile.example.com/seafhttp/protocol-version: 404.
[12/27/21 11:46:54] Bad response code for GET https://seafile.example.com/seafhttp/protocol-version: 404.
[12/27/21 11:47:04] Bad response code for GET https://seafile.example.com/seafhttp/protocol-version: 404.
[12/27/21 11:47:14] Bad response code for GET https://seafile.example.com/seafhttp/protocol-version: 404.
[12/27/21 11:47:25] Bad response code for GET https://seafile.example.com/seafhttp/protocol-version: 404.
[12/27/21 11:47:34] Bad response code for GET https://seafile.example.com/seafhttp/protocol-version: 404.
[12/27/21 11:47:44] Bad response code for GET https://seafile.example.com/seafhttp/protocol-version: 404.
[12/27/21 11:47:52] libcurl failed to GET https://seafile.example.com/api2/repos/: SSL connect error.
[12/27/21 11:47:54] Bad response code for GET https://seafile.example.com/seafhttp/protocol-version: 404.
[12/27/21 11:48:04] Bad response code for GET https://seafile.example.com/seafhttp/protocol-version: 404.
[12/27/21 11:48:14] Bad response code for GET https://seafile.example.com/seafhttp/protocol-version: 404.
[12/27/21 11:48:24] Bad response code for GET https://seafile.example.com/seafhttp/protocol-version: 404.
[12/27/21 11:48:35] Bad response code for GET https://seafile.example.com/seafhttp/protocol-version: 404.
[12/27/21 11:48:45] Bad response code for GET https://seafile.example.com/seafhttp/protocol-version: 404.
[12/27/21 11:48:52] libcurl failed to GET https://seafile.example.com/api2/repos/: Timeout was reached.
[12/27/21 11:48:55] Bad response code for GET https://seafile.example.com/seafhttp/protocol-version: 404.
[12/27/21 11:49:04] Bad response code for GET https://seafile.example.com/seafhttp/protocol-version: 404.

This is my Apache reverse proxy config:

<VirtualHost *:80>

               ServerName seafile.example.com
               ServerAdmin admin@example.com

               RewriteEngine On
               RewriteCond %{HTTPS} !=on
               RewriteRule ^/?(.*) https://%{SERVER_NAME}/$1 [R,L]

               #ProxyPass / http://localhost:8000/
               #ProxyPassReverse / http://localhost:8000/
</VirtualHost>

<VirtualHost *:443>

  ServerName seafile.example.com

  SSLEngine On
  SSLCertificateFile /etc/letsencrypt/live/seafile.example.com/cert.pem
  SSLCertificateKeyFile /etc/letsencrypt/live/seafile.example.com/privkey.pem
  SSLCertificateChainFile /etc/letsencrypt/live/seafile.example.com/fullchain.pem

  Alias /media  /home/seafile/haiwen/seafile-server-latest/seahub/media

  <Location /media>
    Require all granted
  </Location>

  RewriteEngine On

  #
  # seafile fileserver
  #
  ProxyPass /seafhttp http://127.0.0.1:8082
  ProxyPassReverse /seafhttp http://127.0.0.1:8082
  RewriteRule ^/seafhttp - [QSA,L]

  #
  # seahub
  #
  SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1
  ProxyPreserveHost On
  ProxyPass / http://127.0.0.1:8000/
  ProxyPassReverse / http://127.0.0.1:8000/
</VirtualHost>

I can’t find anything online that points to this exact error. I’m using an Apache reverse proxy and Let’s Encrypt SSL certificates. I’ve recently upgraded from Seafile Server Community to Seafile Server Pro.

As already mentioned everything seems to actually work perfectly fine I just keep getting these errors or warnings.

Any help appreciated! If I missed any info feel free to ask