Skip to content

issues Search Results · repo:rolodato/gitlab-letsencrypt language:JavaScript

Filter by

40 results
 (65 ms)

40 results

inrolodato/gitlab-letsencrypt (press backspace or delete to remove)

Build process can take some time, so challenge file can be invalid when published: $ gitlab-le --token xxxxxx --path /acme-challenge --jekyll --email xx@xx.xx --production --repository https://gitlab.com/xxx/xxx ...
  • iBobik
  • 2
  • Opened 
    on May 1, 2019
  • #53

An --ignore-cert-errors switch might be useful here as I d assume this would be a pretty common use case. # gitlab-le --email foo@bar.com --token 1234 --domain blog.example.com --repository https://gitlab.com/foo/bar.gitlab.io ...
  • lyarwood
  • Opened 
    on Jan 9, 2019
  • #52

How can I force gitlab-letsencrypt to upload the acme challenge to another branch than master? I got a CI/CD pipeline which depends on another branch, since I cloned the project and got the original Jekyll ...
  • marbetschar
  • 2
  • Opened 
    on Dec 13, 2018
  • #51

Following this format gitlab-le \ --email example@example.com --domain example.com www.example.com --repository https://gitlab.com/gitlab_user/gitlab_repo --token ...
  • babakness
  • 1
  • Opened 
    on May 21, 2018
  • #47

Hey, I m stuck waiting for pages to be generated with the authorization file in place to continue, but because the job is waiting it isn t continuing on to actually build the site for pages. Whats some ...
  • Jackbennett
  • 1
  • Opened 
    on May 18, 2018
  • #46

When I run this: npm i -g gitlab-letsencrypt I get this error: npm ERR! code 1 npm ERR! Command failed: /usr/bin/git clone --depth=1 -q -b v2.1.0 https://github.com/rolodato/le-acme-core.git /Users/konsumer/.npm/_cacache/tmp/git-clone-55f7ccb3 ...
  • konsumer
  • Opened 
    on Apr 27, 2018
  • #45

For the benefit of others: the default behaviour of creating the challenge file in public/.well-known/acme-challenge/ does not work with the HUGO static site generator (https://gohugo.io). The fix is relatively ...
  • vkehayas
  • Opened 
    on Mar 31, 2018
  • #44

node: v9.0.0 npm: 5.5.1 I cant install it to ubuntu, it shows; npm ERR! code ENOVERSIONS npm ERR! No valid versions available for le-acme-core A complete log of this run can be found in: npm ERR! /home/saint/.npm/_logs/2018-01-27T23_16_57_128Z-debug.log ...
  • alchemistsaint
  • 2
  • Opened 
    on Jan 27, 2018
  • #43

When trying to download and install version 3.1.0 using the command line $ npm install -g --user root --prefix pkg/usr --cache src/npm-cache gitlab-letsencrypt@3.1.0 I get the following error output: ...
  • rffontenelle
  • 4
  • Opened 
    on Jan 22, 2018
  • #42

I would love to see more logging about what is happening. I gladly do this myself, once #38 is merged ;)
  • leipert
  • Opened 
    on Jan 17, 2018
  • #41
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.