Modernbill/FraudGuardian - Dead order form, SSL possible issue?
Now I have used FraudGuardian for months and never had any issues. This all started Thursday. I believe it was late Friday when Michael at MB apologies and said everything was up 100%. Doing more test I found that was incorrect and anyone trying to place an order with FraudGuardian enabled always got "page can not be found". Now this page appears as MB sends info to FraudGuardian and awaits FraudGuardian to send the results back to it.
Being as Michael said it was up and working we both started troubleshooting my server. We did test with the following items:
[1] Firewall off, FraudGuardian on with varilogix on
[2] Firewall off, FraudGuardian on with varilogix off
[3] FraudGuardian server IPs in my firewall allowed list
Keep in mind if FraudGuardian is set to off in MB orders work fine with varilogix. I tailed all logs and found no errors. The only remotely close error we found was the following which was located in /var/log/emaxhosting.com
[24/May/2005 09:03:06 09291] [info] Connection to child 13 established (server emaxhosting.com:443, client 68.39.xx.xx)
[24/May/2005 09:03:06 09291] [info] Seeding PRNG with 1160 bytes of entropy
[24/May/2005 09:03:06 09291] [info] Connection: Client IP: 68.39.xx.xx, Protocol: SSLv3, Cipher: RC4-MD5 (128/128 bits)
[24/May/2005 09:03:06 09291] [info] Initial (No.1) HTTPS request received for child 13 (server emaxhosting.com:443)
[24/May/2005 09:03:06 09291] [info] Connection to child 13 closed with unclean shutdown (server emaxhosting.com:443, client 68.39.xx.xx)
[24/May/2005 09:03:06 09296] [info] Connection to child 18 established (server emaxhosting.com:443, client 68.39.xx.xx)
[24/May/2005 09:03:06 09296] [info] Seeding PRNG with 1160 bytes of entropy
[24/May/2005 09:03:06 09291] [info] Seeding PRNG with 1160 bytes of entropy
[24/May/2005 09:03:06 09291] [info] Connection: Client IP: 68.39.xx.xx, Protocol: SSLv3, Cipher: RC4-MD5 (128/128 bits)
[24/May/2005 09:03:06 09291] [info] Initial (No.1) HTTPS request received for child 13 (server emaxhosting.com:443)
[24/May/2005 09:03:06 09291] [info] Connection to child 13 closed with unclean shutdown (server emaxhosting.com:443, client 68.39.xx.xx)
[24/May/2005 09:03:06 09296] [info] Connection to child 18 established (server emaxhosting.com:443, client 68.39.xx.xx)
[24/May/2005 09:03:06 09296] [info] Seeding PRNG with 1160 bytes of entropy
Michael says no one else has issues with FraudGuardian. I find it odd that the same time their service mess up something out of the blue happens to my server that enables it to NOT work with FraudGuardian but work fine with anything else.
Does anyone have any other clue or suggest I might try to fix this issue? BTW acunett also looked at this and didn't find anything wrong.
