Skip to content
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

HA Sync to sync API config and tokens #97

Closed
babs opened this issue Mar 10, 2021 · 1 comment · Fixed by #115
Closed

HA Sync to sync API config and tokens #97

babs opened this issue Mar 10, 2021 · 1 comment · Fixed by #115
Assignees
Labels
feature request New feature or request

Comments

@babs
Copy link

babs commented Mar 10, 2021

It would be nice if in case of HA setup, to have API's config synced between nodes including keys and tokens.

@jaredhendrickson13
Copy link
Owner

Hey!

This is a good idea. I'll look into it a bit to see if there's an easy way to use the built-in pfSense HA Sync function or if a custom implementation will be needed.

In the meantime, there is a fairly simple way to do this from the command line now if you need something working earlier:

  1. Run pfsense-api backup on the master node.
  2. Copy the /usr/local/share/pfSense-pkg-API/backup.json file from the master node to the same path on the backup node. scp or rsync should be able to do this.
  3. Run pfsense-api restore on the backup node.

@jaredhendrickson13 jaredhendrickson13 added backlog Issues backlogged for inclusion in future releases feature request New feature or request labels Mar 12, 2021
@jaredhendrickson13 jaredhendrickson13 removed the backlog Issues backlogged for inclusion in future releases label Mar 22, 2021
@jaredhendrickson13 jaredhendrickson13 self-assigned this Mar 22, 2021
@jaredhendrickson13 jaredhendrickson13 linked a pull request Apr 8, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants