Hi Ricky, Thanks to your preceding instructions, I started the server + hestia + WP website and it is already working. Now I ran into a problem. I want to redirect the domain to a VPS server where I have Hestia installed. There are some ns1 and ns2 records in hestia in the DNS section, I entered them at the domain operator, later the web domain stopped working, the Hestia admin panel does not work, the domain does not work either. When I change the DNS records back to the original ones at the registrar, everything goes back to its original state. what about that? I read some forums, and they say it's not easy, you need to set up a DNS server through some software, so that the name servers are defined correctly so that the domains work correctly. I'm testing in a VPS oracle free tier, I have a Hestia panel installed there, and I want the domain to be public.
Can you do a video on how to properly setup Cloudflare SSL for the hestia panel subdomain as well as your main website? I'm facing a lot of trouble during these.
Let's say your subdomain is shop.example.com. Create the following records on cloudflare. 1 An A record for shop. 2 A CNAME record for www.shop with a value of shop.example.com. Give it time to propagate. Issue ssl on HestiaCP. If you get an error such as too many redirects, go to cloudflare ssl and tinker with settings, for instance remove it from strict... If ssl is unable to be issued on Hestia either the DNS isn't ready yet or Try pausing cloudflare and reissue ssl again. Don't try too many times. Letsencrpt has limits. Once ssl is issued, resume site on cloudflare. If any ssl errors occur after this, tinker with ssl settings on cloudflare. It'll work.
@@rwahowa I want to use Cloudflare origin certificate, not Let's Encrypt so in Browser it show's that it's issued by Cloudflare. Currently I have the cloudflare origin SSL on my website settings in hestia but in browser I see E1 certificate. Also, a weird problem, when I try to set up CF origin certificate in hestacp dashboard> settings> ssl it says saved but it remains blank.
Using cloudflare origin cert needed you to turn off cloudflare proxy. Don't know if that's still the case. Under DNS try turning everything back to gray
I am using the HestiaCP control panel for my website, and I've integrated it with Cloudflare. However, when I enable the DNS Proxy feature on Cloudflare for my site's IP address, the website stops working. I want to route traffic through Cloudflare but am unsure how to resolve this issue. I don't have extensive technical knowledge. What steps should I take to fix this problem?
Hi Ricky, great tutorial. Keep it up. I am try to use Cloudflare for DNS and use HesticCP for nameservers. Google is my domain registrar. I created glue records in Google Domains for the nameservers. But my domain nameservers are set to the Cloudflare nbameservers. I have created the A & NS records in HestiaCP. But when I point a new domain using the nameservers, it's not working. Am I missing something? Thought of changing the nameservers from Cloudflare to the ones I have in the Glue records but thoght then Cloudflare would cease be my DNS provider.
To use Cloudflare, you don't need to set up glue records, and you don't need to do anything on HestiaCP. You just add the Cloudflare NS to your Google domain. Then add the other records to cloudflare. To use personal NS (Hestia is in charge of your DNS): 1. Create glue records on Google Domains (NS1.yourdomain, NS2.yourdomain ) 2. Add the created glue records as your NS on Goggle 3. In your Hestia user, set up the default Nameservers you created. May not be necessary, but you do it so that, every new domain created will inherit these records. 4. At this point, the domain you added with these nameservers, should be working assuming you have given it time to propagate. If not : 5. Change the DNS template. Go to DNS settings for that domain. Click on Edit DNS zone. Then under Template, choose child-ns.
@@rwahowa But if I go with Cloudflare, and I create several sites inside Hestia, I cannot expose them even with NGINX Reverse Proxy, since they don't have different ports.
I've been stuck for almost a month now trying to solve this....We couldn't find the verification token in your domain's TXT records. You might need to wait a few minutes before Google sees your changes to the TXT records....I've already added it on my hestiacp but I still can't verify my domain. Could you kindly help me?
Can you explain is there any reason to use your own dns instead of cloudflare? Currently, I don't see any reason other than some mega private configurations that care about privacy in every aspect. Cloudflare gives you free static content cache, nearest cdn, ddos protection (as long as your real IP hasn't been leaked) and much more.
Hello Ricky, thank you for this Video, i have an issue when I add DNS Records to Cloudflare, ERR_TOO_MANY_REDIRECTS, could you please tell me if you have an idea to resolve this problem ? thanks in advance :)
If you have already created A records for the domain, add www as well.Then pause cloudflare , next issue let's encrypt SSL on hestiacp. If SSL issues correctly,then DNS is ok.
@@rwahowa Hey Ricky, the problem was solved yesterday without doing nothing ! maybe I had to wait till my DNS is propagated ! Thank you very much for your time Ricky :) you are awsome !
I actually don't know how to thank you!
I swear you are the best, you helped me verry much!
Keep the great work, my guy!
You are welcome. And thanks for watching.
hey please do a video how to setup rclone for HestiaCP
Hi Ricky, Thanks to your preceding instructions, I started the server + hestia + WP website and it is already working. Now I ran into a problem. I want to redirect the domain to a VPS server where I have Hestia installed. There are some ns1 and ns2 records in hestia in the DNS section, I entered them at the domain operator, later the web domain stopped working, the Hestia admin panel does not work, the domain does not work either. When I change the DNS records back to the original ones at the registrar, everything goes back to its original state. what about that? I read some forums, and they say it's not easy, you need to set up a DNS server through some software, so that the name servers are defined correctly so that the domains work correctly.
I'm testing in a VPS oracle free tier, I have a Hestia panel installed there, and I want the domain to be public.
Is your intent to use cloudflare for DNS or to use hestia (your domain will be the NS servers) ?
Can you do a video on how to properly setup Cloudflare SSL for the hestia panel subdomain as well as your main website? I'm facing a lot of trouble during these.
Let's say your subdomain is shop.example.com.
Create the following records on cloudflare.
1 An A record for shop.
2 A CNAME record for www.shop with a value of shop.example.com.
Give it time to propagate.
Issue ssl on HestiaCP.
If you get an error such as too many redirects, go to cloudflare ssl and tinker with settings, for instance remove it from strict...
If ssl is unable to be issued on Hestia either the DNS isn't ready yet
or
Try pausing cloudflare and reissue ssl again. Don't try too many times. Letsencrpt has limits.
Once ssl is issued, resume site on cloudflare. If any ssl errors occur after this, tinker with ssl settings on cloudflare.
It'll work.
@@rwahowa I want to use Cloudflare origin certificate, not Let's Encrypt so in Browser it show's that it's issued by Cloudflare.
Currently I have the cloudflare origin SSL on my website settings in hestia but in browser I see E1 certificate.
Also, a weird problem, when I try to set up CF origin certificate in hestacp dashboard> settings> ssl it says saved but it remains blank.
Check this docs.hestiacp.com/admin_docs/web/ssl_certificates.html
Using cloudflare origin cert needed you to turn off cloudflare proxy. Don't know if that's still the case. Under DNS try turning everything back to gray
@@rwahowa is it okay if I mail you with the server details so you can help me out? Please 🥺
I am using the HestiaCP control panel for my website, and I've integrated it with Cloudflare. However, when I enable the DNS Proxy feature on Cloudflare for my site's IP address, the website stops working. I want to route traffic through Cloudflare but am unsure how to resolve this issue. I don't have extensive technical knowledge. What steps should I take to fix this problem?
Does the website have SSL enabled in HestiaCP? Also check which SSH settings you have on cloudflare. Tinker with them a bit, try full mode.
Hi Ricky, great tutorial. Keep it up.
I am try to use Cloudflare for DNS and use HesticCP for nameservers. Google is my domain registrar. I created glue records in Google Domains for the nameservers. But my domain nameservers are set to the Cloudflare nbameservers. I have created the A & NS records in HestiaCP. But when I point a new domain using the nameservers, it's not working. Am I missing something? Thought of changing the nameservers from Cloudflare to the ones I have in the Glue records but thoght then Cloudflare would cease be my DNS provider.
To use Cloudflare, you don't need to set up glue records, and you don't need to do anything on HestiaCP. You just add the Cloudflare NS to your Google domain. Then add the other records to cloudflare.
To use personal NS (Hestia is in charge of your DNS):
1. Create glue records on Google Domains (NS1.yourdomain, NS2.yourdomain )
2. Add the created glue records as your NS on Goggle
3. In your Hestia user, set up the default Nameservers you created. May not be necessary, but you do it so that, every new domain created will inherit these records.
4. At this point, the domain you added with these nameservers, should be working assuming you have given it time to propagate. If not :
5. Change the DNS template. Go to DNS settings for that domain. Click on Edit DNS zone. Then under Template, choose child-ns.
@@rwahowa But if I go with Cloudflare, and I create several sites inside Hestia, I cannot expose them even with NGINX Reverse Proxy, since they don't have different ports.
You should do meditation videos also lol.... Your voice is relaxing as hell lol.
Thanks mate. I may look into it. Meditation or hypnosis for IT people >> “I can learn all programming languages in a year, yes I can. I am the man”.
I've been stuck for almost a month now trying to solve this....We couldn't find the verification token in your domain's TXT records. You might need to wait a few minutes before Google sees your changes to the TXT records....I've already added it on my hestiacp but I still can't verify my domain. Could you kindly help me?
What's your set up like? reach out via the website if you still need assistance
Can you explain is there any reason to use your own dns instead of cloudflare?
Currently, I don't see any reason other than some mega private configurations that care about privacy in every aspect. Cloudflare gives you free static content cache, nearest cdn, ddos protection (as long as your real IP hasn't been leaked) and much more.
Just use Cloudflare. Takes the server load off your website and the security that comes with using Cloudflare is important.
Hello Ricky, thank you for this Video, i have an issue when I add DNS Records to Cloudflare, ERR_TOO_MANY_REDIRECTS, could you please tell me if you have an idea to resolve this problem ? thanks in advance :)
If you have already created A records for the domain, add www as well.Then pause cloudflare , next issue let's encrypt SSL on hestiacp. If SSL issues correctly,then DNS is ok.
@@rwahowa My LetsEncrypt SLL works correctly, but I have always this Error
ERR_TOO_MANY_REDIRECTS, does it mean it doesnt come from DNS ?
Go to cloudflare SSL settings and tinker with it, if it is in strict mode, put at full or something else. Let me know how that goes
@@rwahowa Hey Ricky, the problem was solved yesterday without doing nothing ! maybe I had to wait till my DNS is propagated ! Thank you very much for your time Ricky :) you are awsome !