Hi Manuel, I think we're seeing this generally in docker installations - I think I have a fix proposed for this (the issue appears to be the APP_DOMAIN used in the docker compose file causes this validation error when we check the certificate).
This is the key part of the error message that's showing the problem with the login post validation
HTTP Origin header (http://64.227.102.95:3000) didn't match request.base_url (http://64.227.102.95:3000)
Hi Daniel, Thank you, I copied changes from your PR and it worked.
Few cases to consider:
I ran it on a azure server and its ip-address:3000 showed the same error with the change. I had to connect it to a subdomain with nginx proxy with APP_DOMAIN as subdomain to make it past through the sign in. So environment variable will be a better choice i think
Yes, I think the environment variable is a better solution - the docker-compose file was originally written to support local development using docker (I think we didn't have enough people using it locally to notice the issue you saw with the login submissions failing).
I've merged the changes into the main branch (so you shouldn't need to worry about re-applying that patch going forward). However, do feel free to add any environment variables you need to the compose file or pass them at startup.
For further actions, you may consider blocking this person and/or reporting abuse
Hi Akhil!
The issue is still there, when trying to login there is a blank page after put the credentials: 64.227.102.95:3000/users/sign_in
I tried different things but not able to login when installed forem using docker
Hi Manuel, I think we're seeing this generally in docker installations - I think I have a fix proposed for this (the issue appears to be the APP_DOMAIN used in the docker compose file causes this validation error when we check the certificate).
This is the key part of the error message that's showing the problem with the login post validation
I'm also seeing this reported as github.com/forem/forem/issues/13696 so it's definitely not limited to your installation.
Hi Daniel, Thank you, I copied changes from your PR and it worked.
Few cases to consider:
I ran it on a azure server and its ip-address:3000 showed the same error with the change. I had to connect it to a subdomain with nginx proxy with APP_DOMAIN as subdomain to make it past through the sign in. So environment variable will be a better choice i think
Yes, I think the environment variable is a better solution - the docker-compose file was originally written to support local development using docker (I think we didn't have enough people using it locally to notice the issue you saw with the login submissions failing).
I've merged the changes into the main branch (so you shouldn't need to worry about re-applying that patch going forward). However, do feel free to add any environment variables you need to the compose file or pass them at startup.