mirror of
https://github.com/koel/koel.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #1905] The MAC is invalid when docker compose down and up again #1030
Labels
No labels
Authentication
Dependencies
Documentation
Feature Request
Flac
Help Wanted
Installation/Setup
Integration
Mobile
PR Welcome
Pending Release
Performance
Playlist
S3
Search
Sync
[Pri] Low
[Pri] Normal
[Status] Keep Open
[Status] Needs Author Reply
[Status] Needs Review
[Status] Stale
[Status] Will Implement
[Type] Blessed
[Type] Bug
[Type] Duplicate
[Type] Enhancement
[Type] Help Request
[Type] Question
[Type] Task
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/koel-koel#1030
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 @freezy7 on GitHub (Mar 2, 2025).
Original GitHub issue: https://github.com/koel/koel/issues/1905
I initially installed Koel using Docker without any issues. However, being unfamiliar with it, I didn’t record the APP_KEY which was automatically generated during the initialization. This key was in the .env file, but I didn't save it at the time.
Later, I purchased Koel Plus and activated it. However, the collaboration feature isn’t working. I can invite friends, generate invitation links, and see them in my playlist, but they can't access my playlist.
I thought restarting might help, so I used the docker compose down command, which removed the container and reset the .env file. When I started the container again, the website displayed an error: “The MAC is invalid.” This error prevents me from logging into Koel, and I hope to get some help with this.
I think this issue is related to the fact that the data is bound to the APP_KEY. I lost the original APP_KEY, and I’m not sure if there’s any way to retrieve it.
@freezy7 commented on GitHub (Mar 2, 2025):
I have read issue #1781 .They are very similar, the only problem is that I no longer have the original APP_KEY
@phanan commented on GitHub (Mar 2, 2025):
If you've lost the app key I'm afraid there's no way to restore it. Since the license is encrypted with the app key, you basically lost the license, too—but I'm willing to restore it for you, of course. I'm more curious about the issue of not being able to share playlists.
@freezy7 commented on GitHub (Mar 2, 2025):
Alright, I'll have clearing the data and reinstalling it. please help me restore the license key, I will try the playlist share again.
@phanan commented on GitHub (Mar 2, 2025):
Just deactivated your key — you can now use it again. You can also always
do it yourself via LemonSqueezy.
Am So., 2. März 2025 um 20:33 Uhr schrieb Holiday @.***
@freezy7 commented on GitHub (Mar 3, 2025):
this is the screenshot
@phanan commented on GitHub (Mar 3, 2025):
Got it, thanks! I’ll take a look.
On Mon, Mar 3, 2025 at 15:37 Holiday @.***> wrote:
@freezy7 commented on GitHub (Mar 3, 2025):
I found the problem. The playlist I shared didn’t have a folder. After creating a folder and then making a new playlist inside it, the sharing worked.
@phanan commented on GitHub (Mar 3, 2025):
Hmm, that sounds like a bug. You don't need a folder to share playlist.
Am Mo., 3. März 2025 um 17:01 Uhr schrieb Holiday @.***