-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: no implicit conversion of String into Integer #16
Comments
I just tried updating my own blog's Jekyll verison to 3.7.0 and ran, it still worked..
|
Hey there,
I think what this actually tells me is, that despite using bundle exec, jekyll-gitlab-letsencrypt wants to use my system version of Jekyll and not the one from my gem file. This breaks the functionality of bundle exec at all if I'm not mistaken. |
Hmm, it's failing on this line:
Which would suggest that |
Thanks for your help, I think I was able to isolate the cause of my problem, as the additional logging returns {"error":"404 Not Found"} for me. The next problem for me is now finding out what the Gitlab API wants to hear, as simply using the new name in config does not work. :( But this is definitely not caused by Jekyll-gitlab-letsencrypt. |
After digging further I have found that the token i used previously (api - permission) has no longer sufficient rights to pull such information. After creating a token with more powerful permissions (ticking everything on for testing) it worked. |
Thanks for tracking it down! Keep the issue open, and I'll add some logging/error handling so the next person with an insufficiently-permissioned token gets a clearer message instead of mysterious crashes about strings and integers |
Should be fixed by #17 |
Hey there,
Im currently not able to use jekyll-gitlab-letsencrypt I always get the same error:
jekyll 3.7.0 | Error: no implicit conversion of String into Integer
My Jekyll version is 3.7.0 and Ruby is ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-darwin16]
My config looks like this:
permalink: pretty
sass:
sass_dir: /styles/imports
gitlab-letsencrypt:
Gitlab settings:
personal_access_token: MY TOKEN IS USALLY HERE # GitLab Private Access Token use with env variable
gitlab_repo: 'kindredone/webseite' # Namespaced repository identifier
Domain settings:
email: MY MAIL IS USUALLY HERE # Let's Encrypt email address
domain: 'kindred.one' # Domain that the cert will be issued for
Jekyll settings:
base_path: './' # Where you want the file to go
pretty_url: true # Add a "/" on the end of the URL... set to
true
if you use permalink_style: prettyfilename: 'letsencrypt.html' # What to call the generated challenge file
Delay settings:
initial_delay: 120 # How long to wait for Gitlab CI to push your changes before it starts checking
delay_time: 15 # How long to wait between each check once it starts looking for the file`
I'm not to sure currently what is causing this problem but it seems to always be present, even on commits that previously worked with lets encrypt.
Does anyone else have this problem or knows if it is caused by jekyll-gitlab-letsencrypt and if not of a possible other cause?
My research so far has basically yielded no results at all. :(
The text was updated successfully, but these errors were encountered: