| 1:20 am on May 6, 2014 (gmt 0)|
|I can access the website with https from an internal computer, but external systems can only access with http. |
What happens when you try? Browser time-out, error message-- either from browser or from server-- or something else entirely? I assume there's no information in access logs, or you'd have said.
The main purpose of this question is to buy time until someone who speaks Apache comes along ;) But the answer will do no harm and might be useful.
| 7:14 am on May 6, 2014 (gmt 0)|
If you chose the "Standard" (69.99) SSL Cert that only verifies domain ownership (not your organization), then you'll need to use the intermediate certificate GoDaddy provides and chain them together.
Without it, you'll get an "Invalid SSL" warning.
Try this: [support.godaddy.com ]
| 2:00 pm on May 6, 2014 (gmt 0)|
When I try from outside I just get a browser time-out / "Page cannot be displayed". And I have checked the access logs and they indicate nothing, so I am assuming that means the request is not reaching the server.
-thomcraver: I have done this. I have the main SSL, the intermediate and the key all linked in the conf file. I do not receive an SSL error. When viewed internally the little lock is green and all is good. So I believe the certificate itself is ok.
| 5:56 pm on May 6, 2014 (gmt 0)|
config file says
right? Are all applicable Virtual Hosts set the way they're supposed to be? (I realize both of these are in the category of "Is the machine plugged in?")
"Local connection" = direct, physical connection that bypasses the internet entirely?
I don't think it can be a certificate issue, because that would lead to a browser error message saying exactly what the problem is and asking if you want to back off or forge on ahead.
phranque? where'd you go?
| 7:56 pm on May 8, 2014 (gmt 0)|
Lucy- yes the config file is set to listen on 80 and 443. I have tried just having 443 and that doesn't seem to make any difference.
As far as the Virtual Hosts, I'm afraid I don't know Apache well enough to say a firm yes, however I don't *think* I changed anything on them, so I see no reason for that to be the problem since it did work in the past.
And correct, you only receive a "page cannot be displayed" error, nothing about security.
I apologize for my ignorance on this issue. That is why I am seeking help :)
| 9:37 pm on May 8, 2014 (gmt 0)|
In your Vhost config, are you binding 443 to an external IP address or to an internal IP address? Or are you simply using :443 in the config?
| 9:57 pm on May 8, 2014 (gmt 0)|
I have also tried:
Neither seems to change anything.
| 11:09 pm on May 8, 2014 (gmt 0)|
The server name goes inside this envelope.