Cannot activate new account

RalfJung · November 26, 2015, 4:18pm

I installed Discourse using the launcher at https://github.com/discourse/discourse_docker/. I kept the configuration from samples/standalone.yml almost unchanged, except that I had to change the port 80 because there is an apache running on the host. That apache is now set up to act as reverse proxy, forwarding requests to localhost:8088, which is the port that I bound the Discourse container to.
The admin interface says I am on Discourse version https://github.com/discourse/discourse/tree/3eb0288adb16eae63514657b71ae9c38433a1f5c.

Stuff seems to basically work, I can create an account and create topics etc. However, activating an account does not work: Pressing the button on the confirmation page has no effect. (How did I log in to create a topic, you may wonder? I used the “Forgot Password” functionality.) This is with Firefox 42. The JS error console shows

15:32:40.704 ReferenceError: $ is not defined1 vendor-5939aced2df07b0bcc1c101662121c68.js:1:285

zogstrip · November 26, 2015, 4:21pm

You should update to latest, there was a about that issue (it’s the commit right next to the one you’re at)

https://github.com/discourse/discourse/commit/d6932e4ac44df8aafef89c5f1d3a047a3f261681

RalfJung · November 26, 2015, 6:16pm

Indeed, ./launcher rebuild did it. Thanks!

Now I wonder, can I somehow make it track a stable branch rather than the current development branch?

zogstrip · November 26, 2015, 6:18pm

Just change the version you’re tracking in the app.yml file to “stable” for example

github.com

discourse/discourse_docker/blob/master/samples/standalone.yml#L45


      
          
            ## Which Git revision should this container use? (default: tests-passed)
            #version: tests-passed
          
          env:
            LC_ALL: en_US.UTF-8
            LANG: en_US.UTF-8
            LANGUAGE: en_US.UTF-8
            # DISCOURSE_DEFAULT_LOCALE: en
          
            ## How many concurrent web requests are supported? Depends on memory and CPU cores.
            ## will be set automatically by bootstrap based on detected CPUs, or you can override
            #UNICORN_WORKERS: 3
          
            ## TODO: The domain name this Discourse instance will respond to
            ## Required. Discourse will not work with a bare IP number.
            DISCOURSE_HOSTNAME: 'discourse.example.com'
          
            ## Uncomment if you want the container to be started with the same
            ## hostname (-h option) as specified above (default "$hostname-$config")
            #DOCKER_USE_HOSTNAME: true

RalfJung · November 26, 2015, 6:37pm

Thanks a lot

Can I somehow mark this bug as fixed?

Topic		Replies	Views
Port already in use, what to do? Installation	26	19134	March 6, 2020
Problem setting up Discourse with docker behind Nginx reverse proxy. Encountering SPDY protocol error Installation	2	760	November 23, 2018
Running Discourse docker alongside Apache Installation	7	1614	August 21, 2020
Discourse won't start because port 80 is in use Support	4	1971	July 17, 2020
Install Discourse, change docker port 80 Installation unsupported-install , docker	15	14453	June 8, 2024

Cannot activate new account

Related topics