33 reputation
5
bio website
location
age
visits member for 2 years, 11 months
seen Jun 23 at 14:39

Feb
27
answered Postfix store emails
Feb
9
awarded  Popular Question
Oct
28
awarded  Editor
Oct
10
answered UnKnown can't find <hostname>: Non-existent domain
Oct
10
answered Ubuntu CVE-2013-1635 PCI DSS
Oct
10
comment CentOS partition reporting out of space
delete files from partition/volume group!
Oct
10
awarded  Supporter
Oct
10
answered Twin debian servers
Oct
10
answered proper DNS setup for Dedicated server
Oct
10
answered How can I check vps server security when my hosting has been met attack
Oct
10
awarded  Teacher
Oct
10
answered CentOS partition reporting out of space
Oct
10
awarded  Scholar
Oct
10
accepted Malware removal from the code
Oct
26
asked Malware removal from the code
Oct
4
answered Hostname and SSL (apache) issue on Debian
Oct
3
comment Hostname and SSL (apache) issue on Debian
Now i am still stuck with the issue "[Tue Oct 02 22:40:32 2012] [error] Hostname linemnt01.tap.pt provided via SNI and hostname moclm.tap.pt provided via HTTP are different" Some of the guys are calling it an apache2.2.X bug now where could i get 2.1.x.LOL
Oct
3
comment Hostname and SSL (apache) issue on Debian
This (moclm) refers to the “service”. Access to moclm.tap.pt (either internally or from the web) is made via a reverse-proxy, which then forwards the requests to the machine linemnt01."
Oct
3
comment Hostname and SSL (apache) issue on Debian
"The server LINEMNT01 is behind a DMZ (behind a firewall). Access to it is possible via the firewall (access controlled) either directly for management purposes, or via reverse-proxy (and the firewall) for service availability. The name linemnt01.tap.pt resolves to 172.17.128.77 and my opinion is that it should remain like that because it refers to the host itself. On the other hand, moclm.tap.pt resolves to 10.129.9.142 (from internal networks) and to 91.198.90.142 (from the internet).
Oct
3
comment Hostname and SSL (apache) issue on Debian
Yeah sorry i missed <virtualhost> directive. The config is OK. apachectl configtest say OK. I dont know it could be because of this name mess may be. The server is behind the dmz with reverse proxy to forward the requests. and the server has two DNS records in the internal name server. here is what i heard from the network team in the Portugal office.