I am so proud of setting up my website and hosting a serverless load balancer. However, in the case I need to support some legacy systems, I won’t be able to use MySQL or Postgresql to manage them. So, I have to start from scratch with an alternative that is more powerful than most modern alternatives like Elasticsearch.
While building cyberPanel, it turns out this will be not quite enough to go on with due to its poor scalability. My concern is this if it becomes unstable due to memory fragmentation or memory leaks, then I cannot work on other parts of the application because I can no longer deploy new changes. Fortunately all the resources are available here as well. What to do next? If you don’t have good memory and want to migrate from php memory to cPanel memory, here is how to point your DNS nameservice using CyberPanel.
First step : Find their IP address using our proxy server. Remember that we have proxy servers on both machines. So if we know the IP address of the site’s domain server, we can find where they are hosted via https://ip.google.com/ip. Then, in order to point these things we need two different types of DNS records — DNS Records & TXT Records. You can find more about configuring these types here. In general, make sure DNS and TXT records are configured properly when you get to host the web server. As far as you know, we will use GCP and Heroku for development, but that should be fine. Also the following steps can be used in any cloud provider environment (like Azure)
When adding nameserver to CPanel, you can see only name servers where you can add DNS + TXT records. Add these two records. Create HTTPS connection to your SSL certificate. Go over the name servers and give one for the domain name, another for the user account, etc. Don’t forget to copy this key on a local computer if your public keys weren’t working. Now add “X-Forwarded” rules to the Name Servers located in the domains (like google.com to www.google.com. That’s good. If you still can’t figure it out by yourself, check these links for help:
https://app.cyberpanel.com/cpanel/cyberpanel_add_nameserver
https://app.cyberpanel.com/cpanel/cyberpanel_remove_nameserver
https://app.cyberpanel.com/cpanel/cyberpanel_update_nameserver
https://app.cyberpanel.com/cpanel/cyberpanel_enable_nameserver
https://app.cyberpanel.com/cpanel/cyberpanel_disable_nameserver
https://app.cyberpanel.com/cpanel/cyberpanel_get_nameserver
https://app.cyberpanel.com/cpanel/cyberpanel_get_nameserver_rule
https://app.cyberpanel.com/cpanel/cyberpanel_get_nameserver_rule_byname
https://app.cyberpanel.com/cpanel/cpanel_update_nameserver
https://app.cyberpanel.com/cpanel/cpanel_disable_nameserver
https://app.cyberpanel.com/cpanel/cpanel_update_nameserver
https://app.cyberpanel.com/cpanel/cpanel_disable_nameserver
https://app.cyberpanel.com/cpanel/cpanel_get_nameserver_rule
https://app.cyberpanel.com/cpanel/cyberpanel_get_nameserver_rule_byname
https://app.cyberpanel.com/cpanel/cpanel_disable_nameserver
https://app.cyberpanel.com/cpanel/cpanel_get_nameserver
https://app.cyberpanel.com/cpanel/cyberpanel_update_nameserver
https://app.cyberpanel.com/cpanel/cpanel_disable_nameserver
https://app.cyberpanel.com/cpanel/cpanel_update_nameserver
Once done, go to cPanel -> Nameserver -> Configure-> Add rule-> Click on name servers-> Select the correct region for naming servers
In the end, let’s say the server has two instances. One with ubuntu 16.04 LTS and others with k3s. Ubuntu 17.xLTS. And these two sites will run at two separate ports in http://localhost:8081/ and http://localhost:8000/ respectively. The nameserver server will listen to these two port while serving the files in two distinct locations, one of them being http://localhost:8081/ and second one http://localhost:8083/ depending upon which file you are serving.
To find the nameserver server’s IP address, enter cPanel -> Nameserver-> Configure-> Add Rule-> Enter your IP address. It looks like it is just a few milliseconds away from the actual name server IP address for both your host’s machine1.
To connect your web server with the DNS of the nameserver server, enter the same keywords from above step — name servers and the IP address of the server. And you are done. This process does take a bit of time, but once you are set it should be pretty fast and smooth.
The command below shows you the full details:
curl -X GET http://localhost:8081/index.html;
# or, if you’re on an ssh server:
ssh x
And finally, there is also one more quick tip to ensure that everything works seamlessly:
Use only SSL certificates of your web server. Use TLS as proxy server. There is no need to convert any certificate into SSL if you use GCP/Heroku, since it already exists.
Conclusion
CyberPanel is very easy to setup and maintain. When you use GCP or Heroku, install the required dependencies and build your code. Once it is ready, you can host it via cyberserver or even github repo using GitHub Serverless Compute. Its built-in features makes sure all your secrets are safe and secure. Additionally, it takes minimal effort to move between cPanel and cyberserver or github serverless computing environments. Since it is open source, security matters and hence making it the safest thing to choose for development and hosting purposes. Besides, with many plugins including authentication, logging, caching, compression, encryption, etc. you’re bound to have what you need. On top of all that you enjoy free access to many useful tools such as Cloudwatch logs, Google Analytics/Gmail etc. Not forgetting great feature like Smart Panel and dashboard view. For more information visit here and here.