Newbie local HTTPS error running existing Angular Bitbucket repository

I am new to Cloudflare and trying to prepare my Angular project with Firebase Auth and Messaging for deployment. Because the repository is on Bitbucket, I followed a process for manual deployment with plan to add bitbucket pipeline later. I added a wrangler.toml file in the root: name = "<cloudflare project name>" main = "src/cf-worker.ts" compatibility_date = "2023-07-24" [site] bucket = "<angular project dist/project_name folder>" and a worker (cf-worker.ts) in the src folder. I was able to deploy, completing the OAUTH login. When i run wrangler dev the site comes up and works except for the portion requiring HTTPS. The problem is that i am getting an error when i try: wrangler dev --local-protocol https I get the following error: kj/compat/tls.c++:501: error: error accepting tls connection; kj::mv(e) = kj/compat/tls.c++:74: failed: OpenSSL error; message = error:10000416:SSL routines:OPENSSL_internal:SSLV3_ALERT_CERTIFICATE_UNKNOWN stack: 103de1b5e 103de674e 103de6d98 103de75d0 103df1dc0 103df34c0 I need HTTPS to run a service-worker to get Firebase Messaging working
1 Reply
Tyrone
TyroneOP16mo ago
Hi Skye, I am running on Mac with wrangler version 3.4.0 LibreSSL 2.8.3 is the openssl version. i will give that a try and post if that resolves it. thank you. i tried both of your suggestions. Openssl version now: OpenSSL 3.1.2 1 Aug 2023 (Library: OpenSSL 3.1.2 1 Aug 2023) Still getting :
workerd/util/symbolizer.c++:99: warning: Not symbolizing stack traces because $LLVM_SYMBOLIZER is not set. To symbolize stack traces, set $LLVM_SYMBOLIZER to the location of the llvm-symbolizer binary. When running tests under bazel, use --test_env=LLVM_SYMBOLIZER=<path>. kj/compat/tls.c++:501: error: error accepting tls connection; kj::mv(e) = kj/compat/tls.c++:74: failed: OpenSSL error; message = error:10000416:SSL routines:OPENSSL_internal:SSLV3_ALERT_CERTIFICATE_UNKNOWN stack: 1091f5b5e 1091fa74e 1091fad98 1091fb5d0 109205dc0 1092074c0
Interestingly the https://<project>.<account>.workers.dev/home does work and fortunately. the browser is still able to reach my local VM running the backend. But would still like to get the local dev working properly.
Want results from more Discord servers?
Add your server