Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Offline
#14 2017-08-20 08:35:18
- jpdupont
- Member
- Registered: 2004-10-01
- Posts: 752
Re: Non-HTTPS Sites Labeled "Not Secure" by Chrome
On the home page of Webfaction : CentOS 7.
Offline
Re: Non-HTTPS Sites Labeled "Not Secure" by Chrome
I wrote to them:)
Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Offline
Re: Non-HTTPS Sites Labeled "Not Secure" by Chrome
Here is the answer from WF.
The official certbot client will not work on our servers as it requires root access.
Instead of following the instructions on community.webfaction.com/questions/19988/using-letsencrypt I would recommend that you try the following tool that was developed by one of our customers for the specifics of our environment:
Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Offline
Re: Non-HTTPS Sites Labeled "Not Secure" by Chrome
thank-you. but the link to github does it provide step by step instructions? if so it was not obvious to me.
…. texted postive
Offline
Re: Non-HTTPS Sites Labeled "Not Secure" by Chrome
Hi Bici,
I have braved it to a point but I am also finding it difficult.
Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Offline
Re: Non-HTTPS Sites Labeled "Not Secure" by Chrome
I’ve gone through the instructions up to a point but when I try
$ rbenv install 2.3.1I get
-bash: rbenv: command not foundUnderstandable as I get the same result after
$ type rbenvWhat is not understandable is that a .rbenv actually exists as I think that I have installed it successfully. Can someone shed some light on what’s wrong?
Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Offline
Re: Non-HTTPS Sites Labeled "Not Secure" by Chrome
HI Yiannis, unless you are already using RBEnv to manage Ruby, or if you are already a Ruby developer that stage is – they say – not necessary.
I’ve just tried following the step-by-step instructions on the wiki linked at the top for Wordpress and got as far as “what you’ve done so far” without problems. The “rbenv” installation is not part of that. The only error I found in the instructions up to that point was that the this command under “Get a real certificate”:
letsencrypt_webfaction --account_email etc. etc.should read:
letsencrypt_webfaction --letsencrypt_account_email etc. etc.(same as it does for the test certificate instance a few paragraphs further up)
I now need to set up the htaccess redirect, the admin setting for https and check my site for hard-coded instances of http:// links that should read now read https:// or (maybe better) have no protocol.
I’ll look at setting up the CRON job after I have it working cleanly on https.
ADDED: the password you add to the letsencrypt_webfaction … command is your general webfaction password (not your SSH password).
I also set up config-yml as described here placing in a directory in my account base directory. It follows exactly the pattern shown here leaving domains, public, servername, and cert_name blank (with servername included it threw an error at least when logged in via SSH). You can then use letsencrypt_webfaction … command without specifying username and password.
TXP Builders – finely-crafted code, design and txp
Offline
Re: Non-HTTPS Sites Labeled "Not Secure" by Chrome
colak wrote #306698:
I’ve gone through the instructions up to a point but when I try
i hope that someone can post a fool (me) proof write-up for webfaction
…. texted postive
Offline
Re: Non-HTTPS Sites Labeled "Not Secure" by Chrome
It seems that I reached a point that I definitely can not move from:)
Would it be OK to just delete all installs via sftp and start again… or will I break the internet?
Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Offline
Re: Non-HTTPS Sites Labeled "Not Secure" by Chrome
The simplest way of getting HTTPS working on your site is to use the option in Cloudflare, see here. Whilst this isn’t the most elegant approach (using your own certificate is preferred IMO) it works absolutely fine. Indeed, we use it for the Textpatern docs site since it runs on Jekyll GitHub Pages which doesn’t allow for an SSL certificate directly.
I’d still persevere with getting a certificate set up on your domain if you can, but if it’s proving impossible then that is an acceptable (free) alternative.
Offline
#24 2017-08-26 07:04:19
- jpdupont
- Member
- Registered: 2004-10-01
- Posts: 752
Re: Non-HTTPS Sites Labeled "Not Secure" by Chrome
Hello colak,
Did you follow the three easy steps method that I have given the link above?
Read the comments also, especially regarding the auto-renew script.
Here is a summary of it
An other good summary here with the auto-renew script
I followed this method for several sites successfully. The only thing I look forward to is the process automation that has been announced by Webfaction since June.
Jean-Pol
Last edited by jpdupont (2017-08-26 07:07:48)
Offline