API
Is there something that I’m missing regarding the API?
I’m running Immich on a truenas scale, and trying to access the API.
And I can’t figure out what I’m doing wrong.
I have tried to configure a reverse proxy before Immich so I get ssl
Reinstall Immich
Install a diffent instant off Immich
Done a curl from the shell
New api keys
New non admin user
But I’m still ending up with http 401
11 Replies
:wave: Hey @Phila54,
Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:.
References
- Container Logs:
docker compose logs docs
- Container Status: docker ps -a docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA
Checklist
I have...
1. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
2. :ballot_box_with_check: read applicable release notes.
3. :ballot_box_with_check: reviewed the FAQs for known issues.
4. :ballot_box_with_check: reviewed Github for known issues.
5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
6. :ballot_box_with_check: uploaded the relevant information (see below).
7. :ballot_box_with_check: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable
(an item can be marked as "complete" by reacting with the appropriate number)
Information
In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:
- Your docker-compose.yml and .env files.
- Logs from all the containers and their status (see above).
- All the troubleshooting steps you've tried so far.
- Any recent changes you've made to Immich or your system.
- Details about your system (both software/OS and hardware).
- Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
- The version of the Immich server, mobile app, and other relevant pieces.
- Any other information that you think might be relevant.
Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)
If this ticket can be closed you can use the /close command, and re-open it later if needed.
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:It would be helpful if you provide some information and not just tick all the boxes
Which endpoint are you trying to hit? Which parameters are you passing? Which body? Which Immich version are you on?
Sorry, I didnt think that I should attach them. Im on version v1.126.1.
I have tried the local ip.
I have done this:
import requests
api_key = 'xx'
url = 'http://192.168.1.52:30041/api/albums'
headers = {
'Authorization': f'Bearer {api_key}'
}
response = requests.get(url, headers=headers)
print(response.json())
And this in local shell and remote:
curl -X GET "http://0.0.0.0:30041/api/albums" \
-H "Authorization: Bearer XX"
And this is the error message.
{'message': 'Invalid user token', 'error': 'Unauthorized', 'statusCode': 401, 'correlationId': 'kjhiwb2o
What my endgoal is to use Immich for wallpanel in homeassistant, where I have no controll of the API call. And that didnt work so I started to troubleshoot and noticed that I cant get the call to work either.
0.0.0.0 isn't a valid ip address for starters
This is what I see in truenas
It binds to 0.0.0.0, which basically says "bind to all interfaces"
That's just a way of showing expressing that though, still not a valid ip address
If you're on that same host you can just use
localhost:30041I used 127.0.0.1 I get the same invalid user token
Api key is not a bearer token
It's an
x-api-keyNice thanks, thats seems to do the trick
This thread has been closed. To re-open, use the button below.