ER706W referer check failed related issue
ER706W referer check failed related issue
Recently I posted a reply on a thread that was addressing the same bug on a different router.
@clive_a advised me to create a new thread by being at the same time very dismissive saying that the issue was fixed in a new firmware release for ER707-M2 even though I explained its happening with a different router "ER706W" which is what I own.
I did my due diligence and checked the new firmware updates to find out that that fix was only addressed for that certain router in a new firmware. even though all the routers that probably share the same hardware (like mine) would have the same issue most probably. incompetence.
I am relinking my same post again so its a new thread.
ps: @clive_a no its not a browser cache issue. it happens with any device try to browse the synology https interface.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @Pink_Waters
Thanks for posting in our business forum.
Pink_Waters wrote
Update, after reseting the router and getting rid of the problem, i am back to the original problem where if i go to the HTTPS url for my local synology, i get check referer failed.
The referer check failure is estimated to be fixed in the V5.15.X.Y release. Please refer to the release note in future firmware updates.
- Copy Link
- Report Inappropriate Content
Hi @Pink_Waters
Thanks for posting in our business forum.
Pink_Waters wrote
Recently I posted a reply on a thread that was addressing the same bug on a different router.
@clive_a advised me to create a new thread by being at the same time very dismissive saying that the issue was fixed in a new firmware release for ER707-M2 even though I explained its happening with a different router "ER706W" which is what I own.
I did my due diligence and checked the new firmware updates to find out that that fix was only addressed for that certain router in a new firmware. even though all the routers that probably share the same hardware (like mine) would have the same issue most probably. incompetence.
I am relinking my same post again so its a new thread.
ps: @clive_a no its not a browser cache issue. it happens with any device try to browse the synology https interface.
Synology?
What is the diagram like?
What config do you configure to reproduce the issue?
How do you reproduce the issue?
- Copy Link
- Report Inappropriate Content
I did your solution #2 here, adding the synology FQDN in the domain field. then everytime i go to the synology address i get a tplink login page for the standlone mananagement of the gateway. After disabling the DDNS and even removing the DDNS config, the redirection is still happening.
- Copy Link
- Report Inappropriate Content
Hi @Pink_Waters
Pink_Waters wrote
I did your solution #2 here, adding the synology FQDN in the domain field. then everytime i go to the synology address i get a tplink login page for the standlone mananagement of the gateway. After disabling the DDNS and even removing the DDNS config, the redirection is still happening.
I required the details yet you did not provide them. I am not able to provide any suggestions regarding what you described.
This is another description of the issue which seems to be the port forwarding instead of the referer check. Literally, if you want to get this resolved, be cooperative and specific.
And the DDNS was merely a template, an example. It does not mean you use it in your case where your DDNS service provider might be different.....
- Copy Link
- Report Inappropriate Content
I already explained in my first post to the letter what happened. When I tried to go to the synology that I have https web portal. I would get the referer error. I searched and found your post then did your fix and that caused the issue I described having right now where now instead I get redirected to the gateway standalone portal. Disabling or removing that custom ddns doesn't fix the redirection.
- Copy Link
- Report Inappropriate Content
I had to reset the router in order to resolve the bug that the mod here was dancing around acknowledging it.
- Copy Link
- Report Inappropriate Content
Update, after reseting the router and getting rid of the problem, i am back to the original problem where if i go to the HTTPS url for my local synology, i get check referer failed.
- Copy Link
- Report Inappropriate Content
Hi @Pink_Waters
Thanks for posting in our business forum.
Pink_Waters wrote
Update, after reseting the router and getting rid of the problem, i am back to the original problem where if i go to the HTTPS url for my local synology, i get check referer failed.
The referer check failure is estimated to be fixed in the V5.15.X.Y release. Please refer to the release note in future firmware updates.
- Copy Link
- Report Inappropriate Content
@Clive_A Sounds good, Thanks! are you talking about omada controller or router firmware?, becasue the latest router firmware is on 1.1 and omada controller is already on V5.15
- Copy Link
- Report Inappropriate Content
Hi @Pink_Waters
Thanks for posting in our business forum.
Pink_Waters wrote
@Clive_A Sounds good, Thanks! are you talking about omada controller or router firmware?, becasue the latest router firmware is on 1.1 and omada controller is already on V5.15
V5.15.X.Y is not V5.15. It means the other versions in V5.15.X.Y. Not meaning now. I am aware it is V5.15 now.
Firmware of the router.
- Copy Link
- Report Inappropriate Content
To be frank I am not sure if there is a language barrier or what but most of what you say make less sense the more you elaborate.
Are you saying the fix will come in firmware 5.15ish for the router? If the router firmware right now is on v1 that means the fix will be here in 2 years give or take? What are we talking about here?
Also I did some digging on this issue and seems like when I go to my local synology https url. While it's showing me referer check failed , the ssl cert is tplink. So I am not sure, is the gateway intercepting the ssl connection?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 235
Replies: 13
Voters 0
No one has voted for it yet.