Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Calls to /api/verify from ip 3.85.226.144 (aws)? #1458

Closed
lakemike opened this issue Aug 5, 2021 · 1 comment
Closed

Calls to /api/verify from ip 3.85.226.144 (aws)? #1458

lakemike opened this issue Aug 5, 2021 · 1 comment
Assignees

Comments

@lakemike
Copy link

lakemike commented Aug 5, 2021

Hi, I'm running photoprism behind a combination of traefik and authelia (2FA). I see some error messages in authelia's docker logs:
error: date='Thu Aug 05 2021 10:20:17 GMT+0000 (UTC)' method='GET', path='/api/verify' requestId='a74d27c6-0bb2-47ae-b631-b7b189b0cf56' sessionId='ojx4qDN-w1nSkhwS30i_dna5exDGo7oG' ip='3.85.226.144' message='Error: User 'unknown' is not sufficiently authorized to access photoprism.mydomain.xx/.'
Reverse DNS says 3.85.226.144 is an AWS server, so somehow photoprism is triggering calls from AWS to my photoprism container. What are these calls to /api/verify and do I need to enable them?
Thanks!

@lastzero
Copy link
Member

lastzero commented Aug 5, 2021

All our API calls use /api/v1/..., so the /api/verify request doesn't seem to come from our client or server. Consider using a VPN if it's a private instance anyway as putting multiple layers of auth in top of PhotoPrism is hard to configure and may take time to experiment e.g. because it impacts browser caching and we're using websockets.

@lastzero lastzero self-assigned this Aug 5, 2021
@photoprism photoprism locked and limited conversation to collaborators Aug 5, 2021
@lastzero lastzero closed this as completed Aug 5, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants