# About renewal using eab-key **URL:** \ **Category:** Help\ **Created:** [August 26, 2024, 3:04pm UTC](https://community.letsencrypt.org/t/about-renewal-using-eab-key/224658 "2024-08-26T15:04:11Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [August 26, 2024, 4:09pm UTC](https://community.letsencrypt.org/t/about-renewal-using-eab-key/224658/7 "2024-08-26T16:09:50Z")
> [@nsrijay](#): > > But this command works , \*\*sudo certbot renew --force-renewal --deploy-hook /tmp/script.sh \*\* . Is this good enough to ensure that renewal works without the eab settings in conf file ? No, Peter made good point that --dry-run sets the Let's Encrypt Staging server. You look to be using some other CA since you used --server in your first post. And, LE does not require EAB 🙂 As for --force-renewal, be careful to only use that once and not for your regularly scheduled renew. You'd end up getting a cert each time which might cause problems with your CA. And, I'd avoid using --deploy-hook for renew command because that should already be in your renewal profile from your first command. See the /etc/letsencrypt/renewal folder for these profiles I'm not sure my --dry-run suggestion works as-is with alternate CA. I know there was some sort of trick about adding `--server URL` but not sure if that actually works with --dry-run or was some other context. Update: I found a previous thread which talks about --dry-run and --server. Should work > [@My Server is Geoblocked and I don't have DNS or Firewall privileges](https://community.letsencrypt.org/t/my-server-is-geoblocked-and-i-dont-have-dns-or-firewall-privileges/217128/26): > > … --- _[View the full topic](https://community.letsencrypt.org/t/about-renewal-using-eab-key/224658)._