What's new

Beta Asuswrt-Merlin 3004.388.4 beta is now available

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Status
Not open for further replies.
Honestly, as I said before the only variable here is moving from GT-AX6000_388.2_2_stable to GT-AX6000_3004_388.4_beta2. I guess that I will just have to revert back to the latest stable.


just tried to help.
Cheerz!
 
RT-AX86S. Using 388.4_B2 since release and no issues with my simple setup. Works good.
 
just tried to help.
Cheerz!
Not sure why you took it the wrong way. I had even liked your post trying to help! You must have woken up on the wrong side if the bed or not yet taken your medicine!
 
Last edited:
Sorry to post about this here again but I am pretty confident that this is a firmware problem as my settings (below) have not changed one bit from my previous ones (and I try to keen things as close to default as possible) and I have only been unable to get Plex remote access with this version of AsusMerlin and with no other changes to my plex server either. Why has it stopped working as soon as I upgraded to this beta?

View attachment 52287View attachment 52288View attachment 52289


I am on the latest beta and have no issue with Plex remote access. I don't have any ports manually opened . . . just upnp enabled. I am running Plex on a Synology NAS in a docker container and have a GT-AX6000.
 
I am on the latest beta and have no issue with Plex remote access. I don't have any ports manually opened . . . just upnp enabled. I am running Plex on a Synology NAS in a docker container and have a GT-AX6000.
Thanks for confirming that it is working on yours with the same router model as mine. I will try another factory reset and see.
 
Thanks for confirming that it is working on yours with the same router model as mine. I will try another factory reset and see.
You were told 2 times by now - just disable port forwarding and leave only UPnP.
Then report back...
 
I am on the latest beta and have no issue with Plex remote access. I don't have any ports manually opened . . . just upnp enabled. I am running Plex on a Synology NAS in a docker container and have a GT-AX6000.
What Synology do you have? I’m ds1821+ and two extensions. Off topic.
 
Plex is working for me, but that isn't much help to you since I have 2_2 on the server side and this beta on the client side. And my plex settings are the bog standard remote access, but I mostly run it over VPN.

There were two things that caught my eye though. One was that your plex server was getting a public IP address from your ISP. You must mean that your router is getting a public IP address.

Verging on OT: The other is that you are forwarding to a 192.168.1.10 address, so your internal subnet is not the default. Personally, I avoid 192.168.0.x, 192.168.1.x with a passion. I'm running my plex server in a docker image on a truenas box, and it pulls a different IP address than my truenas box. It could be that your plex server is on a different address than that 1.10 one.
 
Thanks for confirming that it is working on yours with the same router model as mine. I will try another factory reset and see.
I had a problem with Plex port forwarding a while ago on my router (AXE16000). What I did was kept the internal port default but used a different external port...worked a charm
 
Odd you having those plex issues. My plex on synology ds218j is working without any issues at all. I have tried UPNP enabled and port forwarding disabled and also enabled. I did not have to restart my plex server after router beta 2 install. I did notice when I logged into my plex server I had to actually sign in and once I did it worked well.

Plex working good behind VPN as well (i modified the vpn config file with "route plex.tv 255.255.255.255 192.168.x.x" <-- synology ip).
As said above the trick with plex is to use the default internal 32400 port while using a different external port (i use port 50000). I had so much headache figuring that out and how to route plex through my vpn provider. Took me long to figure it out.

Even with my port forwarding turned on plex and synology mobile apps are accessible outside of my network without any issues. Very happy camper :)
 
Maybe it´s time to open a "PLEX-Thread"...?;)
 
1691827458197.png


Working flawless
 
Odd you having those plex issues. My plex on synology ds218j is working without any issues at all. I have tried UPNP enabled and port forwarding disabled and also enabled. I did not have to restart my plex server after router beta 2 install. I did notice when I logged into my plex server I had to actually sign in and once I did it worked well.

Plex working good behind VPN as well (i modified the vpn config file with "route plex.tv 255.255.255.255 192.168.x.x" <-- synology ip).
As said above the trick with plex is to use the default internal 32400 port while using a different external port (i use port 50000). I had so much headache figuring that out and how to route plex through my vpn provider. Took me long to figure it out.

Even with my port forwarding turned on plex and synology mobile apps are accessible outside of my network without any issues. Very happy camper :)
@Plak (fellow camper) you are an absolute star. Changing the external port has definitely done the trick (which is quite strange as not needed to that previously). Happy now that remote access seem to be working without needing to go through a full reset again. It would be fantastic if you could kindly PM a bit more details as to how you have changed the VPN config file (forgive me for being a bit clueless here) and thank you again to all for their great advice on how to troubleshoot this. Back on topic now....Phew.
 
I expected B3 today, it seems like no b3 today.
Will let the system run some more then.
Just yesterday I reboot it.
 
Please be patient. It will come out when it's done...
388.4_beta2_onlinetime.JPG
 
I move up one of my routers fron 388.2.2 to 388.4.beta.

The only issue I have is this in my log…

Aug 11 17:42:27 rc_service: watchdog 2235:notify_rc stop_aae
Aug 11 17:42:27 rc_service: watchdog 2235:notify_rc start_mastiff
Aug 11 17:42:27 rc_service: waitting "stop_aae" via watchdog ...
Aug 11 17:42:27 custom_script: Running /jffs/scripts/service-event (args: stop aae)
Aug 11 17:42:28 custom_script: Running /jffs/scripts/service-event (args: start mastiff)
Aug 11 17:42:28 Mastiff: init
 
Status
Not open for further replies.

Similar threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top