mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-09 08:26:00 +02:00
[GH-ISSUE #1065] Project ID error. The sisstem not recognize my firebase-key-file #746
Labels
No labels
ai-generated
android-app
android-app
android-app
🪲 bug
build
build
dependencies
docs
enhancement
enhancement
🔥 HOT
in-progress 🏃
ios
prio:low
prio:low
pull-request
question
🔒 security
server
server
unified-push
web-app
website
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ntfy#746
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @redenfire on GitHub (Mar 23, 2024).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1065
Hi everyone.
I'm on a linux Linux Mint 21.1 x86_64, with Docker version 26.0.0, build 2ae903e. I've installed a self-hosted version on ntfy with auth enabled.
I have a problem with my firebase-key-file. I've generated it with FCM, I download the file and I've mount the /etc/ntfy folder with docker.
The folder is correctly mount.
I tried to use the ENV var NTFY_FIREBASE_KEY_FILE or a server.yml for use my FCM json but the logs output is always this:
This is the content of my file, named vvfy-XXXX.json, where XXX is the rest of project id inside the file:
Can anyone help my?
@redenfire commented on GitHub (Mar 23, 2024):
Resolved!
The file was wrong.
Under Firebase site, I created a new private key into Project settings > Service accounts
The downloaded file need to be linked into container under NTFY_FIREBASE_KEY_FILE env, or in server.yml
After this i downloaded again the google-service.json. This file is necessary for build the apk.
I think this can be useful from someone else, because I didnt undestend the ntfy guide for FCM.
@wunter8 commented on GitHub (Mar 23, 2024):
Thank you for sharing how you got it working!