starred/pocket-id
1
0
Fork 0
mirror of https://github.com/pocket-id/pocket-id.git synced 2025-12-06 09:13:19 +03:00
Code Issues 121 Packages Projects Releases 16 Wiki Activity

🐛 Bug Report: Unsure If I've Configured Pocket-ID Incorrectly, However I Can't Access Pocket-ID's Account Settings Anymore After Updating It To The Latest Pocket-ID Version. #350

New Issue
Closed
opened 2025-10-07 00:11:35 +03:00 by OVERLORD · 7 comments
OVERLORD commented 2025-10-07 00:11:35 +03:00
Owner
Copy Link

Originally created by @ZenDeuo on GitHub.

Reproduction steps

I updated Pocket-ID to the latest version and it just stopped working correctly.

Expected behavior

It should allow me access to my Account's Settings as this is how I manage my Applications that Pocket-ID is linked to.

Actual Behavior

When I login it gets 200 which is good, but then when I try to access https://domain.tld/settings/account it 401's and gives the following error in logs:
[GIN] 2025/02/14 - 05:45:22 | 401 | 73.81µs | ::1 | GET "/api/users/me"
Error #01: You are not signed in

But when I go to https://domain.tld/settings/account it returns all my information that I'm actively logged in with?
Also Applications Pocket-ID is linked to such as my Gitea Instance still function as normal and are accessible using Pocket-ID it's just Pocket-ID itself isn't allowing me to access its settings :(

This is the Logs Image:
Image

And this is what https://domain.tld/api/users/me Returns:
Image

Version and Environment

v0.29.0
I use Cosmos Cloud to run my Containers which helps for easier management through a Web Portal.
These Containers however can also be managed via Docker's CLI as well so in my eyes it's pretty good for everything.
I've setup my .env files as stated in the documentation and used the GitHub Docker-Compose file.

Log Output

This is the Logs Image:
Image

Originally created by @ZenDeuo on GitHub. ### Reproduction steps I updated Pocket-ID to the latest version and it just stopped working correctly. ### Expected behavior It should allow me access to my Account's Settings as this is how I manage my Applications that Pocket-ID is linked to. ### Actual Behavior When I login it gets 200 which is good, but then when I try to access https://domain.tld/settings/account it 401's and gives the following error in logs: [GIN] 2025/02/14 - 05:45:22 | 401 | 73.81µs | ::1 | GET "/api/users/me" Error #01: You are not signed in But when I go to https://domain.tld/settings/account it returns all my information that I'm actively logged in with? Also Applications Pocket-ID is linked to such as my Gitea Instance still function as normal and are accessible using Pocket-ID it's just Pocket-ID itself isn't allowing me to access its settings :( This is the Logs Image: ![Image](https://github.com/user-attachments/assets/8e751ffb-c507-46b6-b2b8-176b4b2f226c) And this is what https://domain.tld/api/users/me Returns: ![Image](https://github.com/user-attachments/assets/8365e6bf-5603-45cf-bf8e-5c5dcdc64fe1) ### Version and Environment v0.29.0 I use Cosmos Cloud to run my Containers which helps for easier management through a Web Portal. These Containers however can also be managed via Docker's CLI as well so in my eyes it's pretty good for everything. I've setup my .env files as stated in the documentation and used the GitHub Docker-Compose file. ### Log Output This is the Logs Image: ![Image](https://github.com/user-attachments/assets/8e751ffb-c507-46b6-b2b8-176b4b2f226c)
OVERLORD added the bug label 2025-10-07 00:11:35 +03:00
OVERLORD commented 2025-10-07 00:11:38 +03:00
Author
Owner
Copy Link

@ZenDeuo commented on GitHub:

Hi there Elias,

I'm sorry for taking a while to respond to this, I didn't expect to be out all day yesterday so I got home late and didn't really have much time to get back to this issue.

Thank you so much for supporting me with this so far.

So I use Firefox but I did install Brave to test this issue within a Chromium Based Browser as you've shown in your Screenshot and also so that I can get to the same place in the Dev Tools.

Here's the Cookie Screenshot from the Applications tab within Dev Tools:
Image

For my .env Files they look like this: (domain.tld replaced with my domain ofc)

  • Backend .env File:

APP_ENV=production
PUBLIC_APP_URL=https://myid.domain.tld
# /!\ If PUBLIC_APP_URL is not a localhost address, it must be HTTPS
DB_PROVIDER=sqlite
# MAXMIND_LICENSE_KEY=fixme # needed for IP geolocation in the audit log
SQLITE_DB_PATH=data/pocket-id.db
POSTGRES_CONNECTION_STRING=postgresql://postgres:postgres@localhost:5432/pocket-id
UPLOAD_PATH=data/uploads
PORT=3000
HOST=0.0.0.0

  • Frontend:

PUBLIC_APP_URL=https://myid.domain.tld
# /!\ If PUBLIC_APP_URL is not a localhost address, it must be HTTPS
INTERNAL_BACKEND_URL=http://localhost:3000

Thanks,
ZenDeuo

@ZenDeuo commented on GitHub: Hi there Elias, I'm sorry for taking a while to respond to this, I didn't expect to be out all day yesterday so I got home late and didn't really have much time to get back to this issue. Thank you so much for supporting me with this so far. So I use Firefox but I did install Brave to test this issue within a Chromium Based Browser as you've shown in your Screenshot and also so that I can get to the same place in the Dev Tools. Here's the Cookie Screenshot from the Applications tab within Dev Tools: ![Image](https://github.com/user-attachments/assets/11eb8f00-8902-4f9b-bc03-375ab3f55c64) For my .env Files they look like this: (domain.tld replaced with my domain ofc) - Backend .env File: <code>APP_ENV=production</code> <code>PUBLIC_APP_URL=https://myid.domain.tld</code> <code># /!\ If PUBLIC_APP_URL is not a localhost address, it must be HTTPS</code> <code>DB_PROVIDER=sqlite</code> <code># MAXMIND_LICENSE_KEY=fixme # needed for IP geolocation in the audit log</code> <code>SQLITE_DB_PATH=data/pocket-id.db</code> <code>POSTGRES_CONNECTION_STRING=postgresql://postgres:postgres@localhost:5432/pocket-id</code> <code>UPLOAD_PATH=data/uploads</code> <code>PORT=3000</code> <code>HOST=0.0.0.0</code> - Frontend: <code>PUBLIC_APP_URL=https://myid.domain.tld</code> <code># /!\ If PUBLIC_APP_URL is not a localhost address, it must be HTTPS</code> <code>INTERNAL_BACKEND_URL=http://localhost:3000</code> Thanks, ZenDeuo
OVERLORD commented 2025-10-07 00:11:38 +03:00
Author
Owner
Copy Link

@ZenDeuo commented on GitHub:

Hi there Elias,

Thanks for the rapid reply, I understand that "You're not signed in" should only get displayed if you're not signed in, however in this case that doesn't happen.

I'm unable to Screen Record at this time due to me not being at home however I'll try to re-explain it as best I can in the steps I follow.

Before I updated the container to the latest version, it would log in perfectly fine and send me straight to domain.tld/settings/account which was the expected behaviour.

Now that it's been updated, when I log in, it just stays on the Login Page and does not move past that, when I try to manually go to domain.tld/settings/account it then throws that log that you see above with the error "Error #01: You are not signed in". That's the unexpected behaviour.

As part of the unexpected behaviour, I kept an eye on the pages that were being called in the logs, I noticed /api/users/me was called so I decided within the same browser to navigate to domain.tld/api/users/me which presented me with the correct details that I was logged in with.

So it doesn't really all make too much sense when it says in the logs I'm not logged in however in the same browser that I logged in with when getting that error, when going to domain.tld/api/users/me it returns that I am logged in.

As for the version, I'm not too sure anymore if I am on the right version or not, I followed the Documentation and used the docker-compose.yml file then started it up as usual following the Documentation.

I will check up on that and see if there's a difference to my docker-compose.yml file, if so I'll make the adjustments and see how that goes and get it to update to the latest version and report back.

Thanks,
ZenDeuo

@ZenDeuo commented on GitHub: Hi there Elias, Thanks for the rapid reply, I understand that "You're not signed in" should only get displayed if you're not signed in, however in this case that doesn't happen. I'm unable to Screen Record at this time due to me not being at home however I'll try to re-explain it as best I can in the steps I follow. Before I updated the container to the latest version, it would log in perfectly fine and send me straight to domain.tld/settings/account which was the expected behaviour. Now that it's been updated, when I log in, it just stays on the Login Page and does not move past that, when I try to manually go to domain.tld/settings/account it then throws that log that you see above with the error "Error #01: You are not signed in". That's the unexpected behaviour. As part of the unexpected behaviour, I kept an eye on the pages that were being called in the logs, I noticed /api/users/me was called so I decided within the same browser to navigate to domain.tld/api/users/me which presented me with the correct details that I was logged in with. So it doesn't really all make too much sense when it says in the logs I'm not logged in however in the same browser that I logged in with when getting that error, when going to domain.tld/api/users/me it returns that I am logged in. As for the version, I'm not too sure anymore if I am on the right version or not, I followed the Documentation and used the docker-compose.yml file then started it up as usual following the Documentation. I will check up on that and see if there's a difference to my docker-compose.yml file, if so I'll make the adjustments and see how that goes and get it to update to the latest version and report back. Thanks, ZenDeuo
OVERLORD commented 2025-10-07 00:11:39 +03:00
Author
Owner
Copy Link

@stonith404 commented on GitHub:

Alright, thanks for your detailed explanation, this really helps.

It seems like the access token cookie doesn't get set or sent correctly. As soon as you're home, could you share a screenshot of the cookies like this:

Image

Make sure to obscure the access token (string starting with "ey") in the screenshot.

Also, what did you set for PUBLIC_APP_URL?

@stonith404 commented on GitHub: Alright, thanks for your detailed explanation, this really helps. It seems like the access token cookie doesn't get set or sent correctly. As soon as you're home, could you share a screenshot of the cookies like this: ![Image](https://github.com/user-attachments/assets/213b25cc-de6c-464c-b44f-a26d32bd57ea) Make sure to obscure the access token (string starting with "ey") in the screenshot. Also, what did you set for `PUBLIC_APP_URL`?
OVERLORD commented 2025-10-07 00:11:39 +03:00
Author
Owner
Copy Link

@stonith404 commented on GitHub:

When I login it gets 200 which is good, but then when I try to access https://domain.tld/settings/account it 401's and gives the following error in logs

But when I go to https://domain.tld/settings/account it returns all my information that I'm actively logged in with?

I'm not sure if I understand it correctly. "You're not signed in" only get displayed after you've logged in? When you manually open the "https://domain.tld/settings/account" page everything works as expected?

If I didn't understand you correctly could you share a screen recording? Also are you really on the latest version, because v0.29.0 isn't the latest?

@stonith404 commented on GitHub: > When I login it gets 200 which is good, but then when I try to access https://domain.tld/settings/account it 401's and gives the following error in logs > But when I go to https://domain.tld/settings/account it returns all my information that I'm actively logged in with? I'm not sure if I understand it correctly. "You're not signed in" only get displayed after you've logged in? When you manually open the "https://domain.tld/settings/account" page everything works as expected? If I didn't understand you correctly could you share a screen recording? Also are you really on the latest version, because `v0.29.0` isn't the latest?
OVERLORD commented 2025-10-07 00:11:41 +03:00
Author
Owner
Copy Link

@ZenDeuo commented on GitHub:

Hi there Elias,

Just a quick update, I've gone ahead and updated the Image that was in my docker-compose file and updated it, but I'm still running into the same issue.

I can go ahead and make an entirely new container to see if this issue gets reproduced there too however at the moment I'm running into the same issue in the logs:

[GIN] 2025/02/14 - 09:23:19 | 401 | 56.04µs | ::1 | GET "/api/users/me"
Error #01: You are not signed in

Even though when I go to domain.tld/api/users/me it shows me my logged in information so I've no idea why it's doing that.

Thanks,
ZenDeuo

@ZenDeuo commented on GitHub: Hi there Elias, Just a quick update, I've gone ahead and updated the Image that was in my docker-compose file and updated it, but I'm still running into the same issue. I can go ahead and make an entirely new container to see if this issue gets reproduced there too however at the moment I'm running into the same issue in the logs: [GIN] 2025/02/14 - 09:23:19 | 401 | 56.04µs | ::1 | GET "/api/users/me" Error #01: You are not signed in Even though when I go to domain.tld/api/users/me it shows me my logged in information so I've no idea why it's doing that. Thanks, ZenDeuo
OVERLORD commented 2025-10-07 00:11:42 +03:00
Author
Owner
Copy Link

@stonith404 commented on GitHub:

Alright that's strange. Thanks for sharing the "solution". Feel free to reopen it when the issue occurs again.

@stonith404 commented on GitHub: Alright that's strange. Thanks for sharing the "solution". Feel free to reopen it when the issue occurs again.
OVERLORD commented 2025-10-07 00:11:42 +03:00
Author
Owner
Copy Link

@ZenDeuo commented on GitHub:

Good Afternoon Elias,

I have managed to fix the issue with the Same Setup that you see above, all I did was recreate the container :)

I don't know what was wrong, maybe a bad file that Docker didn't detect or smth?
But everything is setup the exact same as above and everything is now working again as it did the first time!

Thank you very much for you support I really appreciate it :)

@ZenDeuo commented on GitHub: Good Afternoon Elias, I have managed to fix the issue with the Same Setup that you see above, all I did was recreate the container :) I don't know what was wrong, maybe a bad file that Docker didn't detect or smth? But everything is setup the exact same as above and everything is now working again as it did the first time! Thank you very much for you support I really appreciate it :)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
breaking
bug
documentation
feature
needs more upvotes
open to pull requests
pull-request
Mirrored from GitHub Pull Request
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/pocket-id#350
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?