Repository navigation
"Invalid Origin" error after updating to .34 release #3282
Replies: 7 comments
|
Can you ensure that NEXTAUTH_URL is correctly set to the address you're using to access karakeep? |
|
The previous Karakeep version was working fine - the only change was to upgrade to v 0.34. The NEXTAUTH_URL setting didn't change with the upgrade. What does 'Invalid Origin" mean for Karakeep?
…On Tue, Oct 20, 2026 at 5:20 PM Mohamed Bassem ***@***.***> wrote:
*MohamedBassem* left a comment (karakeep-app/karakeep#3215)
<#3215 (comment)>
Can you ensure that NEXTAUTH_URL is correctly set to the address you're
using to access karakeep?
—
Reply to this email directly, view it on GitHub
<#3215?email_source=notifications&email_token=ABPTBHR5MWCH4RYQQKRHUC35U7JK5A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTMMZQGE3TGNBVHEY2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-6301734591>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABPTBHRWCQLDESY4MQJ5JD35U7JK5AVCNFSNUABFKJSXA33TNF2G64TZHM3TKMZVHA4TSNZZHNEXG43VMU5TKOJUHE3TMMJXHEYKC5QC>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
@The-Pezman yes, in 0.34 we changed our auth library and this was an unintended change in behavior. I cant try to restore the previous behavior, but fixing NEXTAUTH_URL should unblock you. |
|
Okay, please let me know how exactly I should fix it. Right now, its setting is:
NEXTAUTH_URL="http://localhost:3000"
…On Sun, Oct 25, 2026, 05:26 Mohamed Bassem ***@***.***> wrote:
*MohamedBassem* left a comment (karakeep-app/karakeep#3215)
<#3215 (comment)>
@The-Pezman <https://github.com/The-Pezman> yes, in 0.34 we changed our
auth library and this was an unintended change in behavior. I cant try to
restore the previous behavior, but fixing NEXTAUTH_URL should unblock you.
—
Reply to this email directly, view it on GitHub
<#3215?email_source=notifications&email_token=ABPTBHTAKNL2PD3PIATZ6DT5VW2JNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTMMZZGU4TENJVGE3KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-6395925516>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABPTBHR25SFG52ZB5PCIYPL5VW2JNAVCNFSNUABFKJSXA33TNF2G64TZHM3TKMZVHA4TSNZZHNEXG43VMU5TKOJUHE3TMMJXHEYKC5QC>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Set it to the address you access karakeep from. |
This indicates how I have set Karakeep up on the server. Hopefully this information can indicate what we need to pass to NEXTAUTH |
|
@The-Pezman the "Invalid Origin" error means the address your browser uses doesn't match Set Then restart the services so the change is picked up (service names can differ by install, check with systemctl restart karakeep-webIf it still fails, check that nginx forwards the original host and protocol to Karakeep, since the check depends on them: location / {
proxy_pass http://127.0.0.1:3000;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Real-IP $remote_addr;
}Notes:
Let me know what address you open Karakeep with and I can check the exact value. |
Uh oh!
There was an error while loading. Please reload this page.
Describe the Bug
I got this error, which I'd never seen before, when attempting to login after updating to the .34 release. Doing a quick search gave me this answer:
However, I've never had a problem with URL redirects, and nothing changed on the nginx server after the update. So I don't know what the issue(s) could possibly be.
Steps to Reproduce
Expected Behaviour
I'd expect to be able to login
Screenshots or Additional Context
No response
Device Details
No response
Exact Karakeep Version
0.34
Environment Details
No response
Debug Logs
No response
Have you checked the troubleshooting guide?
All reactions