|
Quoted: Quoted: Error 500 is on the server side. -Foxxz i understand that, but is everyone on arfcom having server 500 errors? im not. but it could just be that particular page/script he is hitting. The server logs would also show error 500s. I usually look for them in my logs to indicate there is a server malfunction or as an early warning sign someone is trying to use exploits. -Foxxz |
|
I don't know how this site is set up, but as a site admin elsewhere, the issue with www.ar15.com showing a different certificate is one of a shared IP address. Basically, afcom is on an IP say, 127.0.0.1. Other sites can go on the same IP as long as the server uses "www.ar15.com" plus 127.0.0.1 to identify what site the user wants. Suddenly getting another site (you get a place called "arl" if you continue with the cert) on the same IP when in secured mode, means someone put a certificate on the OTHER site, and neglected to move the IP address to say 127.0.0.2. Secured sites, MUST be on their own IP because the portion of the connection that uses "www.ar15.com" plus 127.0.0.1 to identify, is also encrypted. The server then defaults to the site that is encrypted on the IP. You'll need to go to the server administrator, or someone who has direct access to the configuration on the web server(s) that run ARfcom if my guess is right. For ordinary users, just stop trying to visit the forum section of the site in secured mode and it'll work fine. Something to look into... it looks like the certs or IPs or hostnames are mixed up on the server. (It's not malicious, but just a typeo type mistake on the part of the admin.) |
