# Receiving error regarding certificate not being able to load **URL:** https://meta.discourse.org/t/receiving-error-regarding-certificate-not-being-able-to-load/406822 **Category:** Self-hosting **Tags:** nginx **Created:** [July 4, 2026, 11:48am UTC](https://meta.discourse.org/t/receiving-error-regarding-certificate-not-being-able-to-load/406822 "2026-07-04T11:48:17Z") **Posts on this page:** 1 **Showing post:** 2
### Author: ![NateDhaliwal](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/natedhaliwal/32/313494_2.png) [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal) #### Post date: [July 4, 2026, 1:32pm UTC](https://meta.discourse.org/t/receiving-error-regarding-certificate-not-being-able-to-load/406822/2 "2026-07-04T13:32:38Z")
I suppose you’re using Let’s Encrypt? You can try this: > [@PEM\_read\_bio\_X509\_AUX() failed (SSL: error:0909006C:PEM routines:get\_name:no start line:Expecting: TRUSTED CERTIFICATE)](https://meta.discourse.org/t/pem-read-bio-x509-aux-failed-ssl-errorpem-routinesno-start-line-trusted-certificate/176546/2): > > If you did a [Discourse official Standard Installation](https://meta.discourse.org/t/discourse-official-standard-installation/142537) and deleted everything and started over a bunch of times, you hit the let’s encrypt rate limit and can’t get a certificate for a week And: > [@PEM\_read\_bio\_X509\_AUX() failed (SSL: error:0909006C:PEM routines:get\_name:no start line:Expecting: TRUSTED CERTIFICATE)](https://meta.discourse.org/t/pem-read-bio-x509-aux-failed-ssl-errorpem-routinesno-start-line-trusted-certificate/176546/6): > > For the record, I’ve had the same issue and the problem was that I forgot to redirect port 80 to the server. The DNS check done by discourse-server.sh might be done on port 443 only and did not detect the problem. But Let’s Encrypt does need the port 80 also open. --- _[View the full topic](https://meta.discourse.org/t/receiving-error-regarding-certificate-not-being-able-to-load/406822)._