Skip to content
This repository has been archived by the owner on Sep 7, 2018. It is now read-only.

Let’s Encrypt: Registration key is already in use #55

Open
beatelite opened this issue Jan 11, 2018 · 9 comments
Open

Let’s Encrypt: Registration key is already in use #55

beatelite opened this issue Jan 11, 2018 · 9 comments

Comments

@beatelite
Copy link

beatelite commented Jan 11, 2018

I added the new beta 08. I had to define the danger_zone constant and hard reset the plugin so I could reinit the certs since reissuing them wasn't working (kept getting "Challenge self check failed for domain" error). Now when I register the account I get:

"Let’s Encrypt: Registration key is already in use"

Any suggestions on where to dig to fix this?

@mterrel
Copy link

mterrel commented Feb 1, 2018

I'm also seeing this error. Here's what I did:

  1. Installed the plugin via the Wordpress backend "Add plugin" and searching for WP Encrypt. Did NOT install manually.
  2. Went to the admin settings page and entered the relevant fields and pressed the Register Account button.
  3. Got an Unknown Error banner on the admin settings page.
  4. Left the admin settings page, came back. Pressed the Register Account button.
  5. Got the Registration key is already in use error. Now I get this error every time I press that button.

@hardcore
Copy link

+1

@BlackGrizzly
Copy link

I have such mistake too! Please correct it!

@nvonbulow
Copy link

You can SSH into your server and delete the letsencrypt folder. This will delete the registration key and will generate a new one.

@beatelite
Copy link
Author

@nvonbulow . Tried that and still having the issue. Did you try it?

@nvonbulow
Copy link

@beatelite It worked, but there are different errors I get (see #56) and then it goes back to that again. They seem to be two different yet connected issues.

@Mamishev
Copy link

Mamishev commented Mar 6, 2018

+1
Anybody help please

@hadirsa
Copy link

hadirsa commented Mar 17, 2018

+1

@elilambnz
Copy link

elilambnz commented Apr 30, 2018

Here's a workaround written by robmason38, his comment can be found on this thread

Comment out the below lines in wp-encrypt -> CertificateManager.php

/**
		 * Retrieves information about a Let's Encrypt account.
		 *
		 * @since 1.0.0
		 * @access public
		 *
		 * @param string $location Endpoint URL for the account.
		 * @return array|WP_Error The response if successful, an error object otherwise.
		 */
		public function get_account( $location ) {
			$response = Client::get()->signed_request( $location, array(
				'resource' => 'reg',
			) );
			if ( is_wp_error( $response ) ) {
				return $response;
			}

			/* Horrible Hack to allow account registration to proceed
			*
			if ( isset( $response['status'] ) && 200 !== absint( $response['status'] ) ) {
				return $this->parse_wp_error( $response );
			}
			*
			*/

			$response['location'] = $location;

			return $response;
		}

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants