Archer AXE75 https connection for management fails at initial login
Hi,
Logging into the console via the web browser using 192.168.0.1 went through setup with no issues. Going into 'Advanced' - 'System' - 'Administration' and then under 'Local Management' I select Enable for Local Management via HTTPS:, then log off.
Go to log back in to check the https: setting and I get warnings from the browser (used Edge and Firefox) that https: connection cannot be established and to 'go back' or proceed forward under risk. Under Firefox, proceeding forward, eventually the https connection gets established. No so using Edge (Edge and Windows 11 at latest versions as of 3/2/24).
Perhaps I am missing something here but I would expect that using https://192.168.0.1 would initially establish the request and then succeed in arriving at the encrypted connection without these warnings.
So what's happening here?I would not expect to get this warning. I do not get these warning when going to other https enabled sites.
And more importantly am I doing something incorrect in the configuration setup?
Explanations and help would be sincerely appreciated.
Thanks
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Been covered before here. Use https in search area or look up "How to login to the TP-Link Router's web management page when HTTPS is enabled"
Has to do with certificates.
- Copy Link
- Report Inappropriate Content
I appreciate your reply, but there is NO solution covered by the forum. Many questions are posted, but no solution.
So I tried 2 different OS's and 4 browsers. And everyone of them indicate that the certificate from the Archer AXE75 is invalid.
Some one at TP-Link should check the certificate that is loaded by default in the routers. The sheer volume of threads asking about this issue certainly indicate a systemic problem with https: enabled for management from the intrenal network side.
- Copy Link
- Report Inappropriate Content
It is not a web site that needs a certificate for security. It is your own router that you are linking to.
- Copy Link
- Report Inappropriate Content
Well, here again, I believe you are not recognizing the issue. Look at the manual, or other articles for the http error - the router has, and presents you the web page for adminstrative login. You get to router's web page by using https://tplinkwifi.net or https://192.168.0.1 Se the image below - this is from the router's management page.
Then you encounter the certificate errors as explained and shown previously. There is a certifcate from the router, but something is wrong with the certificate or it is incomplete. This certificate error shows on 4 different browsers operating on 2 different OS's. This is issue is not on the user side - it is on the router side.
If you are an associate of tp-link or AXE routers, please elevate this issue to the proper group. Or respond with the way to submit an error issue. Thank you
AXE5400 - Archer AXE75 - Tri-Band Wi-Fi- 6E Router Configuration Page
- Copy Link
- Report Inappropriate Content
I am not with TP Link.
As I understand, the browsers are giving the error because the certificate is self signed as that was a security risk when going to a web site. If you check, other router companies such as linksys, netgear, ... get the same error.
My position is it is your router and not a web site so the error message is bogas.
- Copy Link
- Report Inappropriate Content
Thanks a lot for @ArcherC8 's help, please also refer to: Why TP-Link HTTPS web interface is detected as unsecure by some web browsers?
- Copy Link
- Report Inappropriate Content
Hmm . . . can't post a reply. The site is always indicating invalid links or errors. So will try in short sections.
Hi, I did read the article. Thanks. Not sure why it did not show on initial search.
But, the article confirms what I have been tying to identify and solve. That the certificate (router) is the issue because it is self signed. Properly functioning browsers should only accept certificates that are valid and have a verified CA chain.
Tp-Link should purchase for certificates from a registered CA authority. And yes that costs money and no doubt will be passed on in pricing. But this solves the failure issue. If Tp-link corrected this issue the majority of https errors with browsers would dissappear. Browsers would work in https connections.
- Copy Link
- Report Inappropriate Content
In 2018, the IETF finalized and published TLS v1.3 which improved web performance and security by, removing out of date and insecure TLS v1.2 cipher suites. TLS v1.3 is designed to secure against all known TLS v1.2 vulnerabilities. Shouldn't the router (all products with TLS capability) be at TLS v1.3, after all it is 2024 not 2018.
- Copy Link
- Report Inappropriate Content
Sorry for the series of posts . . .
And finally another issue is the Tether app. Since running into the certificate error, I thought to switch to the Tether app in hopes of a better interface and more secure connection. After loading the app, the app discovers AXE 75. When selecting the router to connect to the app returns the error that the app does not support that router and to use web to connect.
Thank you both for your replies and time.
Squeeks
- Copy Link
- Report Inappropriate Content
The question I would have is would everyone's router need a different certificate since it would be handled like a different website?
I do not consider this as security risk just a bit of a pain sort of like Apple's mac address changing on their devices was.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 882
Replies: 10
Voters 0
No one has voted for it yet.