# Enabling HTTPS for Nakama Console **URL:** \ **Category:** Game Design\ **Tags:** authentication\ **Created:** [March 27, 2021, 2:39am UTC](https://forum.heroiclabs.com/t/enabling-https-for-nakama-console/1500 "2021-03-27T02:39:21Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![landrade](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.heroiclabs.com/landrade/32/575_2.png) [@landrade](https://forum.heroiclabs.com/u/landrade)\ **Post date:** [March 27, 2021, 2:39am UTC](https://forum.heroiclabs.com/t/enabling-https-for-nakama-console/1500/1 "2021-03-27T02:39:22Z")
Starting this new topic to ask if there is some how-to or best practice to enable HTTPS for the newer Nakama Console (version 3.+). It’s been more than a year since the last related questions and from there I couldn’t figure out the best way to configure our server with this security requirement. ---
**Author:** ![novabyte](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.heroiclabs.com/novabyte/32/1324_2.png) [@novabyte](https://forum.heroiclabs.com/u/novabyte)\ **Post date:** [March 27, 2021, 10:51pm UTC](https://forum.heroiclabs.com/t/enabling-https-for-nakama-console/1500/2 "2021-03-27T22:51:24Z")
@landrade This is not specific to the game server. You can use the SSL support built-into the server and configure the SSL keys which we don’t recommend in production; or you can put a load balancer in front of the server which you can configure for SSL negotiation. ---
**Author:** ![landrade](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.heroiclabs.com/landrade/32/575_2.png) [@landrade](https://forum.heroiclabs.com/u/landrade)\ **Post date:** [March 28, 2021, 12:35am UTC](https://forum.heroiclabs.com/t/enabling-https-for-nakama-console/1500/3 "2021-03-28T00:35:37Z")
I meant activating SSL only for the Nakama Console using a Public CA so that the browser recognizes the site as safe. ![image](https://us1.discourse-cdn.com/flex020/uploads/heroiclabs/original/1X/03d71002b5487c0bd851e8cf4585bc07c2b23ca2.png) ---
**Author:** ![novabyte](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.heroiclabs.com/novabyte/32/1324_2.png) [@novabyte](https://forum.heroiclabs.com/u/novabyte)\ **Post date:** [March 28, 2021, 9:21am UTC](https://forum.heroiclabs.com/t/enabling-https-for-nakama-console/1500/4 "2021-03-28T09:21:50Z")
@landrade I fully understand what you’re asking and as I said above its up to you to set up your load balancer configuration appropriately to use SSL. ![SSL-enabled-console](https://us1.discourse-cdn.com/flex020/uploads/heroiclabs/original/1X/e825c5496b8189c19e7c3ed6365406037839f844.png) ---
**Author:** ![RiverExplorer](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.heroiclabs.com/riverexplorer/32/2102_2.png) [@RiverExplorer](https://forum.heroiclabs.com/u/RiverExplorer)\ **Post date:** [March 23, 2024, 11:06pm UTC](https://forum.heroiclabs.com/t/enabling-https-for-nakama-console/1500/5 "2024-03-23T23:06:35Z")
1. Get SSL wrapper from [GitHub - cesanta/ssl\_wrapper: Wrap plain TCP traffic into SSL](https://github.com/cesanta/ssl_wrapper) 2. You have to have PEM certificate that you browser accepts. 3. build the SSL wrapper. (and follow the PEM instructions) 4. In your config.yaml, set your port 7351 to use address 127.0.0.1 5. Then run ssl\_wrapper ssl\_wrapper ssl://{YOUR-PUBLIC-IP}:7351:{YOUR-PEM-FILE}.pem 127.0.0.1:7351 Then you can [https://YOURSERSERVER:7351](https://YOURSERSERVER:7351) ---
**Author:** ![RiverExplorer](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.heroiclabs.com/riverexplorer/32/2102_2.png) [@RiverExplorer](https://forum.heroiclabs.com/u/RiverExplorer)\ **Post date:** [March 23, 2024, 11:09pm UTC](https://forum.heroiclabs.com/t/enabling-https-for-nakama-console/1500/6 "2024-03-23T23:09:46Z")
And for UNIX/Linux do a chmod og-rwx on your PEM file. I have no idea how to restrict read restrictions on other OS’s.