search

cdgco / HestiaWebInterface

[Beta] PHP interface for HesitaCP, providing a beautiful UI, UX, features & integrations.
https://hwi.cdgtech.one
GNU General Public License v3.0
26 stars 9 forks source link

Cloudflare bug #13

Open Stage4000 opened 3 years ago

Stage4000 commented 3 years ago

Cloudflare plugin on hwi calls for hwi folder within hestia, however the installer still installs the cloudflare page in vwi folder (https://github.com/cdgco/HestiaWebInterface/tree/master/install/hestia/web/vwi). Change vwi directory to hwi and it works as intended (as far as I can tell).

Stage4000 commented 3 years ago

Further information on this can be found in my previous (closed) issue comments.

Stage4000 commented 3 years ago

https://github.com/cdgco/HestiaWebInterface/tree/master/install/hestia/web/list/rrd vwi.php needs renamed to hwi.php. calls for it are failing due to improper name just like cloudflare. That doesnt appear to be a full fix either due to access denied even upon changing the file name.

Stage4000 commented 3 years ago

for some reason the if clause that checks referrer is always returning false, I simply removed the referrer check after changing the file name accordingly and it works.

cdgco commented 3 years ago

Sorry, I've been busy and haven't had a chance to look over this. To be honest, the Cloudflare integration is not great, it's pretty fragile and was one of the first integrations I built, before I built a proper plugin system. It's probably not worth making it a standalone plugin now as it's too deeply integrated in the panel, but I'm sure there are other bugs that need to be fixed. I'll accept the changes as a temporary fix, but I'd like to get things properly changed over from VWI to HWI and do some deeper testing of the Cloudflare integration.

Stage4000 commented 3 years ago

Yeah I've still not got cloudflare to work honestly. Not exactly sure what the purpose of the plugin is I've I'm to be honest because cloudflare requires you use their nameservers as SOA.

cdgco commented 3 years ago

It uses the HestiaCP DNS to forward the nameservers to Cloudflare and allows you to change SSL, security level, proxy, etc, directly from the HWI panel.

cdgco commented 3 years ago

It requires that you have nameserver records and DNS setup correctly for your HestiaCP server first.

Stage4000 commented 3 years ago

Well either I have something set up wrong or it doesn't work. I have my domain stage4000 using glue to point ns1 and ns2 to itself and then the cf plugin tries adding it to my panel but the record never propogate to cf and cf is never happy about my nameservers.

Stage4000 commented 3 years ago

Do you have Discord?

cdgco commented 3 years ago

Sorry, I don't use discord. I finally got around to testing some of this. I registered a new domain and pointed it to my glue records. One thing I was doing wrong that was preventing my domain from using my HestiaCP nameservers was that in addition to the glue records, I had A records and AAAA records in cloudflare pointing my nameservers to the IP address. The problem was that the AAAA records were behind the cloudflare proxy (and IPv6 isn't supported in HestiaCP yet). After deleting the AAAA records for my nameservers, my domain resolved correctly using the custom nameservers. So I think you need glue records and A records without a proxy.

As for the actual Cloudflare plugin in HWI, after renaming the folder so that it matches HWI and doesn't point to VWI, it does not seem to work correctly. It is adding the domain to cloudflare successfully and changing the HestiaCP DNS to forward the domain to Cloudflare, but the last step where it copies the HestiaCP dns records into Cloudflare does not seem to be working so I will have to look into that.