vocoder
vocoder
PostsComments
HHomarr
Created by vocoder on 12/18/2024 in #💬・get-help
Redirect URI wrong Protocol
I'm gonna mark this solved so I dont get encouraged to keep the thread going because its good now 🙂 thx again
35 replies
HHomarr
Created by vocoder on 12/18/2024 in #💬・get-help
Redirect URI wrong Protocol
okay! Thank you again. Looks like its working!
35 replies
HHomarr
Created by vocoder on 12/18/2024 in #💬・get-help
Redirect URI wrong Protocol
XD
35 replies
HHomarr
Created by vocoder on 12/18/2024 in #💬・get-help
Redirect URI wrong Protocol
ok, just broken for OIDC in general. The OIDC admin is not being assigned ever. Even starting from scratch doesnt create an admin user
35 replies
HHomarr
Created by vocoder on 12/18/2024 in #💬・get-help
Redirect URI wrong Protocol
Yeah, board not found / you dont have access. On the import. This might be due to how OIDC works? I dont know. Now I'm trying from absolutely zero
35 replies
HHomarr
Created by vocoder on 12/18/2024 in #💬・get-help
Redirect URI wrong Protocol
Going to start from zero and hopefully that helps
35 replies
HHomarr
Created by vocoder on 12/18/2024 in #💬・get-help
Redirect URI wrong Protocol
I think my user is not an admin, which is curious because when it asked, I did correctly assign it to 'admin' which is name of my OIDC admin group claim as well
35 replies
HHomarr
Created by vocoder on 12/18/2024 in #💬・get-help
Redirect URI wrong Protocol
Says I have 4 boards, but when I click on it, it doesn't list any of them. Is this a known issue that's unrelated? 
volumes:
      - ${DOCKER_PATH}/${CONFIG_PATH}/homarr/appdata:/appdata
volumes:
      - ${DOCKER_PATH}/${CONFIG_PATH}/homarr/appdata:/appdata
I'll probably just make a new one and hopefully that one shows up
35 replies
HHomarr
Created by vocoder on 12/18/2024 in #💬・get-help
Redirect URI wrong Protocol
Thanks for your assistance, now I can play
35 replies
HHomarr
Created by vocoder on 12/18/2024 in #💬・get-help
Redirect URI wrong Protocol
Yay 🙂
35 replies
HHomarr
Created by vocoder on 12/18/2024 in #💬・get-help
Redirect URI wrong Protocol
Worked
35 replies
HHomarr
Created by vocoder on 12/18/2024 in #💬・get-help
Redirect URI wrong Protocol
2024-12-23T13:20:54.001Z info: ➕ Connection (2) GET /websockets
2024-12-23T13:20:54.002Z info: tRPC request from unknown by user 'undefined (undefined)'
 ⚠ The "images.domains" configuration is deprecated. Please use "images.remotePatterns" configuration instead.
2024-12-23T13:20:55.124Z info: The callback of 'mediaServer' cron job succeeded (before callback took 0 ms, callback took 2 ms)
2024-12-23T13:20:55.124Z info: The callback of 'downloads' cron job succeeded (before callback took 0 ms, callback took 2 ms)
2024-12-23T13:20:55.124Z info: The callback of 'dnsHole' cron job succeeded (before callback took 0 ms, callback took 2 ms)
2024-12-23T13:20:55.124Z info: The callback of 'healthMonitoring' cron job succeeded (before callback took 0 ms, callback took 2 ms)
2024-12-23T13:20:57.826Z info: tRPC request from server-fetch by user 'undefined (undefined)'
2024-12-23T13:20:57.836Z info: tRPC request from server-fetch by user 'undefined (undefined)'
2024-12-23T13:20:57.846Z info: tRPC request from rsc by user 'undefined (undefined)'
2024-12-23T13:20:58.794Z info: tRPC request from server-fetch by user 'undefined (undefined)'
2024-12-23T13:20:58.800Z info: tRPC request from server-fetch by user 'undefined (undefined)'
2024-12-23T13:20:59.205Z info: ➖ Connection (1) 1001 
2024-12-23T13:20:54.001Z info: ➕ Connection (2) GET /websockets
2024-12-23T13:20:54.002Z info: tRPC request from unknown by user 'undefined (undefined)'
 ⚠ The "images.domains" configuration is deprecated. Please use "images.remotePatterns" configuration instead.
2024-12-23T13:20:55.124Z info: The callback of 'mediaServer' cron job succeeded (before callback took 0 ms, callback took 2 ms)
2024-12-23T13:20:55.124Z info: The callback of 'downloads' cron job succeeded (before callback took 0 ms, callback took 2 ms)
2024-12-23T13:20:55.124Z info: The callback of 'dnsHole' cron job succeeded (before callback took 0 ms, callback took 2 ms)
2024-12-23T13:20:55.124Z info: The callback of 'healthMonitoring' cron job succeeded (before callback took 0 ms, callback took 2 ms)
2024-12-23T13:20:57.826Z info: tRPC request from server-fetch by user 'undefined (undefined)'
2024-12-23T13:20:57.836Z info: tRPC request from server-fetch by user 'undefined (undefined)'
2024-12-23T13:20:57.846Z info: tRPC request from rsc by user 'undefined (undefined)'
2024-12-23T13:20:58.794Z info: tRPC request from server-fetch by user 'undefined (undefined)'
2024-12-23T13:20:58.800Z info: tRPC request from server-fetch by user 'undefined (undefined)'
2024-12-23T13:20:59.205Z info: ➖ Connection (1) 1001
35 replies
HHomarr
Created by vocoder on 12/18/2024 in #💬・get-help
Redirect URI wrong Protocol
Same error unfortunately using the oidc-redirect-fallback-https , the redirect_uri still produces a http link for me. I tried docker compose down homarr then pruned the image, then pulled it fresh, same issue.
35 replies
HHomarr
Created by vocoder on 12/18/2024 in #💬・get-help
Redirect URI wrong Protocol
Okay! Thank you will try shortly here and report / edit my result back. Thank you for your attention to this!
35 replies
HHomarr
Created by vocoder on 12/18/2024 in #💬・get-help
Redirect URI wrong Protocol
https://github.com/homarr-labs/homarr/blob/dev/nginx.conf#L24 also, not an expert on if homarr is implementing more overrides, but isnt the $scheme here going to resolve as http (never s) if it's coming from a internal http server with that fixed proxy_pass? In the tests: also: https://github.com/homarr-labs/homarr/blob/b6dc38483d81ddbbebb9ea35c78bacff516a0e0b/packages/auth/test/redirect.spec.ts#L6 really not sure this should be supported given the methods of data transmission used in client_secret_post or pkce or the sha256 encryption to send the token clear. Authelia simply errors if yours is http.
35 replies
HHomarr
Created by vocoder on 12/18/2024 in #💬・get-help
Redirect URI wrong Protocol
Then you're not relying on headers to determine this. FWIW, I am passing the X-FORWARDED-PROTO via SWAG to the homarr container, but as you know, it runs multiple websockets. Maybe the layering is throwing the variable off (or not being passed through)? If the internal homarr (nginx) webserver supported TLS that would also negate this issue 🙂
35 replies
HHomarr
Created by vocoder on 12/18/2024 in #💬・get-help
Redirect URI wrong Protocol
Since a OpenID/OAuth redirectURI is invalid as HTTP, can you just replace baseUrl here with https if its http? https://github.com/homarr-labs/homarr/blob/3b7e6cc083220a0e3a0cf4f5243c073067ba5bc7/packages/auth/redirect.ts#L16
35 replies
HHomarr
Created by vocoder on 12/18/2024 in #💬・get-help
Redirect URI wrong Protocol
Debian... docker, beta branch tag... docker-compose... with AUTH_OIDC_ISSUER: https://auth.${DOMAIN_NAME} and all associated fields.. edit: verified the beta is the right version and the checker is wrong, maybe an actions issue there
35 replies
HHomarr
Created by vocoder on 12/18/2024 in #💬・get-help
Redirect URI wrong Protocol
Tried to send send the headers as all lower case.. edit.. no dice. Maybe there should just be an option to override this? I'm also seeing Partitioned cookie or storage access was provided to in my browser ... like process.env.force_http_proto || {proto} would fix this ... stuck here, & rolled back for now
35 replies