Error on account activation about docker-image HOT 14 CLOSED

we are working on a new system at the moment which will improve this flow.

from docker-image.

Exactly the same problem. Waiting for a fix.

from docker-image.

Same here. Login with the created password works, tho.

These errors might be related:

"/var/www/sharelatex/web/public/minjs/libs/angular.min.js.map" failed (2: No such file or directory), client: 138.4.3.246, server: _, request: "GET /minjs/libs/angular.min.js.map HTTP/1.1", host: 


114#0: *1034 upstream prematurely closed connection while reading response header from upstream, client: <IP>, server: _, request: "POST /user/password/set HTTP/1.1", upstream: "http://127.0.0.1:3000/user/password/set"

from docker-image.

Creating admin accounts from terminal works. But I cannot create admin accounts for everyone.
An alternative way, for the moment, is to create normal users from terminal with docker command line. But I don't know how.

@balkian Do you know how to create normal user account from command line?

from docker-image.

@zhaozhi0505 try to log in with the user. In my case it works, even after getting that error.

from docker-image.

@balkian Yes it works! So it looks like just the message problem. Thanks!

from docker-image.

@balkian That works for me too, thanks.

from docker-image.

I am having the same issue with the docker image but login still works despite the error. Is there a way to fix this?

from docker-image.

This problem is really annoying because every time I have to tell the user to ignore that message. How can we fix it? @henryoswald

from docker-image.

Seems like this is a general problem, not just one of the docker image, just stumbled over this:
https://github.com/sharelatex/web-sharelatex/issues/392

from docker-image.

Same problem here. I even get the welcome e-mail, but the pass reset is not working.
Is there a workaround for this?
This makes a new installation of sharelatex unusable.

from docker-image.

👍

from docker-image.

I just upgrade the container to version 0.6.1. This bug is fixed. We can close this issue.

from docker-image.

Closed as per @zhaozhi0505 comment

from docker-image.