Discussions / FAQs
Error 111 (net::ERR_TUNNEL_CONNECTION_FAILED): Unknown error
This message is sometimes displayed when accessing an SSL page via a proxy (including our own payment page PayPal).
It is caused by Chrome being unable to render the 502/302 proxy response for some sites (Issue 119713).
Check your browsers Proxy settings. If possible remove the proxy and try again.
To change this setting, go to [chrome://chrome/settings/](chrome://chrome/settings/)
Then Click `Show Advanced Settings`. Scroll down to `Network` and click `Change proxy settings…` Uncheck `Automatically Detect`.
Posted by Andy Gambles about 2 years ago
Convert Private Key to RSA format
Some hosting systems require the Private key to be in RSA format rather than PEM. You can easily convert these files using OpenSSL.
Your private key file will usually start with
`-----BEGIN PRIVATE KEY-----`
an RSA private key will start with
`-----BEGIN RSA PRIVATE KEY-----`
To convert your key simply run the following OpenSSL command
`openssl rsa -in domain.key -out domain-rsa.key`
Posted by Andy Gambles about 2 years ago
How do I convert a PEM to PFX?
You can achieve this using OpenSSL (Mac OSX includes OpenSSL within Terminal.app) or our converter tool.
You should have the following files (Filenames are just for reference)
- Your generated CSR (cert.csr)
- Your Private Key File (key.pem)
- Your SSL certificate provided by the CA (cert.cer)
- The Intermediate Certificate provided by the CA (CA.cer)
**Servertastic Certificate Converter**
You can also use the [Servertastic Certificate Converter](https://tools.servertastic.com/certificate-converter)
**OpenSSL Commands**
Using OpenSSL run the following command
`openssl pkcs12 -export -in cert.cer -inkey key.pem -out certificate.pfx -certfile CA.cer`
This should output a certificate.pfx file.
Posted by Andy Gambles about 2 years ago
ssl_error_rx_record_too_long
This usually means the implementation of SSL on your server is not correct. The error is usually caused by a server side problem which the server administrator will need to investigate.
Below are some things we recommend trying.
- Ensure that port 443 is open and enabled on your server. This is the standard port for https communications.
- If SSL is using a non-standard port then FireFox 3 can sometimes give this error. Ensure SSL is running on port 443.
- If using Apache2 check that you are using port 443 for SSL. This can be done by setting the ports.conf file as follows
`— clip —
Listen 80
Listen 443 https
— clip —`
- Make sure you do not have more than one SSL certificate sharing the same IP. Please ensure that all SSL certificates utilise their own dedicated IP.
- If using Apache2 check your vhost config. Some users have reported changing `<VirtualHost>` to `_default_` resolved the error.
Posted by Andy Gambles about 2 years ago
CSR does not contain a wildcard domain as expected
Posted by Andy Gambles about 2 years ago
SSL Certificate does not work on Parallels Panel (Plesk)?
Once you have installed the certificate in Parallels Panel you need to then assign it to a web site. While managing your domain click
`Websites & Domains > Show Advanced Operations > Website Scripting and Security`
Tick the box `Enable SSL support` then from the drop down select the correct SSL certificate.
Posted by Andy Gambles about 2 years ago
Can I order a certificate for an Internal Server Name or Private IP?
Posted by Andy Gambles about 2 years ago
How to remove my saved card details?
Posted by Andy Gambles about 2 years ago
How do I change my Servertastic account email address?
Posted by Andy Gambles about 2 years ago