Non-HTTPS Sites Labeled "Not Secure" by Chrome

colak · 2017-08-20 14:25:50

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:

github.com/will-in-wi/letsencrypt-webfaction

bici · 2017-08-21 02:53:39

thank-you. but the link to github does it provide step by step instructions? if so it was not obvious to me.

colak · 2017-08-21 04:56:25

Hi Bici,

I have braved it to a point but I am also finding it difficult.

colak · 2017-08-21 15:06:34

I’ve gone through the instructions up to a point but when I try

$ rbenv install 2.3.1

I get

-bash: rbenv: command not found

Understandable as I get the same result after

$ type rbenv

What 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?

jakob · 2017-08-21 19:47:42

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.

bici · 2017-08-21 20:27:50

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

colak · 2017-08-25 05:06:37

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?

philwareham · 2017-08-25 07:58:24

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.

jpdupont · 2017-08-26 07:04:19

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)

colak · 2017-08-26 10:40:11

Hi jp

I started by checking the WF forum post that you linked to but WF support directed me to another method which I find confusing.

Thanks for the 3 easy steps reminder. I’ll look into it.

colak · 2017-08-27 06:34:10

Could somebody please shed some light re my question here?

jakob · 2017-08-28 06:13:17

colak wrote #306731:

Could somebody please shed some light re my question here?

I’m not expert enough on ruby, but presumably for the System Ruby method, you can use uninstall in place of install, but use the entire command as given on the GitHub page to ensure you’re working with the relevant ruby installation locations:

GEM_HOME=$HOME/.letsencrypt_webfaction/gems RUBYLIB=$GEM_HOME/lib gem2.2 uninstall letsencrypt_webfaction

I can’t comment on the RBenv way, but if you had already done the System Ruby method, you don’t need the RBenv as well. As I understand it, the instructions are either/or.

Before you do that, try updating you existing letsencrypt_webfaction installation. The command is identical to running the install command a second time.

Did you try running the command under Testing and then looking in the webfaction admin area at SSL certificates? Running the command showed no output in the terminal (= success) and the test certificate appeared in the webfaction admin area (after revisiting the page). If you get that far, you should be ready to go with the rest.

One thing that was mentioned in one of the other tutorials is that the letsencrypt_account_email you use should be associated with your webfaction account.

EDIT: here and here are some notes about uninstalling rbenv if you used that method.

bici · 2017-08-28 06:33:21

colak wrote #306731:

Could somebody please shed some light re my question here?

PS the latest from Webfaction:
“Our development team are working on implementing Let’s Encrypt to WebFaction control panel, but there is no ETA for this yet”.

jpdupont · 2017-10-01 16:26:43

Yannis,
Have you been able to install your certificates? I just tried the method recommended by Webfaction successfully, after a bug fixed by the author of the script.

github.com/will-in-wi/letsencrypt-webfaction

If you need it, can I provide you with a step-by-step tutorial.

Last edited by jpdupont (2017-10-01 16:27:06)

bici · 2017-10-02 01:27:54

jpdupont wrote #307269:

Yannis,
Have you been able to install your certificates? I just tried the method recommended by Webfaction successfully, after a bug fixed by the author of the script.

github.com/will-in-wi/letsencrypt-webfaction

If you need it, can I provide you with a step-by-step tutorial.

i would like to install it. i am on Webfaction

Textpattern CMS

Textpattern CMS support forum

#16 2017-08-20 14:25:50

Re: Non-HTTPS Sites Labeled "Not Secure" by Chrome

#17 2017-08-21 02:53:39

Re: Non-HTTPS Sites Labeled "Not Secure" by Chrome

#18 2017-08-21 04:56:25

Re: Non-HTTPS Sites Labeled "Not Secure" by Chrome

#19 2017-08-21 15:06:34

Re: Non-HTTPS Sites Labeled "Not Secure" by Chrome

#20 2017-08-21 19:47:42

Re: Non-HTTPS Sites Labeled "Not Secure" by Chrome

#21 2017-08-21 20:27:50

Re: Non-HTTPS Sites Labeled "Not Secure" by Chrome

colak wrote #306698:

#22 2017-08-25 05:06:37

Re: Non-HTTPS Sites Labeled "Not Secure" by Chrome

#23 2017-08-25 07:58:24

Re: Non-HTTPS Sites Labeled "Not Secure" by Chrome

#24 2017-08-26 07:04:19

Re: Non-HTTPS Sites Labeled "Not Secure" by Chrome

#25 2017-08-26 10:40:11

Re: Non-HTTPS Sites Labeled "Not Secure" by Chrome

#26 2017-08-27 06:34:10

Re: Non-HTTPS Sites Labeled "Not Secure" by Chrome

#27 2017-08-28 06:13:17

Re: Non-HTTPS Sites Labeled "Not Secure" by Chrome

colak wrote #306731:

#28 2017-08-28 06:33:21

Re: Non-HTTPS Sites Labeled "Not Secure" by Chrome

colak wrote #306731:

#29 2017-10-01 16:26:43

Re: Non-HTTPS Sites Labeled "Not Secure" by Chrome

#30 2017-10-02 01:27:54

Re: Non-HTTPS Sites Labeled "Not Secure" by Chrome

jpdupont wrote #307269:

Board footer