Hi Daniel/Team,
I ran the command as you suggested - curl -vI https://www.amnetgroup.com
and it got below message.
[root@amdc2webl06 cert]# curl -vI https://www.amnetgroup.com
* About to connect() to www.amnetgroup.com port 443 (#0)
* Trying 52.167.221.189...
* Connected to www.amnetgroup.com (
On 06 Jan 2020, at 11:21, Adrian Gschwend wrote:
> If I add
>
> --
>
>Require all granted
>
> --
>
> This seems to work.
FSVO of “work” that include potentialy allowing access to every single file in
every singe directory on your system, sure.
You should never ever change
Dear group,
I finally started to migrate an Apache 2.2 config to 2.4. I've read the
migration document at
https://httpd.apache.org/docs/trunk/upgrading.html#run-time but I have a
hard time understanding the new access control model.
My config is mainly VirtualHost sections, in some of them I do h
Who is reporting a 502 exactly?
Perhaps we are missing the entire chain of events to properly diagnose
the issue.
If the problem is a client reporting an issue while proxying to this
server try manually to access ther web server yourself to discard
issues:
curl -vI https://www.amnetgroup.com
al
Hi Martin,
Below is the attribute of the existing working certificate. The only
difference is that the new certificate is of validity 2 years , but that
should not be an issue.
We performed below steps while updating -
1.openssl req -newkey rsa:2048 -nodes -keyout amnetgroup.com.key -out
amnetgro
Hi Daniel,
Yes the old one was also wildcard. And we had no alias setup earlier as
well. Though i tried this but it didn't worked either.
Regards
Sachin Kumar
On Mon, 6 Jan 2020, 13:50 Daniel Ferradal, wrote:
> Not sure about 2.4.6, but httpd IIRC recognizes wildcard certificates
> perfectly,
Not sure about 2.4.6, but httpd IIRC recognizes wildcard certificates
perfectly, in any case, you could try adding "ServerAlias
*.amnetgroup.com" to the virtualhost config. The old certificate was a
wildcard too?
El lun., 6 ene. 2020 a las 9:02, Sac Isilia
() escribió:
>
> Hi Daniel,
>
> The CN is
Hi Daniel,
The CN is *.amnetgroup.com . And the ssl certificate is wildcard
certificate that we got from Rapidssl. Till now the old certificate runs
fine with same config.
Regards
Sachin Kumar
On Mon, 6 Jan 2020, 13:25 Daniel Ferradal, wrote:
> The servername "www.amnetgroup.com" and CN in the
