-
Notifications
You must be signed in to change notification settings - Fork 43
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
bad decrypt error message on Deployment #35
Comments
Hi @kashifnaseer! We changed the the way the key is decrypted because of deprecation warning. You'll need to encrypt a key again, by following Step 4 in readme. Basically, we added I'll pin this issue for better visibility. |
Yes, just use ***@***.***" or
***@***.***"
instead of ***@***.***" in your workflow
configuration file.
|
Hi, I'm attempting to set this deployment action up for my small Ruby on Rails site. I am experiencing this error. I have re-encrypted the key but it continues to happen. I have looked at @miloserdow comment above but really don't understand what it means. Any ideas on how I can solve this error? Thanks, |
Hi Neil, My comment was edited for some reason (maybe Github thought I posted someone's email address?). Also, 1 comment was removed so I don't understand my reply to it either :) What version of the workflow are you using? You may try |
Hi, @miloserdow I was literally just about to come on here to delete my message as I ran the workflow once more and it worked!!! I'm over the moon that it works. I'm not great at this server stuff but it works. Thankyou so much! I am using miloserdow/capistrano-deploy@master by the way. |
Thanks for this helpful action! Unfortunately, I still get this error when using
If I execute the shown decrypt command locally with the provided password, it works as expected. The only thing I can find is that locally I have |
Anyone else is having this error? Getting the same error and unable to complete the step
Used same version Used the same command to decrypt the key locally and it worked |
Deployment was working fine , but suddenly today i started getting this message, any idea what's happening or why I'm getting this error?
The text was updated successfully, but these errors were encountered: