@watchmanmonitor wrote:

There was a major docker upgrade about 1-2 months ago, and I think it upgraded to postgres 9.5?

I just did a ./launcher rebuild app today and saw that postgres 9.3 is in use...

:/var/discourse# ./launcher rebuild app
Ensuring launcher is up to date
Fetching origin
Launcher is up-to-date
Stopping old container
+ /usr/bin/docker stop -t 10 app
app
cd /pups && git pull && /pups/bin/pups --stdin
Already up-to-date.
I, [2016-08-25T01:35:26.444275 #13]  INFO -- : Loading --stdin
I, [2016-08-25T01:35:26.452811 #13]  INFO -- : > echo cron is now included in base image, remove from templates
I, [2016-08-25T01:35:26.454853 #13]  INFO -- : cron is now included in base image, remove from templates

I, [2016-08-25T01:35:26.455114 #13]  INFO -- : > apt-get remove -y postgresql-9.5 postgresql-client-9.5 postgresql-contrib-9.5
I, [2016-08-25T01:35:29.102101 #13]  INFO -- : Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be REMOVED:
  postgresql-9.5 postgresql-client-9.5 postgresql-contrib-9.5
0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.
After this operation, 26.0 MB disk space will be freed.
(Reading database ... 34207 files and directories currently installed.)
Removing postgresql-contrib-9.5 (9.5.3-1.pgdg16.04+1) ...
update-alternatives: warning: forcing reinstallation of alternative /usr/share/postgresql/9.5/man/man1/postmaster.1.gz because link group postmaster.1.gz is broken
Removing postgresql-9.5 (9.5.3-1.pgdg16.04+1) ...
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of stop.
Removing postgresql-client-9.5 (9.5.3-1.pgdg16.04+1) ...
Processing triggers for postgresql-common (174.pgdg16.04+1) ...
Building PostgreSQL dictionaries from installed myspell/hunspell packages...
Removing obsolete dictionary files:

I, [2016-08-25T01:35:29.103654 #13]  INFO -- : > apt-get update && apt-get install -y postgresql-9.3 postgresql-client-9.3 postgresql-contrib-9.3
dpkg-preconfigure: unable to re-open stdin:
I, [2016-08-25T01:35:40.684581 #13]  INFO -- : Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease

(the logs continue normally, and the site is up & running now.

But I wonder.. did I skip a step in the recent upgrade, and if so, what changes do I need to make (ostensibly in my app.yml)?

Thanks!

Posts: 3

Participants: 2

Read full topic

@IbnAdam wrote:

Hello

I created a new droplet on DigitalOcean using available Discourse one-click app, and then installed Plesk Onyx on it. Now I am unable to access discourse, neither using IP nor using domain name.

I am trying to follow the instructions given here: https://meta.discourse.org/t/running-other-websites-on-the-same-machine-as-discourse/17247 and I have already edited /var/discourse/containers/app.yml as mentioned. But the problem is with the next step. I cannot find /etc/nginx/conf.d/discourse.conf
Also tried to follow this tutorial https://www.digitalocean.com/community/questions/need-help-with-installing-discourse-and-wordpress but once again there is no /etc/nginx/sites-enabled/default

Where else can I look for this config file?

Additional info: The tutorials suggest running discourse as a sub-domain, but I want to have separate domain names for discourse and for websites running under plesk.

Posts: 2

Participants: 2

Read full topic

@The_Greatest_Basket wrote:

First of all, I'm not sure where to post this so move it to correct category if this is wrong.

---

Okay, during the night there was approx. 30 new topics. After reading 7 topics new topics started to disappear.

image.jpg1024x768 95.2 KB

Now you can see that it shows 23 new topics, but it doesn't show them in Suggested Topics.

image.jpg1024x768 46.6 KB

After that I pressed the "23 New" wich brings me to new topics page.
But it shows no new topics.

This can be very annoying as I might miss out on some good feature requests, interesting conversations etc.

Posts: 2

Participants: 2

Read full topic

@sevenmaxis wrote:

I'm trying to understand how Discourse Advertising Plugin works. My case is DoubleClick for Publishers (DFP).
In repo the divId is not actual id generated by Google Publisher Tag, it's composed string from "div-gpt-ad-", placement and optional postNumber, very similar to actual Google Ad Id but it's an id from Google Generate Tags (for example 'div-gpt-ad-1472113540637-0').
In AdPlugin/DFP tab, there's dfp publisher id but there's no id of Google Ad.
How the actual Google Ad Id (let's say 'div-gpt-ad-1472113540637-0') is showing ad on site by Discourse Advertising Plugin?

Posts: 1

Participants: 1

Read full topic

@dorianamouroux wrote:

Hey there,

I'm creating a plugin to be able to authenticate my users through my own OAuth2 provider.
After login, I want to download his profile image and act like he uploaded it.
I took the sso avatar function

  def pull_image(user, avatar_url)
    begin
      tempfile = FileHelper.download(avatar_url, 1.megabyte, "sso-avatar", true)

      ext = FastImage.type(tempfile).to_s
      tempfile.rewind

      upload = Upload.create_for(user.id, tempfile, ("avatar"), File.size(tempfile.path), { origin: avatar_url })
      user.uploaded_avatar_id = upload.id

      if !user.user_avatar.contains_upload?(upload.id)
        user.user_avatar.custom_upload_id = upload.id
      end
    rescue SocketError
     # skip saving, we are not connected to the net
      Rails.logger.warn "Failed to download external avatar: #{avatar_url}, socket error - user id #{ user.id }"
    ensure
      tempfile.close! if tempfile && tempfile.respond_to?(:close!)
    end
  end

I always got this error wrong constant name #<Class:0x007ff12ab518a0> from this line

upload = Upload.create_for(user.id, tempfile, "avatar", File.size(tempfile.path), { origin: avatar_url })

I tried a bit of everything, but I can't figure out why I have this issue

Thank you for your help,
Dorian

Posts: 1

Participants: 1

Read full topic

@Chopper wrote:

I remember few months ago going on a dashboard that show me the task pending, done, in queue etc. Very usefull when you import phpbb forum.

I can' t remember the link, can someone let me know how can i access it again (the url) ?

Posts: 2

Participants: 1

Read full topic

@meglio wrote:

This dropdown box needs some improvement:

image.png750x1334 212 KB

It is a period switcher control found found on the "top" topics list.

We should make it take full screen width.

Posts: 1

Participants: 1

Read full topic

@Overgrow wrote:

Hello, I have added few custom routes and wonder why some bug in my code have introduced this error. When loading this custom section following is shown (javascript tries to GET this file)...

ActionController::RoutingError (No route matches [GET] "/assets/ember-template-compiler.map")
/home/overgrow/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/actionpack-4.2.7/lib/action_dispatch/middleware/debug_exceptions.rb:21:in `call'

I haven't found any information about "ember-template-compiler.map".(Why is it requesting this file in the first place). Can you please suggest what error in my routing could lead to this error?

I'm using this syntax:

this.route('faq_categories', {path: '/sitefaq'} );
this.route('faq_category', { path: '/sitefaq/:id' } );

Thank you

Posts: 1

Participants: 1

Read full topic

@Turko wrote:

i really liked discourse but i think i am done. Because it has always problems. İ didnt know how to work with it but i tried to learn. install guide was to much complex for me ( if u always worked with cpanel, wordpress, ...) but i made it. after i tried to access my site but SMTP setting is horrible. it is a nightmare for newbies. there is no detailed tutorial. (e.g. dkim and spf) then subdomain problem is here.

You need a subdomain for emails. but if u dont want to use subdomain. ( no solution) it is too bad for index (root domain and subdomain same route) if you want to route your subdomain on digitalocean. OMFG dont try it. ( guide is amazing ) if u want to use discourse with other languages. people approved so much wrong translate and u cant fix it.

Discourse will be better but a small group can use it. i was looking for help but i saw the prices... i was thinking if i give 99 dolars to develepors in my country. (for helping) they go crazy and they create a new project.

Posts: 4

Participants: 4

Read full topic

@Nick_Putman wrote:

I am wondering if it is possible for a user to change their password in settings? I would like to disable this possibility as I am using the Wordpress plugin with SSO, and want all changes to be made in the Wordpress user profile.

At the moment I can't find a setting for password change on discourse, but that doesn't mean there isn't one!

Posts: 2

Participants: 2

Read full topic

@Pad_Pors wrote:

I just resend all the waiting invitations accidentally!

I pushed the button instead of pushing the send an invitation button.

is it possible to confirm some of the admin actions like this one, before execution?

Posts: 1

Participants: 1

Read full topic

@shaneoh wrote:

I've just tried to upgrade discourse to the latest version. I've done this on a clone of our live box because we have had a multitude of problems and I don't want to risk breaking the live instance. I used the upgrade process of running these commands:

cd /var/discourse
./launcher bootstrap web_only
./launcher destroy web_only
./launcher start web_only

This didn't work on our live instance by the way - it broke discourse completely and I had to create a new machine from backups to get it working again.

However on the clone instance it appears the upgrade has worked - but when I try to access the URL the page is completely blank. The browser seems to connect because I can even view the certificate for the site, but the page is blank.

Incidentally the reason we are trying this is because our emails recently stopped sending for no apparent reason, and we have not been able to upload images to our forum for about a month now. This used to work, nothing was changed, and suddenly image uploads hang at 100% and nothing happens.

So basically, a lot of problems, but if I could solve the blank page issues then I can at least see if image uploads and emails work on the new version.

Can anyone help? Discourse hasn't worked the way we need it to (and had it working before) for over a month now and it's starting to impact really heavily on us.

Posts: 1

Participants: 1

Read full topic

@meglio wrote:

For some reason, not all topic metadata is aligned to the right, please see an example below:

blob.jpg1301x1130 187 KB

Posts: 1

Participants: 1

Read full topic

@dorianamouroux wrote:

Hi,

I'm using discourse, and I want to back-up my data and reupload it onto another server with Discourse.
The Read-Only mode would be perfect for it, I can do it with no down-time.
The feature doesn't work though, when I click on it and I refresh, the button is back to normal.
User can still write posts as well.

/admin/logs doesn't log any errors

Posts: 4

Participants: 3

Read full topic

@snakeninny wrote:

The site is http://iosre.com. The site remains unreachable after setting up fail2ban. What now? Thanks!

Posts: 23

Participants: 4

Read full topic

@watchmanmonitor wrote:

Continuing the discussion from Discourse Docker Image version 1.3.3, released:

So, I have been using postgres 9.3 since the new docker image came out.. and just replacing templates/postgres.9.3.template.yml with templates/postgres.template.yml doesn't work.
Given a current backup, what's a good way to upgrade the postgres template?

Posts: 3

Participants: 2

Read full topic

@alankeny wrote:

The description of the variable email prefix says: The [label] used in the subject of emails. It will default to 'title' if not set. We've found that setting email prefix replaces the variable site title throughout the email message including the message body.

Our site is called LibraryTalk, but we would like to use [LT] in subject lines to keep them as short as possible. Setting email prefix to LT leads to a Signup message like this:

Subject: [LT] Confirm your new account

Welcome to LT!

Click the following link to confirm and activate your new account:

How can we use an abbreviation in the subject line but use the site title in the body of email messages without editing every email template?

Posts: 2

Participants: 2

Read full topic

@ivanrlio wrote:

Hi there,

I'm trying to backup our staging site with data from our production site. The log after the numerous CREATE INDEX is as follows:

Enabling readonly mode...
[2016-08-25 17:18:08] Pausing sidekiq...
[2016-08-25 17:18:08] Waiting for sidekiq to finish running jobs...
[2016-08-25 17:18:08] Switching schemas... try reloading the site in 5 minutes, if successful, then reboot and restore is complete.
[2016-08-25 17:18:08] EXCEPTION: ERROR:  relation "digest_unsubscribe_keys_pkey" already exists in schema "backup"
CONTEXT:  SQL statement "ALTER TABLE public.unsubscribe_keys SET SCHEMA backup;"
PL/pgSQL function inline_code_block line 11 at EXECUTE

[2016-08-25 17:18:08] /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.1/lib/patches/db/pg.rb:50:in `exec'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.1/lib/patches/db/pg.rb:50:in `exec'
/var/www/discourse/lib/freedom_patches/active_record_base.rb:7:in `exec_sql'
/var/www/discourse/lib/backup_restore/restorer.rb:252:in `switch_schema!'
/var/www/discourse/lib/backup_restore/restorer.rb:49:in `run'
/var/www/discourse/lib/backup_restore/backup_restore.rb:161:in `block in start!'
/var/www/discourse/lib/backup_restore/backup_restore.rb:158:in `fork'
/var/www/discourse/lib/backup_restore/backup_restore.rb:158:in `start!'
/var/www/discourse/lib/backup_restore/backup_restore.rb:17:in `restore!'
/var/www/discourse/app/controllers/admin/backups_controller.rb:80:in `restore'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/abstract_controller/base.rb:198:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_controller/metal/rendering.rb:10:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:117:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.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.3.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:505:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:92:in `__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:778:in `_run_process_action_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:81:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/abstract_controller/callbacks.rb:19:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_controller/metal/rescue.rb:29:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.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.3.0/gems/activesupport-4.2.6/lib/active_support/notifications.rb:164:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.6/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.6/lib/active_support/notifications.rb:164:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.6/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/abstract_controller/base.rb:137:in `process'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.6/lib/action_view/rendering.rb:30:in `process'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.1/lib/mini_profiler/profiling_methods.rb:76:in `block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_controller/metal.rb:196:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_controller/metal.rb:237:in `block in action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_dispatch/routing/route_set.rb:74:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_dispatch/routing/route_set.rb:43:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_dispatch/routing/mapper.rb:49:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_dispatch/journey/router.rb:43:in `block in serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_dispatch/journey/router.rb:30:in `each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_dispatch/journey/router.rb:30:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_dispatch/routing/route_set.rb:817:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/builder.rb:63:in `call'
/var/www/discourse/config/initializers/008-rack-cors.rb:15:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/conditionalget.rb:38:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/head.rb:13:in `call'
/var/www/discourse/lib/middleware/anonymous_cache.rb:129:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/flash.rb:260:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/session/abstract/id.rb:225:in `context'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/session/abstract/id.rb:220:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/cookies.rb:560:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.6/lib/active_record/query_cache.rb:36:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.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.3.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:88:in `__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:778:in `_run_call_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:81:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/remote_ip.rb:78:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/logster-1.2.4/lib/logster/middleware/reporter.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.6/lib/rails/rack/logger.rb:38:in `call_app'
/var/www/discourse/vendor/bundle/ruby/2.3.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.3.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/request_id.rb:21:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/methodoverride.rb:22:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/runtime.rb:18:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/sendfile.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.1/lib/mini_profiler/profiler.rb:171:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.1/lib/message_bus/rack/middleware.rb:62:in `call'
/var/www/discourse/lib/middleware/request_tracker.rb:73:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.6/lib/rails/engine.rb:518:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.6/lib/rails/application.rb:165:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.6/lib/rails/railtie.rb:194:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.6/lib/rails/railtie.rb:194:in `method_missing'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/urlmap.rb:66:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/urlmap.rb:50:in `each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/urlmap.rb:50:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.1.0/lib/unicorn/http_server.rb:562:in `process_client'
/var/www/discourse/lib/scheduler/defer.rb:85:in `process_client'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.1.0/lib/unicorn/http_server.rb:658:in `worker_loop'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.1.0/lib/unicorn/http_server.rb:508:in `spawn_missing_workers'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.1.0/lib/unicorn/http_server.rb:132:in `start'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.1.0/bin/unicorn:126:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.3.0/bin/unicorn:23:in `load'
/var/www/discourse/vendor/bundle/ruby/2.3.0/bin/unicorn:23:in `<main>'
[2016-08-25 17:18:08] Trying to rollback...
[2016-08-25 17:18:08] Cleaning stuff up...
[2016-08-25 17:18:08] Removing tmp '/var/www/discourse/tmp/restores/default/2016-08-25-171744' directory...
[2016-08-25 17:18:08] Unpausing sidekiq...
[2016-08-25 17:18:08] Disabling readonly mode...
[2016-08-25 17:18:08] Marking restore as finished...
[2016-08-25 17:18:08] Finished!

I'm not sure what the digest_unsubscribe_keys_pkey are, but I believe this is the start of the error.

Any help would be greatly appreciated.

Thanks!

Posts: 4

Participants: 3

Read full topic

@gerhard wrote:

The fallback to English doesn't work for pluralized strings when the language uses different pluralization rules than English.

Posts: 1

Participants: 1

Read full topic

@kuyashi wrote:

How to use CloudFlare's platform to force all traffic over HTTPS connection using page rules.
This is an up to date and user-friendly (fool-proof) way that I use each time and it works perfectly.

Sign up to CloudFlare here - they offer SSL/HTTPS on their Free plan, so that will be just fine for us.

Add your site here - the system will scan for DNS records, make sure all are correct and add any records not picked automatically by the scan i.e. MX records.

You will the have to add the CloudFlare nameservers to your domain. This can be done with whoever your purchased your domain with on their control panel - differs for each provider - some examples:
-GoDaddy: here.
-Namecheap: here.
-Bluehost: here.

Once your nameservers have been successfully edited (you can check this by opening a terminal and issuing the command:
whois yourdomain.com) towards the bottom of the output you should see CloudFlare's nameservers:

Name Server: LARA.NS.CLOUDFLARE.COM
Name Server: GABE.NS.CLOUDFLARE.COM

Now we can head back to our CloudFlare control panel for your new site:

Screen Shot 2016-08-25 at 20.02.41.png1256x649 46.8 KB

Click on the page rules section from the icon menu. Click on create page rule and fill in as follows:

Screen Shot 2016-08-25 at 20.06.41.png795x611 48.7 KB

Enter your domain i the format as in image above: http://*yourdomain.com/* this will force all sub-domains (the * before the domain) and sub-directories (the * after the domain) to use HTTPS.

Click on "add setting" and choose "Always use HTTPS" from the drop down menu. For "Order" yo can leave as "First".

Click on "Save and Deploy".

The setting may take up to 15 minutes to take effect, but then all your traffic should re-direct to https://yourdomain.com .

NOTE:
In order to maintain full HTTPS (green padlock) you will need to go to Discourse settings (/admin/site_settings/category/required) and search for all settings containing http://..../.... and change the links to https://.../.... .

You can check SSL status at: https://www.ssllabs.com/ssltest/ :

Screen Shot 2016-08-25 at 20.21.40.png1268x726 85.4 KB

NOTE:
As noted by @mpalmer below:

... In order for the connection between Cloudflare and your origin to be similarly secure as the connection between the browser and Cloudflare, you need to setup SSL on the origin server, too.

For setting up SSL on your server:

Posts: 5

Participants: 2

Read full topic