Forum Discussion
Different common name ssl acces 403 forbiddent
Hi
I have an issue that access from internet got 403 forbident, domain is *.example.com and virtual server from internal used ssl common name intranet.example.com. Is that related to this common name ?
- Aswin_mk
Cumulonimbus
Hello,
The 403 forbidden—you don't have permission to access this resource' is displayed when a web server recognizes a user's request but is unable to allow additional access. Its not any SSL error. If its ssl error your connection will not secure. please check your connection is secure or not. Please work with app team and confirm why your request having permission issues
BR
Aswin- Anzine321
Altocumulus
i found root case, i have added specific uri path on browser and got response from server and some page did not load and after inspect browser and found error on console Failed to load resource: net::ERR_NAME_NOT_RESOLVED
- waqas34
Altocumulus
It seems like you're asking about an issue related to SSL certificates, common names, and a "403 Forbidden" error. Here’s a breakdown of possible causes and solutions:
Common Name and SSL Certificates
- The common name in an SSL certificate must match the domain name you're trying to access. If it doesn’t, browsers or servers might reject the connection or behave unexpectedly.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com