Raspiblitz: Cannot connect to ElectRS over SSL

Created on 2 Mar 2020  路  6Comments  路  Source: rootzoll/raspiblitz

  • Running a clean install of Raspiblitz 1.4
  • ElectRS installed properly with no errors and fully indexed with no errors
  • I Can connect to Electrs over localhost:50001:t
  • I Cannot connect to Electrs over localhost:50002:s or address.onion:50002:s

sudo nginx -t
returns
nginx: [emerg] BIO_new_file("/etc/ssl/certs/localhost.crt") failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/ssl/certs/localhost.crt','r') error:2006D080:BIO routines:BIO_new_file:no such file) nginx: configuration file /etc/nginx/nginx.conf test failed

I have been running Raspiblitz 1.3 for months with ElectRS working fine over SSL.
It seems that something is wrong with the initial electrs/nginx setup process in 1.4

bug - unconfirmed updates and fixes

Most helpful comment

Here is the answer describing to solve this:
https://github.com/rootzoll/raspiblitz/issues/859#issuecomment-590280339
Start with running this to create a new self-signed cert:
Create a new cert key for nginx using the available script:
/home/admin/config.scripts/internet.selfsignedcert.sh

All 6 comments

Here is the answer describing to solve this:
https://github.com/rootzoll/raspiblitz/issues/859#issuecomment-590280339
Start with running this to create a new self-signed cert:
Create a new cert key for nginx using the available script:
/home/admin/config.scripts/internet.selfsignedcert.sh

That fixed it, thank you.

Just wanted to note that I got this error on a clean install of 1.4, I did not upgrade from 1.3.

The line in the solution is run during the electrs setup script, but must be failing.
Could not demonstrate this issue yet on my test nodes, but will keep an eye on it.
Thank you for reporting!

@openoms can we do anything for the v1.5 to improve on this?

maybe we could run the internet.selfsignedcert.sh later on or last in the script.

That fixed it, thank you.

Just wanted to note that I got this error on a clean install of 1.4, I did not upgrade from 1.3.

Had the same issue and this fixed it for me, too. (upgraded from v1.2 to v1.5rc1)

Was this page helpful?
0 / 5 - 0 ratings

Related issues

tiero picture tiero  路  4Comments

shawnyeager picture shawnyeager  路  4Comments

Himbeergeld picture Himbeergeld  路  3Comments

intorid picture intorid  路  3Comments

fluidvoice picture fluidvoice  路  3Comments