Let's encrypt issue on latest 386.1 beta 2 (RT-AX86U)

[dr_lucas]

When trying to get a let's encrypt certificate, it keeps showing "Authorizing".

[EDITED: Let's encrypt issue is already listed as known]

Also, if I disable let's encrypt (set it to none), it generates a local certificate, but showing it was generated by and for 192.168.50.1, while my router is set on 192.168.1.1 and the network is on 192.168.1.x of course.

 

[RMerlin]

When running a beta firmware, it's a good idea to read the info posted in the Beta thread, especially the second post that lists all known issues. There are MANY posts there already about this.

 

[dr_lucas]

Thanks, just saw the let's encrypt issue listed. My bad.
Is the 192.168.50.1 issue also known?

 

[L&LD]

192.168.50.1 isn't an issue. This is a configurable option.

 

[dr_lucas]

What do you mean? My network is configured to 192.168.1.x and the LOCAL certificate (not lets encrypt) showing as issued to and by 192.168.50.1

https://imgur.com/T7zHynz

 

[RMerlin]

Probably means the certificate was issued before you changed the IP, you will have to regenerate it.

 

[blake444]

I add myself to the conversation because I would like to ask, is it normal that after a factory reset the ddns section still shows the active certificate? and if so, what does its revocation entail?

 

[dr_lucas]

Probably means the certificate was issued before you changed the IP, you will have to regenerate it.

Thanks. How do I delete and regenerate it?

 

[L&LD]

Format the JFFS partition on the next boot, make sure you hit 'Apply' at the bottom of the page before you reboot 3 times in the next 10 to 15 minutes (waiting between 5 to 10 minutes between each reboot).

 

[RMerlin]

Thanks. How do I delete and regenerate it?

"Generate a new certificate" on the screenshot you pasted.

 

[dr_lucas]

"Generate a new certificate" on the screenshot you pasted.

Thanks. Unfortunately it didn't make any change.
I followed what @L&LD suggested and that worked.

 

[RMerlin]

Thanks. Unfortunately it didn't make any change.

Was broken in beta 2, a backup was restored on top of the newly generated certificate. Will be fixed in beta 3.

 

[Eric Lieb]

Was broken in beta 2, a backup was restored on top of the newly generated certificate. Will be fixed in beta 3.

I don't have a generate new certificate option anywhere and mine is stuck at Status: Authorizing. On beta 3

 

[L&LD]

On RMerlin 386.1 Beta 4, the new certificate is generated and valid on my RT-AX86U.

 

[Eric Lieb]

On RMerlin 386.1 Beta 4, the new certificate is generated and valid on my RT-AX86U.

Ya I went ahead and upgraded to beta 4 and fully wiped the router. Now the cert is valid.

 

[palint]

Is this problem related somehow to a problem I get on my AC86U? I'm currently on 386_2.
I use succesfuly duckdns and I get error while trying to get LE certificate:

Verify error: Fetching [...] Timeout during connect (likely firewall problem)

Also on my RPi I can't get my certificate to work in docker - I get http connection to site which is supposed to have be certified..

 

[Nighthawk]

It works just fine on my AX86U firmware 386_2