Content Filter Block Page SSL

Hello,
Are there any guides on getting the Content Filter Block Page to work seamlesly when visiting sites with SSL? Currently on my setup it throws up a warning that "destinationsite.url doesn't supoort a secure connection with HTTPS" and when you click through it shows the Omada "Access Restricted" page but with the original destination site URL in the browser bar. I guess this is related to a local SSL certificate? Thanks.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content

Hi @Absent42
Some web browsers report TP-Link's HTTPS web interface as unsecure because the web interface uses a self-signed certificate for the domain tplinkwifi.net. Most browsers do not trust self-signed certificates because tplinkwifi.net is not an authoritative certificate authority (CA).
However, despite the self-signed certificate, the connection between the browser and the tplinkwifi.net server is secure and encrypted using TLS v1.2. The data transmitted between the client and server remains protected. Browsers may display a security warning, but there is no actual security risk to the user's computer or router.
For more details, please refer to this FAQ
Why TP-Link HTTPS web interface is detected as unsecure by some web browsers?
This error message indicates that access to such websites is likely being blocked by your router's filtering settings.
- Copy Link
- Report Inappropriate Content
Hi @Absent42
Thanks for posting here.
Below is the guide:
How to Configure Content Filter on Omada Router
Please share some screenshots of the error message page and the config pages for us to better understand the situation.
- Copy Link
- Report Inappropriate Content
Hi Vincent,
Yes, I have it setup as in the linked guide. When visiting a blocked SSL sites with the "Block Page" enabled in the "General Config" it behaves as below. Is there a method for getting rid of the SSL warnings?
- Copy Link
- Report Inappropriate Content

Hi @Absent42
Some web browsers report TP-Link's HTTPS web interface as unsecure because the web interface uses a self-signed certificate for the domain tplinkwifi.net. Most browsers do not trust self-signed certificates because tplinkwifi.net is not an authoritative certificate authority (CA).
However, despite the self-signed certificate, the connection between the browser and the tplinkwifi.net server is secure and encrypted using TLS v1.2. The data transmitted between the client and server remains protected. Browsers may display a security warning, but there is no actual security risk to the user's computer or router.
For more details, please refer to this FAQ
Why TP-Link HTTPS web interface is detected as unsecure by some web browsers?
This error message indicates that access to such websites is likely being blocked by your router's filtering settings.
- Copy Link
- Report Inappropriate Content
Vincent-TP wrote
This error message indicates that access to such websites is likely being blocked by your router's filtering settings.
Thanks for the reply. Regarding the above, that's the page the Omada Content Filter creates, the router is an ER7406.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content

Information
Helpful: 0
Views: 200
Replies: 5
Voters 0
No one has voted for it yet.