I am trying to integrate FPX payment gateway provided by Paynet. During implementation, Paynet feedback that my website is SNI enabled which currently not supported by Paynet. They requested to turn off SNI in my website.
I am not very familiar with this SNI thing but I had did some googling and found that it has something to do with SSL certificate too. I heard that some certificate is able to solve this issue and therefore I am opening this ticket.
Anyway solution that you could advice on this issue? By the way I am currently using a free SSL certificate provided by Letās Encrypt.
My domain is: gloo.com.my
The operating system my web server runs on is (include version): Linux
My hosting provider, if applicable, is: AWS
I can login to a root shell on my machine (yes or no, or I donāt know): Yes
Iām using a control panel to manage my site (no, or provide the name and version of the control panel): Yes, version 86.0.16
SNI basically is the configuration (support) that allows you to enable mutiple SSL / https websites/virtualhost on 1 IP.
If your Payment processor require you to turn off SNI, you have two options:
Make this website your default virtualhost for SSL/TLS VH.
Add a new Elastic IP for your AWS instance (additional charge will apply, IP price charged by hour within AWS) and assign this website to the new IP (on the same server). This is basically means you'll bind that IP to this website.
P.S. I don't know if that's an error or not, but it's awkward a payment processor won't allow their client websites to use SNI.... (As most... 99%? online devices around the world support SNI)
Yes, I am able to go to WHM > Manage SSL Hosts. I already make it Primary and confirmed the āIs SNI Requiredā column is āNoā for the Primary host.
But I am still seeing the message āThis site works only in browsers with SNI support.ā when I run on ssllabs.com.
Does that means the configuration is still incorrect?
I actually realized that the reason this might not be working is that you're running Engintron on top of cPanel. Since it's a third-party plugin, I'm not really sure how well it interacts with the default SNI configuration.
You might need to search around for how to configure the default SSL site on Engintron.
Or try fully reload Engintron/nginx - maybe you'll get lucky and it'll pick up the default SNI change.