RT-AC88U - 3.0.0.4.382.18991 (New features)

[Gregory Phillips]

I find it odd that it ran without incident for a couple of days and then suddenly began exhibiting this odd behavior dropping the connection.

 

[Gregory Phillips]

Suffice to say after rolling back I've not had any disconnects yet. I find it strange that initially there were no issues with the new firmware until after a few days had passed and then the unit wouldn't stop dropping connections irrespective of whether or not you power cycled or rebooted it.

 

[netfer]

I find it odd that it ran without incident for a couple of days and then suddenly began exhibiting this odd behavior dropping the connection.

I already seen that ram raises up to 47%, I use the june2017 firmware and the ram os 33%. I upaste to the latest and get download speeds below 50mb, and get kernel entries in the log. I think I go black to the june firmware again.

 

[Gregory Phillips]

I tried several power cycles on the latest firmware but didn't do a reset on it nor am I inclined to do so. Seeing it bomb at random doesn't sit well with me and since I use VOIP phone service the last thing in the world I want for it to do is kill my landline.

 

[Gregory Phillips]

Now the feedback feature in the router says it doesn't have an internet connection even though it does.

Edit: I'm trying it again but this time I manually downloaded the file to install locally rather than allowing the router to obtain the file itself so we'll see what happens.

 

[Graceliying961121]

Intermittent disconnects (no visible WLAN SSID for some minutes) with this firmware.
Even with factory reset.
Seems like the router reboots wireless-part.
Streaming Video interrupts often.
Reverted back to stable RT-AC88U_3.0.0.4_380_7743.

My router in FW3.0.0.4.382_18991 is ok.
Do you have any special settings?

 

[Gregory Phillips]

I'm beginning to believe that my issue is with a particular software client rather than with the router and I will continue to monitor things and report if I discover anything else.

 

[PAPPL]

My router in FW3.0.0.4.382_18991 is ok.
Do you have any special settings?

No special settings. Tried with default wireless settings (WPA2), my settings and Smartconnect settings. No change, streaming is horrible even with Amazon fire tv stick, which has no client settings.
Youtube switches to 240p after minutes, amazon video is pixelated, and after minutes wireless disconnects.
Even Merlin 382.1 firmware has poor wireless performance, but no wireless disconnects.
Switched back to August Firmware, and all ist back to normal.

 

[SystemF]

Just update to 3.0.0.4.382_18991,(without factory reset after update), so far:
1. Extremely slow entering https://router.asus.com.
2. Increase RAM usage to 190 MB with Ai Protection On.
3. Ram justo increase to 191 , as the moment I write this post,
don't download any torrents everything is turned off, only browsing.

So far, not good impressions...........

 

[Gregory Phillips]

Yeah after several more disconnects I've rolled back to 15850.

 

[SystemF]

Roll back to 3.0.0.4.380.7743

 

[RMerlin]

Extremely slow entering

Use another browser than Chrome for https.

Increase RAM usage to 190 MB with Ai Protection On.

How is that a problem? The router has 512 MB of RAM, it's not unusual for additional feature to use more RAM, and that's still well within what's reasonable since the router has 512 MB.

 

[SystemF]

Yep Merlin you're right, i will give one more try with new firmware, will tested with iptv and heavy torrenting to see is there any lags like last firmware.

Update: The IPTV Manual Settings still don't work, set up vids given from my isp and the wan flash red, so disappointing.

Update 2: CPU1 hit 70 % almost - downloading 3 torrents on my broadband 2nd plan 50 Mbps,
iptv glitch 2 times, during downloads.

With old firmware download about 10 torrents cpu hit almost 30-40 %.....pffff again this new firmware is crap, is someone will find new features alexa and iftt useful, i will probably never will use it, Asus can fix the damn iptv issues and and all others stuff thus they add new unnecessary features ........

Update 3: CPU1 just hit 75-79% , CPU 2,3 %, the download speed is slow can't hit even 45Mbps.
Final decision go back to 3.0.0.4.380.7743.

 

[Gregory Phillips]

It looks like the hardware version doesn't make a difference with these issues. I'm perplexed as to why it didn't have any issues for the first few days and then suddenly started dropping the WAN?

 

[PythonJ]

Does Hide SSID also hide guest networks for anyone else? The firmware has been running fine but for some reason the guest networks are hidden, now this wouldn't be a problem but for some weird reason our TV's can connect fine but android phones won't :S I'm more than happy to go back to 380.7743 but what about the security fixes? Will I be ok as long as I change the login name and running normal router mode?

 

[Gregory Phillips]

Roll back to 3.0.0.4.380.7743

Did that earlier today.

 

[Deleted member 22229]

Did that earlier today.

While 7743 is a good firmware there have been plenty of security updates since then. Something to consider.

 

[Gregory Phillips]

While 7743 is a good firmware there have been plenty of security updates since then. Something to consider.

Not having any WAN issues on 7743 trumps any other consideration.

 

[sanke1]

Still no luck in getting Let's Encrypt certificate

Error log is

Dec  6 15:05:01 rc_service: service 6333:notify_rc restart_letsencrypt
Dec  6 15:05:07 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 403
Dec  6 15:05:07 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "urn:acme:error:unauthorized", "detail": "No registration exists matching provided key", "status": 403 }] (120 bytes)
Dec  6 15:10:01 rc_service: service 6451:notify_rc restart_letsencrypt
Dec  6 15:10:13 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 403
Dec  6 15:10:13 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "urn:acme:error:unauthorized", "detail": "No registration exists matching provided key", "status": 403 }] (120 bytes)
Dec  6 15:15:01 rc_service: service 6573:notify_rc restart_letsencrypt
Dec  6 15:15:08 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 403
Dec  6 15:15:08 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "urn:acme:error:unauthorized", "detail": "No registration exists matching provided key", "status": 403 }] (120 bytes)
Dec  6 15:20:01 rc_service: service 6691:notify_rc restart_letsencrypt
Dec  6 15:20:06 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 403
Dec  6 15:20:06 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "urn:acme:error:unauthorized", "detail": "No registration exists matching provided key", "status": 403 }] (120 bytes)
Dec  6 15:25:01 rc_service: service 6812:notify_rc restart_letsencrypt
Dec  6 15:25:07 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 403
Dec  6 15:25:07 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "urn:acme:error:unauthorized", "detail": "No registration exists matching provided key", "status": 403 }] (120 bytes)
Dec  6 15:30:01 rc_service: service 6930:notify_rc restart_letsencrypt
Dec  6 15:30:07 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 403
Dec  6 15:30:07 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "urn:acme:error:unauthorized", "detail": "No registration exists matching provided key", "status": 403 }] (120 bytes)

 

[RMerlin]

Still no luck in getting Let's Encrypt certificate

Error log is

Dec  6 15:05:01 rc_service: service 6333:notify_rc restart_letsencrypt
Dec  6 15:05:07 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 403
Dec  6 15:05:07 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "urn:acme:error:unauthorized", "detail": "No registration exists matching provided key", "status": 403 }] (120 bytes)
Dec  6 15:10:01 rc_service: service 6451:notify_rc restart_letsencrypt
Dec  6 15:10:13 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 403
Dec  6 15:10:13 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "urn:acme:error:unauthorized", "detail": "No registration exists matching provided key", "status": 403 }] (120 bytes)
Dec  6 15:15:01 rc_service: service 6573:notify_rc restart_letsencrypt
Dec  6 15:15:08 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 403
Dec  6 15:15:08 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "urn:acme:error:unauthorized", "detail": "No registration exists matching provided key", "status": 403 }] (120 bytes)
Dec  6 15:20:01 rc_service: service 6691:notify_rc restart_letsencrypt
Dec  6 15:20:06 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 403
Dec  6 15:20:06 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "urn:acme:error:unauthorized", "detail": "No registration exists matching provided key", "status": 403 }] (120 bytes)
Dec  6 15:25:01 rc_service: service 6812:notify_rc restart_letsencrypt
Dec  6 15:25:07 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 403
Dec  6 15:25:07 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "urn:acme:error:unauthorized", "detail": "No registration exists matching provided key", "status": 403 }] (120 bytes)
Dec  6 15:30:01 rc_service: service 6930:notify_rc restart_letsencrypt
Dec  6 15:30:07 kernel: /usr/sbin/acme-client: https://acme-v01.api.letsencrypt.org/acme/new-authz: bad HTTP: 403
Dec  6 15:30:07 kernel: /usr/sbin/acme-client: transfer buffer: [{ "type": "urn:acme:error:unauthorized", "detail": "No registration exists matching provided key", "status": 403 }] (120 bytes)

Error 403 sound like an authorization denied error. Make sure of a few things:

1) that you aren't forwarding port 80 or 443 to another server on your LAN (I assume one of these is used by the validation process

2) That you aren't behind a dual NAT, blocking access from the outside to your router

3) That you aren't in a country where Let's Encrypt is being blocked (I don't know for instance if China does).

4) That your DDNS is working properly (note: I suspect that DNS-o-Matic might not work properly with LE)

Beyond that, best to contact Asus's support, as they do not monitor this forum.