Conert Vbulletin Forum to Https

Applies to self-hosted versions of:
vBulletin 3; vBulletin 4; vBulletin 5;
Cloud sites have https enabled by default and you do not need to do anything.

This FAQ explains how to convert your vBulletin forum to use secure https (SSL) rather than http, and why you might need to.
Note: This guide contains links to external sites. vBulletin Solutions is not responsible for the content of external links and cannot be held responsible for the accuracy of information contained on them.

https stands for Hyper Text Transfer Protocol Secure. It is the secure version of http, the protocol used for sending data between your browser and a website. It means all communications between your browser and the website are encrypted. The ‘S’ stands for secure. Web browsers will usually display a green padlock to indicate that a secure connection is in place. For https to work, an https certificate needs to be installed on the server.

https uses a public and private key system. Data that has been encrypted with the public key can only be decrypted by the private key and vice-versa.
When a web browser connects to a webpage via https, the server sends its https certificate to the browser. This certificate contains the public key needed to begin the secure session.

Data sent over regular http connections are sent in plain text and could in theory be read by anyone who intercepts the connection. With an https connection, the data is securely encrypted, meaning that even if someone intercepted it, they wouldn’t be able to read it.
Starting in January 2017, Google’s Chrome browser will begin to mark non-https pages as ‘Insecure’. This warning may put off visitors to your site. Other browsers are expected to follow suit in due course.
More details on this can be found HERE
Additionally, Google is now using https as a ranking signal, meaning not having https could harm your site’s ranking in Google. More details on this HERE.

Starting in January 2017, Apple is enforcing APP TRANSPORT SECURITY (ATS) for all new apps signed after that date. More details on this HERE. This means that apps signed after January 2017 must use secure https when making API calls and connecting to web services.
We have updated vBulletin Mobile Suite to version 1.13 to publish apps using HTTPS, to meet Apple’s App Transport Security requirement. After Jan. 1, you will not be able to submit updated apps to the iTunes App Store using earlier versions of Mobile Suite. Your current apps are fine and will continue to work with your site; you just won’t be able to update them until you use v1.13.

The first thing you will need is an https certificate. In most cases, the first port of call for this will be your web host. https certificates are commonly referred to as SSL certificates, although these days they are usually actually TLS certificates. These are protocols used for https. TLS stands for Transport Socket Layer, and is the successor to SSL, which stands for Secure Socket Layer. You don’t really need to concern yourself with these two protocols, but if you are interested, technical details can be found HERE.
In most cases, your host will make a small charge for an https certificate. This is generally an annual fee which needs to be renewed. Failure to renew it will cause users to receive a warning in their browser that the certificate has expired, so it’s vital to keep this up to date. https certificates are generally tied to a specific domain. The certificate will need to be installed on your server – again, generally your host will do this for you.

You are not tied to buying the certificate from your host, however it is generally the easiest option if you’re not well versed in doing this type of thing. If you purcahse one from a third party, you will normally find instructions on your web hosts website for how to perform the installation of the certificate yourself. For example, one hosting company has a guide HERE. There is another guide HERE. Use these guides at your own risk – vBulletin does not endorse and has not tested any of the guides linked to here. If you are unsure – speak to your host, who should be happy to help.

The next step is quite simple. Log into your vBulletin AdminCP, and then follow the appropriate instructions below for your version.

vBulletin 3
Go to vBulletin Options > vBulletin Options > Site Name / URL / Contact Details.
Edit ‘Forum URL’ and add the ‘s’ into the URL.
For example, if your URL is, change it to

Then go to Settings > vBulletin Options > vBulletin Options > Server Settings & Optimization Options > Use Remote YUI
Set this to Google.

vBulletin 4
Go to Settings > Options > Site Name / URL / Contact Details.
Edit ‘Forum URL’ and add the ‘s’ into the URL.
For example, if your URL is, change it to

Then go to Settings > Options > Server Settings & Optimization Options > Use Remote YUI
Set this to Google.

vBulletin 5
Go to vBulletin Options > vBulletin Options > Site Name / URL / Contact Details.
Edit these three settings: ‘vBulletin URL’; ‘Login URL’; ‘Core URL’ and add the ‘s’ into the URL.
For example, if your URL is, change it to
NOTE: Do not remove the word ‘core’ at the end of the core URL. You will break your site!

Then go to Settings > Options > Server Settings & Optimization Options > Use Remote jQuery
Set this to Google.

The key to all three vBulletin versions is that all you do in the URL settings is change http to https. Do not alter any other part of the URL.

Once you have changed these settings, go to AdminCP > Maintenance > General Update Tools, and rebuild the styles. (In vB3 this is AdminCP > Maintenance > Update Counters). Leave the default settings and just run this update tool.

Your site should now load and run normally when using https in the URL. However, you now need to redirect any http traffic to https, so that everyone using your site uses the secure connection.
Again, in most cases, the simplest way to arrange this is to ask your host to configure it for you. They shouldn’t charge for doing this, and it won’t take them very long.
If you’d rather do it yourself, it involves playing about with special files used by different types of server software – For instance, a server running ‘Apache’ will use an ‘.htaccess’ file, whereas a server running IIS will use a ‘web.config’ file. If you don’t know which server software your server is running, speak to your host. GoDaddy have a useful guide to making these changes HERE. However, these files can be quite tricky to work with, and an incorrect entry will break your site. It’s much simpler to get your host to do it!

You shouldn’t encounter any difficulties and your site should be showing a green padlock in most browsers.
You may run into issues with ’embedded images’, where people have embedded external images or videos from third party sites into your posts, where those sites are or were not using https. These will trigger what is called a ‘Mixed Content Warning’ in the padlock area of the browser. In practice, what this means is that such embedded images or videos will not show and users may just see a blank space. You should aim to convert these images to attachments, subject to copyright, though this will be a manual task and can be fairly arduous if there are lots of them. Alternatively you can manually edit the embedded URL to change it to https. This will work for major sites like YouTube, but on some sites it may not work if https is not available. There are some third party add-ons that can help with this problem such as THIS ONE, however vBulletin cannot provide official support for third party code.