Quantcast
Channel: Discourse Meta - Latest topics
Viewing all 60707 articles
Browse latest View live

Customized Discourse Help Needed (requests below)

$
0
0

@Jonathan_Drake wrote:

Our requests:

What we (ideally) need from Discourse over time:

§ Membership area
§ Host video recordings
§ Ability to submit assignments using forms
§ Ability to have unrated (or not rated enough times) assignments show up for feedback and rating
§ Ability to view the feedback and rating that your assignment has received
§ Ability to rate feedback received
§ Ability for our team to see the feedback that has been tagged as not good
§ Ability to get a report by participant in terms of how many assignments they have submitted, rated, feedback on their ratings
§ Ability to get a report by assignment ranked by rating that people got so we can look at highly-rated assignments and showcase them, we can look at highly rated assignments and identify ones that are not on the mark and low rated assignments to see where people tripped up
§ Ability to give people badges based on for e.g., how many assignments they have rated

We already have our install up and running but just out of the box.

Looking to get started right away.

Posts: 1

Participants: 1

Read full topic


Unsolving a topic does not remove the icon in the topic list

$
0
0

@chrisalley wrote:

With the Discourse Solved plugin, if I uncheck the "Solved" checkbox in a topic, the tick icon is not removed from left of the topic title in the main topic list. This occurs when I uncheck the Solved checkbox, then click the forum logo to return to the main topic list. It does not occur if I reload the whole app using the browser's reload button; the checkbox will no longer appear next to the topic title in that case (as expected).

Posts: 2

Participants: 2

Read full topic

Unable to rebuild app after changing app.yml

$
0
0

@Will_Graham wrote:

I have made changes to the app.yml file through the DigitalOcean Droplet Console and I'm trying to rebuild the container.

I entered ./launcher rebuild app and it returns -bash: ./launcher: No such file or directory

Does anyone know how to solve this?

Posts: 4

Participants: 2

Read full topic

Problems with Feature Voting plugin

$
0
0

@Trash wrote:

Continuing the discussion from Discourse Feature Voting:

Installed yesterday, but I see a lot of fatal errors in logs:

/var/www/discourse/plugins/discourse-feature-voting/plugin.rb:49:in `user_voted'
(eval):52:in `_fast_attributes'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/active_model_serializers-0.8.3/lib/active_model/serializer.rb:467:in `rescue in attributes'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/active_model_serializers-0.8.3/lib/active_model/serializer.rb:455:in `attributes'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/active_model_serializers-0.8.3/lib/active_model/serializer.rb:479:in `_serializable_hash'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/active_model_serializers-0.8.3/lib/active_model/serializer.rb:361:in `serializable_hash'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/active_model_serializers-0.8.3/lib/active_model/serializer.rb:349:in `as_json'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/multi_json-1.11.2/lib/multi_json/adapters/oj.rb:21:in `dump'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/multi_json-1.11.2/lib/multi_json/adapters/oj.rb:21:in `dump'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/multi_json-1.11.2/lib/multi_json/adapter.rb:25:in `dump'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/multi_json-1.11.2/lib/multi_json.rb:136:in `dump'
/var/www/discourse/app/controllers/topics_controller.rb:579:in `block (2 levels) in perform_show_response'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal/mime_responds.rb:217:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal/mime_responds.rb:217:in `respond_to'
/var/www/discourse/app/controllers/topics_controller.rb:576:in `perform_show_response'
/var/www/discourse/app/controllers/topics_controller.rb:93:in `show'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/abstract_controller/base.rb:198:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal/rendering.rb:10:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:117:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:117:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:555:in `block (2 levels) in compile'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:505:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:505:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:92:in `__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:778:in `_run_process_action_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:81:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/abstract_controller/callbacks.rb:19:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal/rescue.rb:29:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/notifications.rb:164:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/notifications.rb:164:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/abstract_controller/base.rb:137:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.2.6/lib/action_view/rendering.rb:30:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.9.2/lib/mini_profiler/profiling_methods.rb:76:in `block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal.rb:196:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal.rb:237:in `block in action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/routing/route_set.rb:74:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/routing/route_set.rb:74:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/routing/route_set.rb:43:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/journey/router.rb:43:in `block in serve'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/journey/router.rb:30:in `each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/journey/router.rb:30:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/routing/route_set.rb:817:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/builder.rb:63:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/conditionalget.rb:25:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/head.rb:13:in `call'
/var/www/discourse/lib/middleware/anonymous_cache.rb:127:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/flash.rb:260:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/session/abstract/id.rb:225:in `context'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/session/abstract/id.rb:220:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/cookies.rb:560:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/query_cache.rb:36:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/connection_pool.rb:653:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:88:in `__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:778:in `_run_call_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:81:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/remote_ip.rb:78:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/logster-1.2.2/lib/logster/middleware/reporter.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.6/lib/rails/rack/logger.rb:38:in `call_app'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.6/lib/rails/rack/logger.rb:22:in `call'
/var/www/discourse/config/initializers/100-quiet_logger.rb:13:in `call_with_quiet_assets'
/var/www/discourse/config/initializers/100-silence_logger.rb:26:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/request_id.rb:21:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/methodoverride.rb:22:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/runtime.rb:18:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/sendfile.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.9.2/lib/mini_profiler/profiler.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-2.0.0.beta.5/lib/message_bus/rack/middleware.rb:60:in `call'
/var/www/discourse/lib/middleware/request_tracker.rb:73:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.6/lib/rails/engine.rb:518:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.6/lib/rails/application.rb:165:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.6/lib/rails/railtie.rb:194:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.6/lib/rails/railtie.rb:194:in `method_missing'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/urlmap.rb:66:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/urlmap.rb:50:in `each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/urlmap.rb:50:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-5.0.1/lib/unicorn/http_server.rb:562:in `process_client'
/var/www/discourse/lib/scheduler/defer.rb:85:in `process_client'
/var/www/discourse/lib/middleware/unicorn_oobgc.rb:95:in `process_client'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-5.0.1/lib/unicorn/http_server.rb:658:in `worker_loop'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-5.0.1/lib/unicorn/http_server.rb:508:in `spawn_missing_workers'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-5.0.1/lib/unicorn/http_server.rb:132:in `start'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-5.0.1/bin/unicorn:126:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.0.0/bin/unicorn:22:in `load'
/var/www/discourse/vendor/bundle/ruby/2.0.0/bin/unicorn:22:in `<main>'

After some hours most users could not access the forum (blank page). This morning we have disabled Feature Voting plugin and we resolve the problem.

Maybe a contrast with Topic Counter Visitor plugin?

Those are the plugins installed:

@joebuhlig, we really :heart: Feature Voting plugin, if it is possible we want to reinstall it as soon as possible.
Thanks in advance!

Posts: 11

Participants: 2

Read full topic

How to change nginx log rotation period

$
0
0

@gearoid wrote:

How can I change this and have it retained across upgrades ?

If I edit the web.template.yml in /var/discourse/templates I get a problem pulling new versions.

Posts: 3

Participants: 2

Read full topic

Sharing / inviting to non-topic pages

$
0
0

@charleswalter wrote:

Has there ever been discussion about making it easy to share non-topic pages? Our topic lists are like individual communities for us, and it would be great if the users could invite their friends to join their communities.

Thought it would be worth separating this topic from the points brought up by @tgxworld

Continuing the discussion from Add to homescreen banner on Android:

Posts: 1

Participants: 1

Read full topic

After backup restore on other server, uploaded images are broken

$
0
0

@yadlabus wrote:

Hello guys!

I have 2 instances of the same forum: an old one hosted in DigitalOcean, and a new one hosted on our company server and accessible only on our company intranet. I am original admin of the old forum only.

The backup of 1st forum has been restored to the new one, everything worked fine except user uploaded images in posts. They are all broken.

As you can see in this snapshot where I edit a post with a broken image, the image does appear in the preview and the url seems to be relative, so I assume it points to the picture hosted on the new intranet server.

But the link on the rendered post is absolute and refers to the old forum (inaccessible from our intranet):
https://www.oldforum.com/uploads/default/original/1X/be73346d397d355ee1e03e817a2beecfac28bad3.png

It should point to https://www.newforum.com/uploads/...

What can I do to solve this issue? :worried:

PS: I'm far from a specialist, I somehow managed to set up my first discourse instance following the great step-by-step guides available out there...

Thanks!

Posts: 4

Participants: 3

Read full topic

Getting UnknownHostError from Gem::RemoteFetcher on new install

$
0
0

@Law wrote:

I've just done a fresh install as I couldn't view site any more randomly.

I had a backup so I didn't mind.

But following the guide to a T it does not want to build?

Ubuntu 16.04

It work perfectly before hand. Nothing has changed?

Fresh Ubuntu + SSH setup + Static IP.

Then follow guide and it fails.

From viewing the logs. This gets repeated alot.

There are lots of these?? also.
Gem::RemoteFetcher::UnknownHostError: no such name (https://rubygems.org/gems/tilt-2.0.2.gem
Gem::RemoteFetcher::UnknownHostError: no such name (https://rubygems.org/gems/sprockets-3.6.0.gem)
Gem::RemoteFetcher::UnknownHostError: no such name (https://rubygems.org/gems/message_bus-2.0.0.beta.5.gem)

Bottom Error
RuntimeError: cd /var/www/discourse && su discourse -c 'bundle install --deployment --verbose --without test --without development' failed with return #
Location of failure: /pups/lib/pups/exec_command.rb:105:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"bundle_exec", "cmd"=>["su discourse -c 'bundle install --deployment --verbose --without test --without development'", "su discourse -c 'bundle exec rake db:migrate'", "su discourse -c 'bundle exec rake assets:precompile'"]}
5f5ec921ad61417df5f46f7dc328840d2138bce08457b43626d3192876773143

Posts: 6

Participants: 2

Read full topic


Removed banner message in user digest emails

$
0
0

@jpalermo wrote:

Hello; my organization recently posted our first banner in our Discourse community to promote a live chat, but when we took it down afterwards, one of our users reported getting the following message in their community digest email: "This topic is no longer a banner. It will no longer appear at the top of every page."

Can someone tell me why removing the banner would show up publicly and in the digest email? Do all users get this in their digest? Is there a way to prevent this from happening again? We like the banner feature, but don't want our user community to get these kinds of notifications:

Posts: 2

Participants: 2

Read full topic

I want to move the Facebook and Twitter share buttons to post menu

$
0
0

@stevenpslade wrote:

Continuing the discussion from How can I custom share button?:

I have added new post menu items for sharing to Facebook and Twitter.

They do not have any functionality yet though. I was looking to hopefully piggy back on action of the original share actions for facebook and twitter but I am struggling with doing so.

I was also looking at the api documentation for adding a new share source, but it has not helped.

What do I need to do to copy the share action of the current facebook and twitter buttons and place them on the post menu items I have created.

Posts: 1

Participants: 1

Read full topic

502 Bad gateway error after switching to SSL

$
0
0

@MattCHM wrote:

Hi, I'm getting started with running Discourse on a Digital Ocean Ubunto 14.04 LEMP droplet, alongside WordPress. Everything was running fine, using the SSO WordPress plugin for Discourse. Discourse is in a subdomain.

I subsequently installed a wildcard SSL. WordPress is running fine, but when I try to connect to Discourse I get a 502 Bad gateway error. I have tried editing the /etc/nginx/sites-enabled/default file and /etc/nginx/conf.d/discourse.conf with no success. This isn't really my area and I can see I'm going to make things worse if it keep tinkering...

This is the content of /etc/nginx/conf.d/discourse.conf

server {
        listen 80; listen [::]:80;
        server_name forum.mydomain.com;  # <-- change this
        return 301 https://$host$request_uri;
}
server {
    listen 443 ssl spdy;
    listen [::]:443 ssl spdy;
    server_name forum.mydomain.com;  # <-- change this

    ssl on;
    ssl_certificate     /usr/local/etc/ssl/pusslcert.crt;
    ssl_certificate_key /usr/local/etc/ssl/pusslcertprivate.key;
    ssl_dhparam        /usr/local/etc/ssl/dhparam.pem;
    ssl_ciphers ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM$

    # enable SPDY header compression
    spdy_headers_comp 6;
    spdy_keepalive_timeout 300; # up from 180 secs default

    location / {
        proxy_pass https://unix:/var/discourse/shared/standalone/nginx.https.sock:;
        proxy_set_header Host $http_host;
        proxy_http_version 1.1;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    }
}

This is the content of cd /etc/nginx/sites-enabled/default

server {
        listen 80 default_server;
	listen [::]:80 default_server ipv6only=on;

        root /usr/share/nginx/html;
        index index.php index.html index.htm;
        # Make site accessible from http://localhost/
        server_name mydomain.com;
        location / {
                 try_files $uri $uri/ /index.php?$args;
        }

	location ~ \.php$ {
		try_files $uri =404;
		fastcgi_split_path_info ^(.+\.php)(/.+)$;
		fastcgi_pass unix:/var/run/php5-fpm.sock;
		fastcgi_index index.php;
		fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
		include fastcgi_params;
	}
}

# HTTPS server
#
server {
        listen 443 default ssl;
        listen [::]:443 ssl;
        server_name mydomain.com;
        ssl_certificate /usr/local/etc/ssl/pusslcert.crt;
        ssl_certificate_key /usr/local/etc/ssl/pusslcertprivate.key;
        ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
        ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES25$
        ssl_prefer_server_ciphers on;
        root /usr/share/nginx/html;
        index index.php index.html index.htm;
	location / {
                 try_files $uri $uri/ /index.php?$args;
        }
	location ~ \.php$ {
		try_files $uri =404;
		fastcgi_split_path_info ^(.+\.php)(/.+)$;
		fastcgi_pass unix:/var/run/php5-fpm.sock;
		fastcgi_index index.php;
		fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
		include fastcgi_params;
	}
}

These are from the /var/log/nginx/error.log

2016/04/29 21:54:21 [crit] 3680#0: *1299 connect() to unix:/var/discourse/shared/standalone/nginx.https.sock failed (2: No such file or directory) while connecting to upstream, client: 58.175.118.49, server: forum.mydomain.com, request: "GET / HTTP/1.1", upstream: "https://unix:/var/discourse/shared/standalone/nginx.https.sock:/", host: "forum.mydomain.com"
2016/04/29 21:54:22 [crit] 3680#0: *1299 connect() to unix:/var/discourse/shared/standalone/nginx.https.sock failed (2: No such file or directory) while connecting to upstream, client: 58.175.118.49, server: forum.mydomain.com, request: "GET /favicon.ico HTTP/1.1", upstream: "https://unix:/var/discourse/shared/standalone/nginx.https.sock:/favicon.ico", host: "forum.mydomain.com", referrer: "https://forum.mydomain.com/"

I'm afraid I'm not sure what this is telling me or what needs to be done to fix it. Obviously mydomain.com has been changed and is correct in the actual files.

In /var/discourse/containers/app.yml the following ports are exposed:

 - "2222:22" # If you don't need to use ./launcher ssh app, you can remove this too

Can anyone advise me on what I need to edit? If its a bigger job I'm happy to pay someone with the expertise to fix this. Perhaps PM me if that's the case.

Posts: 1

Participants: 1

Read full topic

Unable to take complete backup

$
0
0

@Nitaishyamdas wrote:

I am trying to take backup ( with files ) from UI but it remains stuck at " Removing '.tar' leftovers... "

[2016-04-30 02:19:55] Removing old backups...
[2016-04-30 02:19:55] Cleaning stuff up...
[2016-04-30 02:19:55] Removing '.tar' leftovers...

When I type pg_dump in discourse then it says:-

pg_dump: [archiver (db)] connection to database "root" failed: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?

How can I take complete backup?

Posts: 4

Participants: 3

Read full topic

Not sending Mandrill emails due to "SMTPAuthenticationError"

$
0
0

@stevenpslade wrote:

I currently see this error message in the dashboard:

Some problems have been found with your installation of Discourse:
There are 181 email jobs that failed. Check your app.yml and ensure that the mail server settings are correct. See the failed jobs in Sidekiq.

I check Sidekiq and it is this error over and over:

Jobs::HandledExceptionWrapper: Wrapped Net::SMTPAuthenticationError: 435 4.7.8 Error: authentication failed:

I have not messed with app.yml file or any email settings recently. I am running v1.6.0.beta1. Help!

Posts: 5

Participants: 3

Read full topic

Can email address remain hidden when using sso?

$
0
0

@nisbeti wrote:

I have an education site that needs a forum for students and tutors to discuss. I want to use sso as users are already signed up with their email / their parent's email. But I want their email address to remain hidden from other students and tutors, while still actually receiving emails from discourse when their @username is mentioned, for example. Is this possible / easily achievable?

Posts: 2

Participants: 2

Read full topic

Should I be worried of these error messages>

$
0
0

@envieme wrote:

(facebook) Authentication failure! csrf_detected: OmniAuth::Strategies::OAuth2::CallbackError, csrf_detected | CSRF detected

See this once in a while, like every few days.

Posts: 1

Participants: 1

Read full topic


Auto focus cursor in search box on mobile

$
0
0

@charleswalter wrote:

When users tap on magnifying glass on mobile, It would provide a smoother experience if we could auto-focus the cursor in the search box and bring up the keyboard. Any issues with this?

Posts: 3

Participants: 2

Read full topic

Easier insert-new-topic process

$
0
0

@Pad_Pors wrote:

i want to see if it is a good idea to have a simple empty box new to the "+new topic" button, in order to reduce the barriers to insert new topics.

something like this, which when you type in it, you are typing the subject of your new topic:

and then after you click on the "+ new topic" button, the rest of the box come out.

Posts: 3

Participants: 2

Read full topic

Vague error from clicking on a tag link on this site

How to find out if user is logged in and insert some js

$
0
0

@envieme wrote:

Hope someone can help me with this.

I want to insert a getsitecontrol.com script to ask our members to subscribe to a newsletter. But I want this only to be shown for members.

I tried doing this using jQuery in Admin > Customize > CSS/HTML >

<script>
$(document).ready(function(){
if((Discourse.User.current()))
{ $('<script>')
    .attr('type', 'text/javascript')
    .text('(function (w,i,d,g,e,t,s) {w[d] = w[d]||[];t= i.createElement(g);
    t.async=1;t.src=e;s=i.getElementsByTagName(g)[0];s.parentNode.insertBefore(t, s);
  })(window, document, '_gscq','script','//widgets.getsitecontrol.com/xxxx/script.js');')
    .appendTo('body');
}
else {
}});
</script>

But it doesn't seem to work. No errors on the console too. Can someone help please?

Posts: 1

Participants: 1

Read full topic

Error sending emails

$
0
0

@Benninger wrote:

Hello all,

my discourse installation has been offline for 6 months. Now I reactivated the server, updated Ubuntu, Docker and Discourse and almost everything is running again - except sending emails :frowning: (The old mandrill settings used to work - I have to change them due to mandrills ... you know)

The settings seem to be correct (although the setting DISCOURSE_SMTP_ENABLE_START_TLS: false seems to be ignored. the admin interface shows enable_starttls_auto = true)

production.log shows:

Started POST "/admin/email/test" for xxx.xxx.xxx.xxx at 2016-04-30 08:54:23 +0000
Processing by Admin::EmailController#test as /
Parameters: {"email_address"=>"xxx@xxx.de"}
Sent mail to xxx@xxx.de (47.4ms)
Completed 422 Unprocessable Entity in 159ms (Views: 1.2ms | ActiveRecord: 0.0ms)

These are my settings:

DISCOURSE_SMTP_ADDRESS: my.smtp-server.net
DISCOURSE_SMTP_PORT: 25
DISCOURSE_SMTP_USER_NAME: my@email-address.de
DISCOURSE_SMTP_PASSWORD: mypassword
DISCOURSE_SMTP_ENABLE_START_TLS: false

Where can I retrieve more information?

Thank you in advance,
Benninger

Posts: 3

Participants: 2

Read full topic

Viewing all 60707 articles
Browse latest View live




Latest Images