Skip to content
Discussion options

You must be logged in to vote

I got the same error on a brand new frigate install: I have a work around:
It appears to be due to an older version of py-vapid being shipped in the container. A bug apparently fixed in a newer version of that lib.
web-push-libs/vapid#105

My hack of a fix was to update the library directly.
edit within the running container: /usr/local/lib/python3.11/dist-packages/py_vapid/__init__.py

line 200:
self.private_key = ec.generate_private_key(ec.SECP256R1,
to:
self.private_key = ec.generate_private_key(ec.SECP256R1(),
just add ().

Stop the container; make the changes to enable notifications again; and start it up; the pem file will be generated.
Probably a better way to do this would be to j…

Replies: 7 comments 11 replies

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
1 reply
@NickM-27
Comment options

NickM-27 Oct 17, 2025
Collaborator Sponsor

Comment options

You must be logged in to vote
3 replies
@ThePao89
Comment options

@ThePao89
Comment options

@mihugo
Comment options

Answer selected by revellion
Comment options

You must be logged in to vote
1 reply
@mihugo
Comment options

Comment options

NickM-27
Oct 21, 2025
Collaborator Sponsor

You must be logged in to vote
2 replies
@mihugo
Comment options

@NickM-27
Comment options

NickM-27 Oct 22, 2025
Collaborator Sponsor

Comment options

You must be logged in to vote
4 replies
@revellion
Comment options

@revellion
Comment options

@revellion
Comment options

@hawkeye217
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage
6 participants