Viewing 5 replies - 1 through 5 (of 5 total)
  • No. Is there a particular reason you want/need one license for both?

    tim

    Thread Starter dstrawhand

    (@dstrawhand)

    At the point we push everything to production they will then be sharing the same API key. I’ve read if you’re an unpaid member, it’s a little tougher to fix this issue in that you need to reset Wordfence to defaults so that it fetches a new free API key from our scanning server. Is that the most adequate solution?

    Why not install it on staging and production, each with their own key. When you have it configured like you want it on staging and are ready to push to prod, export the settings (bottom of options page) and import into production.

    Would that work?

    tim

    Thread Starter dstrawhand

    (@dstrawhand)

    I guess that will have to do, thank you!

    Generally speaking, when we perform updates will the API key be overwritten each time?

    No. The API and the settings should save in the database unless you select the option to “Delete Wordfence tables and data on deactivation” (near bottom of options page). You can also export the settings just in case they were lost which should save everything including IP addresses and ranges you have blocked.

    tim

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘API key across multiple domains’ is closed to new replies.