[Release] Asuswrt-Merlin 384.14 (and 384.13_2) are now available

[skeal]

LetsEncrypt cert issue is still here.

Dec 18 21:24:49 kernel: Cert success.
Dec 18 21:24:49 kernel: cat: write error: Invalid argument

And cert.pem/chain.pem nor created, nor updated properly.

Enable webui access from both https and http on the system page under administration. This does not mean your router is open to the web. Oh and reboot.

 

[The Chief]

Enable webui access from both https and http on the system page under administration.

Interesting. Why https webui became a «a must» for LE? I'm curious.

 

[skeal]

Interesting. Why https webui became a «a must» for LE? I'm curious.

It's something I stumbled upon. I don't know the technical reason.

 

[srwal]

I don't have a USB plugged in.... I even tried the original ASUS firmware.... still no changes... Firmware seems to be installing, the main page refreshes, and then nothing!

I also did a manual reset, and the factory reset as well

Finally got it rectified... Did a recovery flash to the first Merlin RT-AC68U_378.55_0, then did a dirty flash to RT-AC68U_384.14_0.

All seems to be well now...

 

[Grisu]

you should have mentioned that your last firmware is more than 3 years old

 

[skeal]

flash to the first Merlin RT-AC68U_378.55_0, then did a dirty flash to RT-AC68U_384.14_0.

Should reset the router to factory defaults and hand configure. Upgrading that far is going to cause problems, sooner or later.

 

[htismaqe]

Back to Beta 3 on my RT-AC86U. The GUI had locked up twice this afternoon running 383.14 release.

 

[srwal]

you should have mentioned that your last firmware is more than 3 years old

I was running 384.13 and it wouldn't take the firmware, so that why I went that far back to see if my hunch would work...and it did

 

[maxbraketorque]

Installed 384.14_0 on three AC86Us this morning. Two are a main/AP pair, and the third is a router at a remote site with the update installed over OVPN. All good so far, but one thing I noticed is that the router name is showing up in my syslog server as the name that I provided in the LAN section followed by a dash and a series of alphanumeric characters.

 

[ezflma]

@RMerlin, fyi, I installed 384.15_alpha1-gd2fea342ca on my RT-AX88U tonight, and it fixed my USB Samba SMBv2 access issues. It's up and functional. Thank you.

 

[RAH-66]

AX88U 3.0.0.4.384.7968 2019/12/18

 

[skeal]

@RMerlin, fyi, I installed 384.15_alpha1-gd2fea342ca on my RT-AX88U tonight, and it fixed my USB Samba SMBv2 access issues. It's up and functional. Thank you.

+1 No issues so far with the alpha 1.

 

[skeal]

AX88U 3.0.0.4.384.7968 2019/12/18

Looks like 384.15 is getting interesting for the AX88U!

 

[Marin]

No issues with the 384.15 alpha here, too.

 

[Treadler]

+1 No issues so far with the alpha 1.

No issues here.

It was awful until I did an initialise/restore though.
I had never done a reset on this router. Just lazy!

All good now.

 

[Andy1932]

Get your own thread!!!

 

[RAH-66]

Looks like 384.15 is getting interesting for the AX88U!

I hope this new GPL will go into 384.15 alpha 2

ASUS RT-AX88U Firmware version 3.0.0.4.384.7968 :
- Improve wireless compatibility.
- Improve wireless performance.
- AiProtection related issue fixes.
- Supports Amazon Wi-Fi simple setup : Helps you connect WSS supported devices to your Wi-Fi network and Alexa account in fewer steps. Enabling this feature creates a simple setup network that supported devices can use to access Wi-Fi credentials saved in the Amazon Wi-Fi Locker.

 

[Cyanix]

AX88U 3.0.0.4.384.7968 2019/12/18

Firmware has been pulled from the web page.

Tried it for 20 minutes, WAN was down the whole time.

 

[RMerlin]

Dec 18 21:24:49 kernel: cat: write error: Invalid argument

That is NOT an error message, this message is perfectly normal.

And cert.pem/chain.pem nor created, nor updated properly.

acme.sh does not create these files, it now creates files named after the domain. Check a few lines below, the complete path and filenames to the new key and certs are logged.

 

[RMerlin]

Interesting. Why https webui became a «a must» for LE? I'm curious.

Because the stock firmware ONLY uses LE for https, therefore enabling LE without https makes no sense.