SSL certificates

SSL certificates are important to secure all traffic between SmartFoxServer 2X and its clients, via protocol encryption. This includes raw TCP/UDP, HTTP/BlueBox and WebSocket.

In order to deploy an SSL certificate you need two steps:

  • Associate a domain name with your server
  • Acquire an SSL certificate and deploy it on the server

Associating a domain name to your server

Server instances created under Overcast can be accessed via their public IP or AWS default domain name. If you want to customize the server's domain name you will need to acquire a domain name from a domain registrar and point the relative DNS record to the server's public IP address.

Alternatively, Overcast offers an integrated approach to assign custom domain names to servers. Follow these steps.

  1. Acquire a second-level domain name from a domain registrar, i.e.
  2. Associate the second-level domain name with the application under which your server runs, as described on the Creating a new application page (this applies to existing applications too, no need to create a new one).
  3. Associate a third-level name of your choice, i.e. tictactoe, to a server (if supported by the server type):
    • If the server has still to be launched, a specific step will be executed during the server launch procedure, as described on the Creating a new server page.

      Create Server / Domain Name
    • If the server already exists, in the application view click on the [Edit domain] icon in the Custom Domain column.

      Edit server domain name /1

      In the modal window showing up, enter the domain name and confirm.

      Edit server domain name /2

Deploying an SSL certificate

Once you have a domain name associated with the server you can add an SSL certificate to enable traffic encryption.

You can follow this SmartFoxServer guide to learn all the details about the process.

Accessing the AdminTool via SSL

If you want to access the AdminTool securely, after deploying the SSL certificate, you will need to perform an extra configuration step:

  • Connect to the AdminTool normally, using port 8080
  • Select Server Configurator > Remote Admin
  • Turn on the Use encryption switch
  • Restart SFS2X
admintool encryption

Now you can connect back to the AdminTool using port 8443, example: https://<my.domain>:8443/admin/. Make sure to set the same port number in the connection UI and turn on the encrypt option.

admin client ssl connection