Issues connecting via iphone 11. Get ""Socket operation failed: POST /oauth/config""
31 Replies
UPLOAD_LOCATION=D:\iPhone Photos this could be an issue with the space in the path
what url address did you use on the mobile app?that looks alright
which location is this?
is this the path on my server?
yeah that is the value you put on your
.env file
what is the log of the server? can you access from the web?let me fix that space in the path
yes I can access it via web
can you post the picture of the mobile app on the url screen
yes, will do
let me login via mobile
once I have made change in .emv file do I have to redeploy the container using "docker-compose up -d"
or just stop and start will do the job?
you should do docker-compose down then up
removed space from the path, still same error
can you go into your phone web browser and enter
http://192.168.100.233:2283?yes, working there
via browser
hmm pretty werid, I assume there is no special setting on your server yet besides the default setting?
yes, nothing beside the default
can access it via android app
but not via ios app
uninstsall the app and try again
be sure to grant local network permission
got it working now 🙂
it think I refused the local network permission last time
got it!
many thanks
for your assistance
to make it further secure is it advisable to change:
DB_HOSTNAME=immich_postgres
DB_USERNAME=postgres
DB_PASSWORD=postgres
DB_DATABASE_NAME=immich
username and password here?
and also I changed:
TYPESENSE_API_KEY=1234
would you mind explaining what is this typesense api key?
yes that should be fine
this can be seen as password for your typesense container, so that let's say if you expose your typesense container to the internet, other people without a password cannot access and use your typesense instance
Thank you so much
Do I need to change any settings in .yml if I change DB username and password in .emv?
No you wouldn’t need to
Hmm, then I’m facing issues
this is what I get
DB_USERNAME=postgres
DB_PASSWORD=post
changed the DB_PASSWORD
It will need to be changes before you run the stack I believe
If you already started the stack the user is created with the original password
that is what I did, I believe. I stopped the docker "docker-compose down", amended the .env file and then start the docker "docker-compose up -d"
I meant before starting up the stack for the first time
however FYI, the database is only expose internally for the whole "stack"
Got it fixed.
Thanks