nice video, but i have a problem. i used the same configuration and when i click on Administrator Console and acces tkeycloak get me a message: Cookie not found, please make... some idea?
Your configs will have to use "localhost" instead of the Docker service name. For example in your localhost.conf for nginx you'll have to reference keycloak as localhost: instead of :
not working for me; so frustrating. im on my mac trying to set it up on my remote linux server. i tried following your basic steps and also using haproxy. i either get content policy errors or redirect uri issues
Thanks for this really helpful video. I learned a lot. I am attempting to setup Keycloak in a production environment behind Nginx. In that case I need to use "start" instead of "start-dev". I think I need to make some other adjustments to what you have demonstrated here. Any chance of a followup video or blog post for that use-case? Thanks again.
Simply changing "start-dev" to "start" works fine i.e starts Keycloak in prod mode and I can still access it via Nginx. Are you seeing something different on your end?
Thank you for this excellent tutorial. There is an error ("failed to initialize keycloak") when trying to access the account information. Any ideas? Other headers needed?
@@code-215 Any attempt to access an account (eg/realms/myrealm/account). It appears to be a Keycloak CORS issue. Setting Web Origins for the account clients (eg account-console) solved it. Hope this helps someone.
The only way Postgres would ask you for SSL is if you explicitly tell it to using ssl=on. The docker-compose in this video doesn't do that. Check your Postgres config
Thank you for watching this video. Please feel free to buy me a coffee www.buymeacoffee.com/Code215
Very good channel. Keep on. Thanks a lot.
nice video, but i have a problem. i used the same configuration and when i click on Administrator Console and acces tkeycloak get me a message: Cookie not found, please make... some idea?
I'm trying to configure nginx with keycloak executing direct on host machine, without docker, do have any tips how to do that?
Your configs will have to use "localhost" instead of the Docker service name. For example in your localhost.conf for nginx you'll have to reference keycloak as localhost: instead of :
Why are you using start-dev if its for production? Change it to start and see if it works.
Nowhere in my title did I say it's for production. There's a different production video in my channel
not working for me; so frustrating. im on my mac trying to set it up on my remote linux server. i tried following your basic steps and also using haproxy. i either get content policy errors or redirect uri issues
попробуйте отдебажить hostname.
@@sergeyshvyrev969 no I can’t remember exactly the issue but it was something stupid and minor
I want to get the links or content of the files like docker compose, nginx conf etc. Thabks if anyone can help.
Thanks for this really helpful video. I learned a lot. I am attempting to setup Keycloak in a production environment behind Nginx. In that case I need to use "start" instead of "start-dev". I think I need to make some other adjustments to what you have demonstrated here. Any chance of a followup video or blog post for that use-case? Thanks again.
Simply changing "start-dev" to "start" works fine i.e starts Keycloak in prod mode and I can still access it via Nginx. Are you seeing something different on your end?
Hi, have you successfully installed in prodcution mode with https and nginx?
nice video, thank you
Thank you so much Sir
Thank you for this excellent tutorial. There is an error ("failed to initialize keycloak") when trying to access the account information.
Any ideas? Other headers needed?
At what point are you seeing this error?
Is there any more information in the Keycloak server logs?
@@code-215 Any attempt to access an account (eg/realms/myrealm/account). It appears to be a Keycloak CORS issue. Setting Web Origins for the account clients (eg account-console) solved it.
Hope this helps someone.
In my case its requiring the ssl for postgres too
The only way Postgres would ask you for SSL is if you explicitly tell it to using ssl=on. The docker-compose in this video doesn't do that. Check your Postgres config
@@code-215 thank you for your quick response. I solve the problem. It was a syntax error. It worked for me.
Why is 'start-dev' still used?
Because this is the dev setup
Why the thumbnail looks like music video's thumbnail 😂