stoatchat/self-hosted
1
0
Fork 0
mirror of https://github.com/stoatchat/self-hosted.git synced 2026-07-21 04:25:24 -04:00
Code Issues 42 Packages Projects Releases Wiki Activity

bug: Vapid Keys guide is down #54

New Issue
Closed
opened 2026-02-16 12:51:15 -05:00 by yindo · 6 comments
yindo commented 2026-02-16 12:51:15 -05:00
Owner
Copy Link
Copy Source

Originally created by @yllekz on GitHub (Feb 15, 2024).

What happened?

# VAPID keys for push notifications
# Generate using this guide: https://gitlab.insrt.uk/revolt/delta/-/wikis/vapid

Trying to set up revolt and going through the .env file which points me to this guide. The site is unreachable? Unavailable due to hardware failure, working on recovering services – Updates: https://rvlt.gg/GnFjwkqD

I found an archive.org cached copy if needed but just FYI the prod site is down.

https://web.archive.org/web/20230612140827/https://gitlab.insrt.uk/revolt/delta/-/wikis/vapid

Originally created by @yllekz on GitHub (Feb 15, 2024). ### What happened? ``` # VAPID keys for push notifications # Generate using this guide: https://gitlab.insrt.uk/revolt/delta/-/wikis/vapid ``` Trying to set up revolt and going through the .env file which points me to this guide. The site is unreachable? ```Unavailable due to hardware failure, working on recovering services – Updates: https://rvlt.gg/GnFjwkqD``` I found an archive.org cached copy if needed but just FYI the prod site is down. https://web.archive.org/web/20230612140827/https://gitlab.insrt.uk/revolt/delta/-/wikis/vapid
yindo added the bug label 2026-02-16 12:51:15 -05:00
yindo closed this issue 2026-02-16 12:51:15 -05:00
yindo commented 2026-02-16 12:51:16 -05:00
Author
Owner
Copy Link
Copy Source

@Rexogamer commented on GitHub (Mar 28, 2024):

Assuming the archive is up to date, this should be pretty easy to resolve - but where do we want to put the guide? This repo? The dev docs?

@Rexogamer commented on GitHub (Mar 28, 2024): Assuming the archive is up to date, this should be pretty easy to resolve - but where do we want to put the guide? This repo? The dev docs?
yindo commented 2026-02-16 12:51:16 -05:00
Author
Owner
Copy Link
Copy Source

@dillfrescott commented on GitHub (Jun 10, 2024):

Its still down?

@dillfrescott commented on GitHub (Jun 10, 2024): Its still down?
yindo commented 2026-02-16 12:51:16 -05:00
Author
Owner
Copy Link
Copy Source

@mpavkovic commented on GitHub (Jun 23, 2024):

Because the URL is still down, and opening an archived copy takes minutes to load, I'm copy-pasting the instructions here, in case anyone needs them

VAPID keys are used to ensure that nobody else can communicate with your clients.

You can generate a private VAPID key by running:

openssl ecparam -name prime256v1 -genkey -noout -out vapid_private.pem

This creates a PEM private key. In order to use this with the server, you must first base64 encode it, then you can pass it in using an environment variable. (Make sure to remove any newlines)

base64 vapid_private.pem

To convert this to a public key, we run:

openssl ec -in vapid_private.pem -outform DER|tail -c 65|base64|tr '/+' '_-'|tr -d '\n'

The output of this command is what the clients will be receiving.

Source: https://web.archive.org/web/20230612140827/https://gitlab.insrt.uk/revolt/delta/-/wikis/vapid

@mpavkovic commented on GitHub (Jun 23, 2024): Because the URL is still down, and opening an archived copy takes minutes to load, I'm copy-pasting the instructions here, in case anyone needs them > VAPID keys are used to ensure that nobody else can communicate with your clients. > You can generate a private VAPID key by running: ``` openssl ecparam -name prime256v1 -genkey -noout -out vapid_private.pem ``` > This creates a PEM private key. In order to use this with the server, you must first base64 encode it, then you can pass it in using an environment variable. (Make sure to remove any newlines) ``` base64 vapid_private.pem ``` > To convert this to a public key, we run: ``` openssl ec -in vapid_private.pem -outform DER|tail -c 65|base64|tr '/+' '_-'|tr -d '\n' ``` > The output of this command is what the clients will be receiving. Source: https://web.archive.org/web/20230612140827/https://gitlab.insrt.uk/revolt/delta/-/wikis/vapid
yindo commented 2026-02-16 12:51:16 -05:00
Author
Owner
Copy Link
Copy Source

@ne275 commented on GitHub (Jul 9, 2024):

so why we need a vapid keys?

@ne275 commented on GitHub (Jul 9, 2024): so why we need a vapid keys?
yindo commented 2026-02-16 12:51:16 -05:00
Author
Owner
Copy Link
Copy Source

@insertish commented on GitHub (Jul 28, 2024):

so why we need a vapid keys?

Push notifications

@insertish commented on GitHub (Jul 28, 2024): > so why we need a vapid keys? Push notifications
yindo commented 2026-02-16 12:51:16 -05:00
Author
Owner
Copy Link
Copy Source

@insertish commented on GitHub (Jul 28, 2024):

Guide is back up, closing out issue.
Will migrate it at some point though, probably when I rewrite the documentation for the new backend stuff.

@insertish commented on GitHub (Jul 28, 2024): Guide is back up, closing out issue. Will migrate it at some point though, probably when I rewrite the documentation for the new backend stuff.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
enhancement
good first issue
help wanted
improvement
pull-request
Mirrored from GitHub Pull Request
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: stoatchat/self-hosted#54
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?