mlex

Cool. Thanks, Byron

Yes, exactly... This will be less secure using the I'm actually using the FileZilla client, but doing this for each file is... frustrating CHMODing public_html... well, isn't that not the right way to go? I mean obviously there could(and will) be files I don't want to CHMOD as usual ones, .htaccess for example, or just random other files I don't want to CHMOD as usual ones for security reasons, but yet, locate them within the public_html folder. UPDATE: Hm... Seems like CHMODing files with 644 is actually enough secured even for sensitive files. Am I getting this right?

Krydos, that's why I'm sharing here with updates So it would be less painful for anyone who's searching for this. You should somehow promote this, because this will actually reduce your server usage resources, and you could consume much more users/clients wolstech, yes, exactly. That's why I was confused with it until I found the link above (https://support.cloudflare.com/hc/en-us/articles/200169626-What-subdomains-are-appropriate-for-orange-gray-clouds-) So, continue with answering my own question(s): Using "Automatic HTTPS Rewrites" isn't actually for forcing https(SSL). So instead, in order to actually force the https(SSL) for the entire domain, avoiding using the .htaccess on your own, it's done with Page Rules at CloudFlare's Dashboard, by accessing the Page Rules and writing something like that: http://*domain.com/*While the only thing there's need to be changed is the domain.comfo example, using the subdomain: http://*example.heliohost.org/*And then choose from the options for "Always use HTTPS".

Thanks Byron, but would this be less secured than with SFTP - SSH method?

When I upload files/folders to my user dir, I'm getting odd permissions(775, 664) and sometimes even none(for some folders) and I must change them manually... As far as I can say, this should be done on the server side config somehow. Could anyone assist me with this, please?

The plugin's options at Helio are very limited, but I indeed start cloudflare using the plugin setup process at first. I'm not expecting something abnormal with my site(ddos attacks etc), but I'm really curious about how to run and use it, besides, this does may prevent some attacks, reduce server load/traffic etc, so why not. So, you're saying it is actually safe to run(activate), say cpanel with cloudflare? Because cloudflare is no-matter-what a third party vendor, so I'm not really sure if they may intercept the pass, login or anything else or not. Not saying they will, but yet. As for the HTTPS, I'm aware of how to make this with .htaccess, but don't really think it's a good idea, because this will additionally use server's resources, instead it should be possible to use cloudflare for that, but seems like I'm having some troubles - the only way I found to force using HTTPS via cloudflare is using Page Rules. But they're limited for only 3 rules... That would be fine if I would use one-three domain names, but I want more UPDATE 1: BTW: there's no HelioHost at this link: https://www.cloudflare.com/partners/view-partners/ May I ask why? UPDATE 2: I also found out, that when I enabled the "Development mode" to on at CloudFlare website, this didn't changed at Helio cpanel... It is still disabled(off). Is that actually normal? UPDATE 3: Seems like the synchronization issue was caused by cloudflare's dashboard. Now it's fine UPDATE 4: Found answer to one of my questions here: What subdomains are appropriate for orange / gray clouds? https://support.cloudflare.com/hc/en-us/articles/200169626-What-subdomains-are-appropriate-for-orange-gray-clouds-

I'm trying the cloudflare and getting some issues with it, some I just don't understand at all. Would be nice if someone could give a hand with this. Firstly, I want to say that when I configured my domain, there was an option to partly(or something like this) transfer traffic via cloudflare or completely(using the cloudflare dns)... So, I choose the second way - that's the better way, right? Ok, so DNS section... I got this window: Now, as you see, this says I should activate the cloudflare for this, including the cpanel... I find this a little bit unsecured, rather then otherwise. Am I wrong? If so, Why? Also, I have troubles with forcing the HTTPS by default. At cloudflare I enabled the "Automatic HTTPS Rewrites", but yet this seems not to be working... Can anyone tell why? I used page rules to force it, but I don't like this and besides, I really wanna know why this isn't working. Oh, just saying, I'm using the "Flexible" way. Forgot to add: As far as I got it, cloudflare should force redirect for its own error pages with free plan(I use this one), but when I actually try to go for non existing page, I'm hitting with heliohost's 404 error page(means my own 404 page, Not Found page). So, basically, this not working as intended... or, is it? Ok, I think I was wrong about the last one(about error pages). It's only target some specific errors, like 500 or 1000 etc. As far as I can tell

I've should search it more precisely... Sorry for that.

Hey folks, As far as I got it, in order to gain an LetsEncrypt free certificate(installing it without SSH, manually), I'll need to update it several times a year... On their page it says there's a simple way of integrating this procedure at hosting end, so it will become more reliable and easy to use. Any chances of getting this anytime soon?

Alrighty then, thanks a lot

Thanks, now it's more clear. One more question(or perhaps should I open a new topic for that?): Obviously, one of the core reasons behind new domains is to separate two(or more) sites, right, so basically my question is it really separate them - not only by folder logic, but also by system resources? Or the resources still shared as it would be one account/site? so to say no difference between one account - one domain/site, to multiple accounts - one domain/site for each?

Thanks a lot, Wolstech! As for domain, do I need to do anything else, except of changing the domain's nameservers for ns1.heliohost.org ns2.heliohost.org and updating at the "Heliohost tools"? And at the files structure, it goes like this: /home/myacc_name etc myacc_name.heliohost.org ... ... public_html cgi-bin Now, when I use the form of addon domains, there's a subdomain and document root input areas, what if a) I don't want a subdomain name - can I skip it, or what are my options? b ) the document root is for separating the content from two(or more) domains, am I getting this right? If so, where will be the folder created, in the "etc" folder, or in the "public_html/my_new_domain_name"? Because obviously, if it will be in the public_html ( and it will, as far as I got it ) it will be accessible from my original domain name, right? like "my_old_domain_name.com/my_new_domain_name". What am I able to do here, if it is really so(except .htaccess)?

Hi, 1) As far as I got it, the Tommy server should be a way stable and reliable one than Johnny, but currently the uptime of Johnny is 100%, while Tommy's 98%. I understand there may be hundredths of reasons for that, but may you please tell me why is this actually so atm? 2) I'm using the Tommy server currently and I can't find PHP Info with both of the templates provided. How can I check what current version am I using atm? 3) I have my own domains(couple of them), and I want one of them to replace the subdomain of the heliohost, and use others as parked domains. Am I able to do that - to delete the subdomain of heliohost, so it will be only available to access the site with my own domain(or other parked domains of my)? Edit: Okey, I think I found the PHP version - it's on the "Server Information" link, at the right column of the paper_lanter theme. It says PHP version is 5.6.24... Is there any info on when it will be upgraded to 7? Edit 2: I've just noticed not my IP address at the "Last Login" area. That IP was 65.19.***.* -- is that someone from Admins or...?