mirror of
https://github.com/anonaddy/anonaddy.git
synced 2026-04-25 06:05:55 +03:00
[GH-ISSUE #617] Invalid MAC after updating #1006
Labels
No labels
bug
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/anonaddy#1006
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 @AdrianColaianni on GitHub (Mar 17, 2024).
Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/617
I am experiencing a "500 | Service Error" when logging in after updating from v0.13.4 to v1.0.9. Upon looking though logs I find the message "The MAC is invalid." from
Encrypter.php. I believe this is the same issue as Issue 333. However, my .env file hasn't changed since Feb 2023 so it is not possible that the APP_KEY changed. When updating, I followed the instructions as they were outlined inSELF_HOSTING.mdand did not accidentally runphp artisan key:generate.@willbrowningme commented on GitHub (Mar 18, 2024):
What's the full stack trace of the error?
If it's the same as in #333 then it appears to be happening when trying to decrypt the
two_factor_secreton the User model.Do you have 2FA enabled?
@AdrianColaianni commented on GitHub (Mar 18, 2024):
I have 2FA enabled, and below are two traces from the error
@willbrowningme commented on GitHub (Mar 18, 2024):
Could you try wrapping your
APP_KEYin your.envfile in double quotes.@AdrianColaianni commented on GitHub (Mar 18, 2024):
No effect, same error message.
@willbrowningme commented on GitHub (Mar 18, 2024):
What if you add
BCRYPT_ROUNDS=10to your.envfile and then run:After that I honestly have no idea I'm afraid, comparing the two versions I cannot see any changes that could have caused this.
The
HasEncryptedAttributes.phptrait is the same - https://github.com/anonaddy/anonaddy/compare/v0.13.4...v1.0.9#diff-b6edb0729ca07e90af550e08b7605f809015a5ccc22c1a16f2e304fadbd787d6@willbrowningme commented on GitHub (Mar 21, 2024):
Any luck trying my previous suggestion?
@AdrianColaianni commented on GitHub (Mar 26, 2024):
It unfortunately didn't fix the issue. I tired reverting versions and that also did not fix it.
@AdrianColaianni commented on GitHub (Mar 29, 2024):
I've nuked the database and effectively reinstalled to get it working (I took backups). Is there a way to set a catch-all on my main domain as a way to get my aliases back?
@AdrianColaianni commented on GitHub (Mar 29, 2024):
I solved this by setting
ANONADDY_ADMIN_USERNAMEto my username, and now any emails sent to non-existant aliases are sent to me.@willbrowningme commented on GitHub (Mar 29, 2024):
Set
ANONADDY_ADMIN_USERNAME=to your account's username in your.envfile.