# Cannot vertify for SSL

**URL:** <https://community.letsencrypt.org/t/cannot-vertify-for-ssl/165429>\
**Category:** Help\
**Created:** [November 13, 2021, 3:33pm UTC](https://community.letsencrypt.org/t/cannot-vertify-for-ssl/165429 "2021-11-13T15:33:28Z")\
**Posts on this page:** 5\
**Page:** 2

<div class="post-metadata">

**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\
**Post date:** [November 14, 2021, 2:45am UTC](https://community.letsencrypt.org/t/cannot-vertify-for-ssl/165429/26 "2021-11-14T02:45:33Z")

</div>

Cool.

Now the moment of truth. What do you see when you run:

```
curl -I 192.168.1.50:80
```

---

<div class="post-metadata">

**Author:** ![dreamcoder](https://avatars.discourse-cdn.com/v4/letter/d/977dab/32.png) [@dreamcoder](https://community.letsencrypt.org/u/dreamcoder)\
**Post date:** [November 14, 2021, 2:58am UTC](https://community.letsencrypt.org/t/cannot-vertify-for-ssl/165429/27 "2021-11-14T02:58:58Z")

</div>

curl -I [192.168.1.50:80](http://192.168.1.50/)  
HTTP/1.1 400 Bad Request  
Date: Sun, 14 Nov 2021 02:54:09 GMT  
Server: Apache/2.4.41 (Ubuntu)  
Expires: Thu, 19 Nov 1981 08:52:00 GMT  
Cache-Control: no-store, no-cache, must-revalidate  
Pragma: no-cache  
Content-Security-Policy: default-src 'self'; script-src 'self' 'nonce-WkJMNlo0U3R6b1FHWXI3TklxN3h5cXlNV3piUmM2ZVJMKzFWRnZXVUdhRT06SWxPT051eWE5dFplSjh5aWJPcVhvNVhKRkFkvZz0='; style-src 'self' 'unsafe-inline'; frame-src \*; img-src \* data: blob:; font-src 'self' data:; media-src \*; connect-src \*; object-src Q5citJQd2JyghWeO%2Fji%2B%2BBLQe2iSckJdrfYjQaAnEYljvlVwTvpsektAJ5AISKqi6Y2PzJk%2Fb7G; path=/; HttpOnly; SameSite=Lax  
Set-Cookie: ocrl6jw2lgwt=hhkg3579pfe6lr3vu7nnhnbuvs; path=/; HttpOnly; SameSite=Lax  
Set-Cookie: nc\_sameSiteCookielax=true; path=/; httponly;expires=Fri, 31-Dec-2100 23:59:59 GMT; SameSite=lax  
Set-Cookie: nc\_sameSiteCookiestrict=true; path=/; httponly;expires=Fri, 31-Dec-2100 23:59:59 GMT; SameSite=strict  
Referrer-Policy: no-referrer  
X-Content-Type-Options: nosniff  
X-Download-Options: noopen  
X-Frame-Options: SAMEORIGIN  
X-Permitted-Cross-Domain-Policies: none  
X-Robots-Tag: none  
X-XSS-Protection: 1; mode=block  
Connection: close  
Content-Type: text/html; charset=UTF-8

---

<div class="post-metadata">

**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\
**Post date:** [November 14, 2021, 3:11am UTC](https://community.letsencrypt.org/t/cannot-vertify-for-ssl/165429/28 "2021-11-14T03:11:20Z")

</div>

I see.

It seems like the first two port forwarding rules in DD-WRT are not working. At least, not when visiting your IP from the internet. (Which is what matters for Let's Encrypt).

Maybe you could try removing them and re-adding them? I'm afraid I don't really have any other ideas.

---

<div class="post-metadata">

**Author:** ![dreamcoder](https://avatars.discourse-cdn.com/v4/letter/d/977dab/32.png) [@dreamcoder](https://community.letsencrypt.org/u/dreamcoder)\
**Post date:** [November 28, 2021, 12:54pm UTC](https://community.letsencrypt.org/t/cannot-vertify-for-ssl/165429/29 "2021-11-28T12:54:45Z")

</div>

It was the firmware on DDWRT.

I reflashed original firmware, forwarded ports and it worked fine using certonly.

Also tested using the cable directly plugged into modem.

Many thanks for everyone's help

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [December 28, 2021, 12:54pm UTC](https://community.letsencrypt.org/t/cannot-vertify-for-ssl/165429/30 "2021-12-28T12:54:54Z")

</div>

Closed on December 28, 2021, 12:54pm UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

[Previous page](https://community.letsencrypt.org/t/cannot-vertify-for-ssl/165429.md?page=1)