mirror of
https://github.com/photoprism/photoprism.git
synced 2026-03-02 22:57:18 -05:00
error tcp: lookup places.photoprism.app #831
Labels
No labels
ai
android
api
auth
awesome
bug
bug
ci
cli
config
database
declined
deprecated
docker
docs 📚
documents
duplicate
easy
enhancement
enhancement
enhancement
epic
faces
feedback wanted
frontend
hacktoberfest
help wanted
idea
in-progress
incomplete
index
invalid
ios
labels
live
live
low-priority
macos
member-feature
metadata
mobile
nas
needs-analysis
no-coding-required
no-coding-required
observability
performance
places
please-test
plus-feature
priority
pro-feature
question
raspberry-pi
raw
released
released
released
research
resolved
security
sharing
tested
tests
third-party-issue
thumbnails
upgrade
upstream-issue
ux
vector
video
waiting
won't fix
won't fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/photoprism#831
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 @Hurray0 on GitHub (Mar 2, 2021).
Originally assigned to: @lastzero on GitHub.
I use
photoprismby docker, and my docker log shows like below:BTW, in

photoprism, I can find photos with geo data like:So, what may happen that cause the error log?
@lastzero commented on GitHub (Mar 3, 2021):
Works for me, might be an issue with your DSN server? The IP for places.photoprism.app is
185.232.68.65. You'll need it to get additional geodata like country, city and location category.@rickysarraf commented on GitHub (Apr 20, 2021):
Thank you for this wonderful project. I ran into the same problem and stumble on this bug report.
So I followed the basic docker install instructions on your website. I'm assuming that your standard config is designed to work with the default standard docker setup most commonly seen.
Since mine is a non-standard setup, where in a special bridge is used, it could possibly be the reason why names are not resolved inside the container.
For example, I have:
@rickysarraf commented on GitHub (Apr 20, 2021):
I just reverted the custom docker changes and it all worked proper. So my guess is that the bug submitter may be having a similar non-standard setup.
@lastzero commented on GitHub (Apr 20, 2021):
Indeed looks like name resolution (DNS) is not properly configured. If other host names work, it's a problem on our side and we need to fix it ASAP...
@rickysarraf commented on GitHub (Apr 20, 2021):
I think it is a problem only on a non-standard docker setup, where people may have networks other than the default
docker0networking, which ultimately results in a broken resolver.Even the Ubuntu apt repositories from within the container were not resolved, so the resolver issue impact is container-wide.
Now what would be a better default network setup for PhotoPrism is something that should be investigated. From what I see, the resolving of the co-ordinates is one of the service you are relying externally.
I had errors like this:
The bad impact of this broken network setup was that it gave the impression that PhotoPrism was terribly slow, whereas the reality is that for every file, the resolver would ask for the remote host, time out, and then move on to the next item.
@rickysarraf commented on GitHub (Apr 20, 2021):
There was also the case of IPv6, which is a separate issue I had.
This was because my bridge had IPv6 enabled explicitly.
And I guess that resulted in the double delay.
@lastzero commented on GitHub (Jul 5, 2021):
Sounds like this is resolved? Can we close the issue?
@fermulator commented on GitHub (Aug 21, 2022):
Just ran into this as well, it would be nice if photoprism failed to start (using some startup guards/checks) to very DNS/network is functioning properly & completely before proceeding with mega indexing.
@pcwii commented on GitHub (Sep 8, 2022):
I have this issue as well. It is not clear from this thread what the "fix" was for this?
@lastzero commented on GitHub (Sep 8, 2022):
Do not block requests to this IP. Use the manual for the firewall you are using or Google to learn how to configure it properly.
@lastzero commented on GitHub (Sep 8, 2022):
https://docs.photoprism.app/getting-started/faq/#why-do-i-see-connection-errors-when-requesting-maps-api-keys-at-startup