How? #124

New Issue

adam · 2025-12-29T00:25:19+01:00

adam commented

2025-12-29 00:25:19 +01:00

Originally created by @jult on GitHub (Jul 6, 2016).

OK, this issue is completely obsolete, as far as I'm concerned. Turned out there was a default python exclusion set in yum.conf, which is strangely never even echoed to its user, not even when doing "yum install python" or something. Seriously hating yum now.

Originally created by @jult on GitHub (Jul 6, 2016). OK, this issue is completely obsolete, as far as I'm concerned. Turned out there was a default python exclusion set in yum.conf, which is strangely never even echoed to its user, not even when doing "yum install python" or something. Seriously hating yum now.

adam closed this issue

2025-12-29 00:25:20 +01:00

adam commented

2025-12-29 00:25:21 +01:00

@seefood commented on GitHub (Jul 6, 2016):

Have you read the readme, at least once?

@seefood commented on GitHub (Jul 6, 2016): Have you read the readme, at least once?

adam commented

2025-12-29 00:25:22 +01:00

@extremeshok commented on GitHub (Jul 6, 2016):

lol, that would be too much effort ;-P

Sorry, I could not resist the trolling

. https://eXtremeSHOK.com .

On 06-Jul-16 1:21 PM, Ira wrote:

Have you read the readme, at least once?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/lukas2511/letsencrypt.sh/issues/240#issuecomment-230745346,
or mute the thread
https://github.com/notifications/unsubscribe/AFrm0COwxaHEuVrwUANbiw3Wm5Ahd_NJks5qS4-hgaJpZM4JF-OJ.

@extremeshok commented on GitHub (Jul 6, 2016): lol, that would be too much effort ;-P Sorry, I could not resist the trolling __________________________________. https://eXtremeSHOK.com .__________________________________ On 06-Jul-16 1:21 PM, Ira wrote: > Have you read the readme, at least once? > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > https://github.com/lukas2511/letsencrypt.sh/issues/240#issuecomment-230745346, > or mute the thread > https://github.com/notifications/unsubscribe/AFrm0COwxaHEuVrwUANbiw3Wm5Ahd_NJks5qS4-hgaJpZM4JF-OJ.

adam commented

2025-12-29 00:25:22 +01:00

@jult commented on GitHub (Jul 6, 2016):

What do you mean by "the readme" ? And yes, I read it all. It's unclear where which files need to be changed. You just have not documented anything pointing to that.

@jult commented on GitHub (Jul 6, 2016): What do you mean by "the readme" ? And yes, I read it all. It's unclear where which files need to be changed. You just have not documented anything pointing to that.

adam commented

2025-12-29 00:25:22 +01:00

@jult commented on GitHub (Jul 6, 2016):

"Generally you want to set up your WELLKNOWN path first," where? I see it in your docs folder, but it does not even state that a filename needs to be changed, or moved, or whereto. You assume too much, you seriously do.

@jult commented on GitHub (Jul 6, 2016): "Generally you want to set up your WELLKNOWN path first," where? I see it in your docs folder, but it does not even state that a filename needs to be changed, or moved, or whereto. **You assume too much, you seriously do**.

adam commented

2025-12-29 00:25:23 +01:00

@jult commented on GitHub (Jul 6, 2016):

I do a git clone of your stuff, as recommended elsewhere, and on the server I see the git formatting in all files, which is also not very appropriate. I mean, if you do make txt files, make them in the .txt format, i.e. don't use code tags. I would easily have created a file like this:

domains.txt (of which still unclear where to put it):

```text
example.com www.example.com
example.net www.example.net wiki.example.net

@jult commented on GitHub (Jul 6, 2016): I do a git clone of your stuff, as recommended elsewhere, and on the server I see the git formatting in all files, which is also not very appropriate. I mean, if you do make txt files, make them in the .txt format, i.e. don't use code tags. I would easily have created a file like this: domains.txt (of which still unclear where to put it): `````` ```text example.com www.example.com example.net www.example.net wiki.example.net `````` ``` ```

adam commented

2025-12-29 00:25:23 +01:00

@jult commented on GitHub (Jul 6, 2016):

"An example would be to create a directory /var/www/letsencrypt and set WELLKNOWN=/var/www/letsencrypt in the scripts config."

What config? The only config after a git clone I see is under /.git/, but that's not "the script config".

@jult commented on GitHub (Jul 6, 2016): "An example would be to create a directory /var/www/letsencrypt and set WELLKNOWN=/var/www/letsencrypt in the scripts config." What config? The only config after a git clone I see is under /.git/, but that's not "the script config".

adam commented

2025-12-29 00:25:24 +01:00

@germeier commented on GitHub (Jul 6, 2016):

There are three things that are assumed:

That you can read the and understand the first page completey "For getting started I recommend taking a look at docs/domains_txt.md, docs/wellknown.md and the Usage section on this page"
That you are not to shy to actually read these documents.
That you are able to find and read: https://github.com/lukas2511/letsencrypt.sh/blob/master/docs/examples/config

@germeier commented on GitHub (Jul 6, 2016): There are three things that are assumed: 1. That you can read the and understand the first page completey "For getting started I recommend taking a look at docs/domains_txt.md, docs/wellknown.md and the Usage section on this page" 2. That you are not to shy to actually read these documents. 3. That you are able to find and read: https://github.com/lukas2511/letsencrypt.sh/blob/master/docs/examples/config

adam commented

2025-12-29 00:25:24 +01:00

@jult commented on GitHub (Jul 6, 2016):

Like I wrote, and I know startssl is in the news because of their bad attempts at trying to go the letsencrypt route, but this is not the what would be expected for letsencrypt usage. The directory structure is not even like the one letsencrypt uses by default through the python installs of certs in /etc/letsencrypt, which is also confusing, since that is the logical route to follow, I would say. But hey, that's me. And even acmetool decided to not follow up on that logic. You're a bunch of weird coders, if you ask me.

The thing is; I have to install a cert on a CentOS 6.8 server (not mine, and I can't upgrade it), acmetool would not work, because install from source requires at least a GLIBC version that I could not get installed on CentOS 6.8, and acmetool provides no package for CentOS 6.* (even though they weirdly do provide the repo for it that, without documenting it, just doesn't hold acmetool).
Yes, one could try python 2.7 on CentOS 6.8, but whatever I do, I keep running into issues with that, a can of worms would be an understatement at this point.

# yum --enablerepo=ius install git python27 python27-devel python27-pip python27-setuptools python27-virtualenv
Loaded plugins: fastestmirror, presto, priorities
Setting up Install Process
Loading mirror speeds from cached hostfile
* base: mirrors.supportex.net
* epel: mirror.nl.leaseweb.net
* extras: mirror.1000mbps.com
* ius: mirror.amsiohosting.net
* updates: mirrors.supportex.net
ius | 2.2 kB 00:00
ius/primary_db | 202 kB 00:00
10 packages excluded due to repository priority protections
Package git-1.7.1-4.el6_7.1.x86_64 already installed and latest version
No package python27 available.
No package python27-devel available.
No package python27-pip available.
No package python27-setuptools available.
No package python27-virtualenv available.
Nothing to do

So I end up with this shell script option, which, one must admit, requires time to get running that is presumably more than installing through startssl. Which was my earlier point.

@jult commented on GitHub (Jul 6, 2016): Like I wrote, and I know startssl is in the news because of their bad [attempts at trying to go the letsencrypt route](https://www.computest.nl/blog/startencrypt-considered-harmful-today/), but this is not the what would be expected for letsencrypt usage. The directory structure is not even like the one letsencrypt uses by default through the python installs of certs in /etc/letsencrypt, which is also confusing, since that is the logical route to follow, I would say. But hey, that's me. And even acmetool decided to not follow up on that logic. You're a bunch of weird coders, if you ask me. The thing is; I have to install a cert on a CentOS 6.8 server (not mine, and I can't upgrade it), acmetool would not work, because install from source requires at least a GLIBC version that I could not get installed on CentOS 6.8, and acmetool provides no package for CentOS 6.\* (even though they weirdly do provide the repo for it that, without documenting it, just doesn't hold acmetool). Yes, one could try python 2.7 on CentOS 6.8, but whatever I do, I keep running into issues with that, a can of worms would be an understatement at this point. ``` # yum --enablerepo=ius install git python27 python27-devel python27-pip python27-setuptools python27-virtualenv Loaded plugins: fastestmirror, presto, priorities Setting up Install Process Loading mirror speeds from cached hostfile * base: mirrors.supportex.net * epel: mirror.nl.leaseweb.net * extras: mirror.1000mbps.com * ius: mirror.amsiohosting.net * updates: mirrors.supportex.net ius | 2.2 kB 00:00 ius/primary_db | 202 kB 00:00 10 packages excluded due to repository priority protections Package git-1.7.1-4.el6_7.1.x86_64 already installed and latest version No package python27 available. No package python27-devel available. No package python27-pip available. No package python27-setuptools available. No package python27-virtualenv available. Nothing to do ``` So I end up with this shell script option, which, one must admit, requires time to get running that is presumably more than installing through startssl. Which was my earlier point.

adam commented

2025-12-29 00:25:24 +01:00

@germeier commented on GitHub (Jul 6, 2016):

If letsencrypt.sh is to complicated for you, you can always go the startssl route or simply use another lightweight ACME implementation, see: https://github.com/certbot/certbot/wiki/Links

@germeier commented on GitHub (Jul 6, 2016): If letsencrypt.sh is to complicated for you, you can always go the startssl route or simply use another lightweight ACME implementation, see: https://github.com/certbot/certbot/wiki/Links

adam commented

2025-12-29 00:25:25 +01:00

@lingej commented on GitHub (Jul 6, 2016):

this is not letsencrypt! Its the letsencrypt.sh repository
See -> https://letsencrypt.org/

@lingej commented on GitHub (Jul 6, 2016): this is not letsencrypt! Its the letsencrypt.sh repository See -> https://letsencrypt.org/

adam commented

2025-12-29 00:25:25 +01:00

@jult commented on GitHub (Jul 6, 2016):

I know, but why completely change the way they prefer to do things (and why install certs in some weird /opt/letsencrypt.sh/certs dir)? You use their servers, you could at least use their conventions. Unless it's something you like to do, to confuse the public at large.

Also, I'm just guessing, but this script wants us to change file.extension.md into file.extension or what? And then move them to the folder where the .sh is.

@jult commented on GitHub (Jul 6, 2016): I know, but why completely change the way they prefer to do things (and why install certs in some weird /opt/letsencrypt.sh/certs dir)? You use their servers, you could at least use their conventions. Unless it's something you like to do, to confuse the public at large. Also, I'm just guessing, but this script wants us to change file.extension.md into file.extension or what? And then move them to the folder where the .sh is.

adam commented

2025-12-29 00:25:25 +01:00

@germeier commented on GitHub (Jul 6, 2016):

Also, I'm just guessing, but this script wants us to change file.extension.md into file.extension or what? And then move them to the folder where the .sh is.

I give up!

@germeier commented on GitHub (Jul 6, 2016): > Also, I'm just guessing, but this script wants us to change file.extension.md into file.extension or what? And then move them to the folder where the .sh is. I give up!

adam commented

2025-12-29 00:25:26 +01:00

@seefood commented on GitHub (Jul 6, 2016):

@jult I actually find the original LetsEncrypt tool to completely change the way I like to do things, including attempting to reconfigure the webserver(s) for me, pick directories for me, and then refuse to run under cron if anything is bothering it (and it's a highly sensitive primadonna).

Here, I just:

git-cloned it into a directory,
created the config and domains list,
made a common acme directory,
made sure all the apache and nginx vhosts show that directory at the correct URL (I just include the same file again and again in all the vhosts' configs)

and that should do it. This works well since I have a mix of static, php and other sites all on the same machine, in various directories owned by different users, and this client just works and allows me to never worry about expired certificates ever again.

If this is not your bag, feel free to use any of the other dozen or two clients written to use their server. this client though, is as simple as they get.

@seefood commented on GitHub (Jul 6, 2016): @jult I actually find the original LetsEncrypt tool to completely change the way I like to do things, including attempting to reconfigure the webserver(s) for me, pick directories for me, and then refuse to run under cron if anything is bothering it (and it's a highly sensitive primadonna). Here, I just: - git-cloned it into a directory, - created the config and domains list, - made a common acme directory, - made sure all the apache and nginx vhosts show that directory at the correct URL (I just include the same file again and again in all the vhosts' configs) and that should do it. This works well since I have a mix of static, php and other sites all on the same machine, in various directories owned by different users, and this client just works and allows me to never worry about expired certificates ever again. If this is not your bag, feel free to use any of the other dozen or two clients written to use their server. this client though, is as simple as they get.

adam commented

2025-12-29 00:25:27 +01:00

@jult commented on GitHub (Jul 6, 2016):

Again, must be me, but is this .md extension something I should know about? First time I encounter it..

@jult commented on GitHub (Jul 6, 2016): Again, must be me, but is this .md extension something I should know about? First time I encounter it..

adam commented

2025-12-29 00:25:27 +01:00

@germeier commented on GitHub (Jul 6, 2016):

http://lmgtfy.com/?q=extension+md

@germeier commented on GitHub (Jul 6, 2016): http://lmgtfy.com/?q=extension+md

adam commented

2025-12-29 00:25:28 +01:00

@Rayne commented on GitHub (Jul 6, 2016):

Again, must be me, but is this .md extension something I should know about? First time I encounter it..

Your nginx-config (jult/nginx-config) repository consists of two files and one of them is a README.md with valid Markdown. Please stop trolling.

@Rayne commented on GitHub (Jul 6, 2016): > Again, must be me, but is this .md extension something I should know about? First time I encounter it.. Your `nginx-config` (`jult/nginx-config`) repository consists of two files and one of them is a `README.md` with valid Markdown. Please stop trolling.

adam commented

2025-12-29 00:25:29 +01:00

@jult commented on GitHub (Jul 6, 2016):

On July 6, 2016 6:25:19 PM GMT+02:00, Dennis Meckel notifications@github.com wrote:

Again, must be me, but is this .md extension something I should know
about? First time I encounter it..

Your nginx-config (jult/nginx-config) repository consists of two
files and one of them is a README.md with valid Markdown. Please
stop trolling.

You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/lukas2511/letsencrypt.sh/issues/240#issuecomment-230826561

It was forked, I never wrote it. It's not my Nginx config.

Sent from my OpenPDroid protected phone with k9mail. Please excuse my brevity.

@jult commented on GitHub (Jul 6, 2016): On July 6, 2016 6:25:19 PM GMT+02:00, Dennis Meckel notifications@github.com wrote: > > Again, must be me, but is this .md extension something I should know > > about? First time I encounter it.. > > Your `nginx-config` (`jult/nginx-config`) repository consists of two > files and one of them is a `README.md` with valid Markdown. Please > stop trolling. > > --- > > You are receiving this because you were mentioned. > Reply to this email directly or view it on GitHub: > https://github.com/lukas2511/letsencrypt.sh/issues/240#issuecomment-230826561 ## It was forked, I never wrote it. It's not my Nginx config. Sent from my OpenPDroid protected phone with k9mail. Please excuse my brevity.

adam commented

2025-12-29 00:25:29 +01:00

@rumpelsepp commented on GitHub (Jul 6, 2016):

@lukas2511 Please lock this. It is spaming my inbox.

@rumpelsepp commented on GitHub (Jul 6, 2016): @lukas2511 Please lock this. It is spaming my inbox.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/dehydrated#124