Deploying Caprover - ARM SSL Error

[barcovanrhijn]

What is the problem?

When deploying Caprover to a new server using Arm64 I'm getting a weird SSL error

Error: RequestError: Error: write EPROTO C0A74550F0730000:error:0A000410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1605:SSL alert number 40

Steps to reproduce the problem:

Install Docker & Then deploy Caprover.
Use caprover serversetup to setup. The error appears after "Enabling SSL... Takes a few seconds..."

Output of the following command on your server:

uname -a && lsb_release -a && free -h

Linux appserver2 5.15.0-100-generic #110-Ubuntu SMP Wed Feb 7 13:28:04 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.4 LTS
Release: 22.04
Codename: jammy
total used free shared buff/cache available
Mem: 3.7Gi 314Mi 275Mi 4.0Mi 3.1Gi 3.2Gi
Swap: 0B 0B 0B

[barcovanrhijn]

Hmm getting the same error when deploying to X64. I've considered that this might be Cloudflare related and removed the proxy setting on Cloudflare. But still no dice.

[githubsaturn]

This also could be a local issue on your local machine (e.g. your laptop). Can you try finishing the set up using the web GUI? You can login to ip:3000 on your browser and manually set the domain and enable/force SSL. Does this work?

[storageddd]

I have same error. After I tried to setup it manually, captain subdomain stops working and I have to many redirects error.

Next steps helped me to solve the issue:

1. disable SSL (include force redirects) on domain provider (in my case Cloudflare);
2. remove caprover container via ssh;
3. install caprover and local setup;
4. create new app in captain interface (caprover.yourdomain.io) and enable HTTPS redirects personally for it (app.yourdomain.io);
5. enable SSL on domain provider (without force HTTP redirects).

[barcovanrhijn]

I retried this on x86 as well; it does not seem to be an issue with the Architecture. I think I needed some required crypto packages for Debian/Ubuntu to be able to get this going. Some unofficial install guides pointed this way.

…

On Tue, 16 Apr 2024, 05:08 Kasra Bigdeli, ***@***.***> wrote: This also could be a local issue on your local machine (e.g. your laptop). Can you try finishing the set up using the web GUI? You can login to ip:3000 on your browser and manually set the domain and enable/force SSL. Does this work? — Reply to this email directly, view it on GitHub <#2042 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASFR24Y7GL35ETEUPXHJXKLY5SI3NAVCNFSM6AAAAABGHXHQMKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJYGE2TAMZZGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>