Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to Login using docker-compose example #2

Open
benyanke opened this issue Aug 25, 2018 · 7 comments
Open

Failed to Login using docker-compose example #2

benyanke opened this issue Aug 25, 2018 · 7 comments

Comments

@benyanke
Copy link

Not sure what's up, but seeing no log messages about failure. When using the specified password, it returns to the login screen with no error.

I'm debugging this as well myself but wanted to put a note here.

@benyanke
Copy link
Author

After looking into debugging, it appears I am authenticating successfully, as debug logs state when I set DEBUG_MODE = true.

It appears to be a redirect-after-login issue.

@justinvoelker
Copy link
Collaborator

justinvoelker commented Aug 26, 2018

I believe this is only an issue if you follow the docker-compose example directly without using a reverse proxy. Using the sample docker-compose as-is, you must be accessing Cypht via an IP address and specified port. Not sure why, but I think that is where the problem lies.

If you have some sort of reverse proxy setup (such as jwilder/nginx-proxy or traefik) so that you can access Cypht via a domain/subdomain, the problem disappears. At least, I think that is what gets around this issue.

@a29er
Copy link

a29er commented Aug 27, 2018

The problem is in cookies. After POST request Cypht responds and in one Set-Cookie header sets and then immediately deletes all hm_{id,login,session} cookies. So the next request there are no cookies at all.

@benyanke
Copy link
Author

Is there a mode to run without a proxy, or somewhere I can debug further to resolve it? I'd be happy to PR this if I can get it working, but I'm lost on the actual root cause after several hours.

@allanrbo
Copy link

I had changed the docker-compose.yml file to use an alternative host port, and also ran into this problem. When I changed it back to the default port 80, I was able to login.

@Razvan0925
Copy link
Contributor

For me, setting CYPHT_DISABLE_ORIGIN_CHECK to 1 resolved this problem.

jasonmunro pushed a commit that referenced this issue Nov 12, 2019
add desktop notifications
@marclaporte
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants