@Clive_A they match for your infromation. Also, I followed the steps provided from previous post. Added DynDNS record and disable it. How everything works great. However, I schedueld it to reboot on a nightly basis. After the reboot, things gone very weird this morning by not allowing me to even get into the default IP and only allowing through domain name. So I went in and deleted DynDNS record and for some strange reason, everything now works like ER605.

  @Clive_A 

"So are you saying that it is working flawlessly now?" Yes, it seems to work flawlessly now. However, I'm not exactly sure what I have done. Anything I can do to help?

"Nothing wrong with it since you tried the previous steps/suggestions?" Yes, everything seems to work fine now. Let's wait until tomorrow morning's schedule reboot to double confirm.

"Or you gotta manually adjust it to make it work okay after every reboot?" No, it seems not the case.

Steps I've done.

  @SakamotoBlog 

What's the solution for [Referer check failed] for the ER707-M2? 

I have the same problem with six new ER707-M2 devices running firmware ER707-M2(UN)_V1.6_1.2.0 Build 20231214.

All of the devices are running in stand alone mode and don't have a controller configured.
Each of the ER707-M2 devices has a static internet ip address on the WAN interface

They do NOT use DDNS.

My internet subnet is added to the list of address permitted for remote management.

I receive the [Referer check failed] when attempting to remotely manage any of the devices from a web browser using the static ip address of its WAN interface. This occurs with Chrome and Firefox.

Please advise.