Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 40
  • Last Modified:

Web site is not accessible.

Dear EE,

My web site is not accessible through URL.

https://abc.com

But it is accessible through IP.

Thanks
0
Netsol-NOS
Asked:
Netsol-NOS
1 Solution
 
Seth SimmonsSr. Systems AdministratorCommented:
is there a DNS A record for the site?  or an entry in your hosts file?
does the host name resolve through ping or nslookup?
what happens when you try to access by host name through a browser?
0
 
Netsol-NOSAuthor Commented:
is there a DNS A record for the site?  or an entry in your hosts file?
Reply:- I do not confirm this, but will check and get back to you.

does the host name resolve through ping or nslookup?
Reply:- How can i do this ?

what happens when you try to access by host name through a browser?
Reply:- Page Can not be found.
0
 
Seth SimmonsSr. Systems AdministratorCommented:
from a command prompt:
ping abc.com
nslookup abc.com

Page Can not be found.

that is something different
that means you do have a DNS record and it is resolving; the web server returned a 404 not found so it's a configuration issue on the web server.  what is it supposed to show?
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Netsol-NOSAuthor Commented:
The IE is not showing 404.

The web page is can be accessible through IP address.

Let me share the nslookup results
0
 
Seth SimmonsSr. Systems AdministratorCommented:
you said the page cannot be found; that is the 404 status code
if IE friendly messages are enabled it will just show that and you probably don't see the 404 but that's what it is
0
 
Netsol-NOSAuthor Commented:
THE PAGE CANNOT BE DISPLAYED

with both HTTP and HTTPS
0
 
Seth SimmonsSr. Systems AdministratorCommented:
that's different then
does the name resolve through ping or nslookup?
0
 
Netsol-NOSAuthor Commented:
when we click http://xx.xx.xx.xx/app

its works fine.

when we click https://xx.xx.xx.xx.app it is not working .
0
 
Seth SimmonsSr. Systems AdministratorCommented:
is there ssl certificate installed and the site bound on port 443?
you won't get https connection automatically
0
 
Netsol-NOSAuthor Commented:
Please see that the URL for external is different.

For example
Web Application is installed on server which has IP address 10.10.10.10 and its machine name is BAKI.microsoft.com

we bind this application with live URL which is www.abc.com for external users.

Now www.abc.com is not working with both (HTTP and HTTPS)
through IP it is working and if we add HTTPS://XX.XX.XX/ not working.
0
 
Matthew BorrussoCommented:
You need to talk to who ever configures the web server.
Assuming your firewall and rules are correct, as you say you can reach it via IP address.
1. check the web server and confirm that the site itself is not bound to the name. This is common on web servers servicing multiple sites.
2. assuming this is not the case since it is responding on the ip itself. your dns records need to be in order.
So from the outside, you would need to have an A record that points to the ip address.
You can verify this by doing the following.
from a command prompt:
nslookup
then: server 8.8.8.8 (this points you to a public google dns server).
then just type your fqdn for outside users ie: meh.domain.com
if this responds with the public ip of the web server, your in good shape, if not, your dns is not configured correctly for public resolution.

3. lastly, https is funny. If you have multiple names attached to the website for internal and external use.. say per the example meh.domain.com and then something internal like meh.domain.local, you will need to change your certificate and do like a UC cert from a public authority (godaddy, digicert, VeriSign).
This way when you go to access the server on https you do not get the untrusted error.I would recommend using the public name as the common name and adding a SAN (Subject Alternative Name) for the internal. Make sure the provide will allow not public entries if this is the case, only cause I have seen that happen.

Another option, purchase a domain name for services only. get the certificate for one name.. then you can use the same name by creating the zone internally and pointing the record to the private address and create the record in the public using the public address. there are many ways to skin this, it just comes down to what's best for you and for the business.

Luck,
Matt
0
 
Netsol-NOSAuthor Commented:
Dear Matt,

Thanks for your reply. this is also we are discussing with Seth Simmons.

Thanks
0
 
Seth SimmonsSr. Systems AdministratorCommented:
let's go back to my previous question that was not answered
can you resolve the site name using ping and nslookup?
0
 
Netsol-NOSAuthor Commented:
Dear Seth,

Problem has been resolved.
SSL certificate was expired.

Thanks
0
 
PberSolutions ArchitectCommented:
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.

I have recommended this question be closed as follows:

Accept: Netsol-NOS (https:#a40611828)

If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.

Pber
Experts-Exchange Cleanup Volunteer
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now