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

Bookmark issue when access to topic is lost (PMs)

$
0
0

@jomaxro wrote:

Earlier I bookmarked a topic that was later moved to PM, which I was not a part of. The post still appears on my bookmark list, but I am unable to see the full post, nor can I remove the bookmark. Speaking with @sam, he confirmed that the same issue would occur if I bookmarked something in a PM but subsequently lost access.

Relevant js errors when clicking remove bookmark:


Posts: 1

Participants: 1

Read full topic


Links in topic summary area do not wrap

UpCloud.com experiences

$
0
0

@ljpp wrote:

Changed to yet another VPS provider yesterday, so here are my initial experiences regarding our new host UpCloud.com.

Disclaimer: We struck a deal with UpCloud exchanging advertising on our community for hosting credits. Even with this affiliation, I intend to share my un-biased view on their operation. Good or bad, I will report.

UpCloud has four datacenters: Chicago, London, Helsinki and Frankfurt. The company itself is based in Finland. They are relatively new as they started in 2012. They are somewhat popular in the Nordic IT-scene and have received favorable reviews. I also have some friends with Kontena.io (world class container gurus), and they spoke favorably about UpCloud.

In terms of pricing they position themselves exactly against the market leader Digital Ocean (another great option). What caught my attention is their marketing, where they also benchmark their operation against DO, claiming significantly better performance. Their marketing promise includes faster CPU cores and significantly faster disk I/O than the similar Digital Ocean VPS. I have not benchmarked their servers.

The UpCloud administration dashboard is straight forward and servers spin up in 45 seconds or so. I am currently on their 80$ plan (Frankfurt), featuring 6 cores, 8GB RAM and 200GB storage. My initial expression is that our site (Tappara.co) is now very snappy and responsive - better than ever before, but of course this is a rather beefy VPS I am using (I have also used DO's 80$ plan in the past).

I have just started using them, so too early to say anything about the reliability or long term performance. At least based on the specs, UpCloud should be a good fit for Discourse. If anyone here has used them, I'd be interested in hearing any comments or feedback how they perform.

Posts: 1

Participants: 1

Read full topic

Can not Delete all Posts

$
0
0

@Imperator wrote:

Hi,

i need to delete a Useer completly, like the user never exist.

When i will delete the Posts i get this...

best regards,
Theo

Posts: 1

Participants: 1

Read full topic

Share badges on social media

$
0
0

@foloex wrote:

Hello world,

I'm trying to enhance my community activeness. In order to do so, I'd like my members to be able to brag about obtaining a badge on social media. It would reinforce the gamification aspect of the forum and lead the community into wanting to obtain badges, thus increasing the overall activity.

Is there a way to share a badge on social media (mainly facebook and twitter) ? If not, what kind of development would it take to do so ? I'm willing to make a plugin if it's what it takes.

Best regards,

Rémi

Posts: 5

Participants: 2

Read full topic

Onebox whitelist missing

$
0
0

@rpasichnyk wrote:

I just installed discourse on VirtualBox to try out oneboxing. I was going to whitelist my oembed site but could not find whitelist in the settings. How one does whitelisting nowadays?

Posts: 3

Participants: 2

Read full topic

Embedding Discourse сomments with GitBook

$
0
0

@lev.kavelin wrote:

Good day!

It is necessary to integrate the Discourse comments with GitBook. For each new page\post should be created theme in the Discourse. In essence this is the same as the plug comments to a blog that is described here - https://meta.discourse.org/t/embedding-discourse-comments-via-javascript/31963/1

But I'm not so good at JS to do it now on their own.

In the catalog Gitbook there are two plug-ins for integration with platform comments discourse. But both the plugin does not work.
https://plugins.gitbook.com/plugin/discourse
https://plugins.gitbook.com/plugin/discourse-external-integration

Can anyone help with this? I would be grateful for any advice.

Posts: 1

Participants: 1

Read full topic

SSO between discourse sites?

$
0
0

@Luke wrote:

Hi,

I was wondering..

Is it possible to "share" user accounts between forums?

If it's not OOTB functionality, is there any way you would suggest doing this?

Thanks.

Posts: 1

Participants: 1

Read full topic


Create docker image from customized discourse git repo which support ssh protocol access only

$
0
0

@irshad_discource wrote:

Hi,
I have to build discourse from customized git code base which support ssh based access only. I have modified the app.yml as per this post. What changes should be there to pass my repo's ssh authentication. I tried the below thing which did'nt work. I just tried to copy ssh key to container.

hooks:
  after_code:
    - exec:
        cd: $home/plugins
        cmd:
          - git clone https://github.com/discourse/docker_manager.git
    - exec:
        cd: $home
        cmd:
         # changes start here
          - cp ~/.ssh/id_rsa container:~/.ssh/id_rsa
          - git remote remove origin
          - git config --remove-section branch.master
          - git config --remove-section branch.tests-passed
          - git remote add origin git@codebase.xyz.com:userName/discourse.git
          - git fetch
          - git remote set-branches --add origin anonymous-locale
          - git branch -u origin/anonymous-locale
          - git reset --hard origin/anonymous-locale

Posts: 1

Participants: 1

Read full topic

Confused about setting up reply by email

$
0
0

@knittingtoday wrote:

I'm reading not to use gmail, but google apps for domain are okay??? . . . but I'm lost on how to get started. Can someone point me to the instructions (step-by-step preferred :wink:) . . . Knittingtoday.com is hosted through google for work or is it called gsuite now?

Posts: 2

Participants: 2

Read full topic

Lattice - A bidirectional navigation plugin for Discourse

$
0
0

@gdpelican wrote:

Hey folks,

I've been plugging away at a fun project for bi-directional navigation with The Food Assembly over the past couple weeks, original idea is outlined here. And now it's an (un-user-tested) reality! The idea is that you can construct a table to view a large number of topics in a tabular format. Check out the README for more info on how to install and use it.

As ever, I'm eager for feedback, so let me know what's not great.

Enjoy!

Posts: 1

Participants: 1

Read full topic

Login not possible (no SSO, no LDAP, etc.)

$
0
0

@pmayer wrote:

Hi guys,

I don't know if this is a bug. I'm hosting a dockerized discourse install for our local makerspace with the official docker discourse image.

Since I'm web developer I'm fluent in PHP/JS/MySQL/etc. and generel server administration. But Ruby and Rails are totally new to me, also I have to admit this is my first dockerized application

I've never tried to "relogin" to the site as all worked perfectly. Today I've just hit logout, cause some of the users told me about some login problems, and that they can not log in anymore. The site is behind a nginx-ssl proxy. But even on the local network (no https) I can not log in anymore.

This is what happens:

  • After Login via the modal, the data is posted to /login which redirects me to / which then redirects me back to /login
  • From /login I get the desired (?) cookie: Set-Cookie:"_forum_session=[xxx]; path=/; HttpOnly" including the redirect to /.
  • From / I getthe cookie Set-Cookie:"destination_url=http%3A%2F%2F<our-domain>%2F; path=/
    _forum_session=[xxx]; path=/; HttpOnly"
    including the header-location to/login

I've already rebuilt the app with ./launcher rebuild app and can't see anything more than the DB-saving in my log:

40:M 25 Oct 15:39:55.051 * 10 changes in 300 seconds. Saving...
40:M 25 Oct 15:39:55.054 * Background saving started by pid 29231
29231:C 25 Oct 15:39:55.141 * DB saved on disk
29231:C 25 Oct 15:39:55.141 * RDB: 8 MB of memory used by copy-on-write
40:M 25 Oct 15:39:55.160 * Background saving terminated with success

This is the start after the rebuild:

run-parts: executing /etc/runit/1.d/copy-env
run-parts: executing /etc/runit/1.d/enable-brotli
Started runsvdir, PID is 28
sh: echo: I/O error
ok: run: redis: (pid 40) 0s
ok: run: postgres: (pid 39) 0s
                _._
           _.-``__ ''-._
      _.-``    `.  `_.  ''-._           Redis 3.0.6 (00000000/0) 64 bit
  .-`` .-```.  ```\/    _.,_ ''-._
 (    '      ,       .-`  | `,    )     Running in standalone mode
 |`-._`-...-` __...-.``-._|'` _.-'|     Port: 6379
 |    `-._   `._    /     _.-'    |     PID: 40
  `-._    `-._  `-./  _.-'    _.-'
 |`-._`-._    `-.__.-'    _.-'_.-'|
 |    `-._`-._        _.-'_.-'    |           http://redis.io
  `-._    `-._`-.__.-'_.-'    _.-'
 |`-._`-._    `-.__.-'    _.-'_.-'|
 |    `-._`-._        _.-'_.-'    |
  `-._    `-._`-.__.-'_.-'    _.-'
      `-._    `-.__.-'    _.-'
          `-._        _.-'
              `-.__.-'

40:M 25 Oct 14:14:38.516 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
40:M 25 Oct 14:14:38.517 # Server started, Redis version 3.0.6
40:M 25 Oct 14:14:38.517 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
40:M 25 Oct 14:14:38.517 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
40:M 25 Oct 14:14:38.547 * DB loaded from disk: 0.030 seconds
40:M 25 Oct 14:14:38.547 * The server is now ready to accept connections on port 6379
rsyslogd: command 'KLogPermitNonKernelFacility' is currently not permitted - did you already set it via a RainerScript command (v6+ config)? [v8.16.0 try http://www.rsyslog.com/e/2222 ]
rsyslogd: imklog: cannot open kernel log (/proc/kmsg): Operation not permitted.
rsyslogd: activation of module imklog failed [v8.16.0 try http://www.rsyslog.com/e/2145 ]
rsyslogd: Could not open output pipe '/dev/xconsole':: No such file or directory [v8.16.0 try http://www.rsyslog.com/e/2039 ]
2016-10-25 14:14:39 UTC [55-1] LOG:  database system was shut down at 2016-10-25 14:14:25 UTC
2016-10-25 14:14:39 UTC [55-2] LOG:  MultiXact member wraparound protections are now enabled
2016-10-25 14:14:39 UTC [39-1] LOG:  database system is ready to accept connections
2016-10-25 14:14:39 UTC [59-1] LOG:  autovacuum launcher started
supervisor pid: 38 unicorn pid: 61
2016-10-25 14:14:52 UTC [86-1] discourse@discourse LOG:  duration: 117.795 ms  parse <unnamed>:               SELECT t.oid, t.typname, t.typelem, t.typdelim, t.typinput, r.rngsubtype, t.typtype, t.typbasetype
                  FROM pg_type as t
                  LEFT JOIN pg_range as r ON oid = rngtypid
                  WHERE
                    t.typname IN ('int2', 'int4', 'int8', 'oid', 'float4', 'float8', 'text', 'varchar', 'char', 'name', 'bpchar', 'bool', 'bit', 'varbit', 'timestamptz', 'date', 'time', 'money', 'bytea', 'point', 'hstore', 'json', 'jsonb', 'cidr', 'inet', 'uuid', 'xml', 'tsvector', 'macaddr', 'citext', 'ltree', 'interval', 'path', 'line', 'polygon', 'circle', 'lseg', 'box', 'timestamp', 'numeric')
                    OR t.typtype IN ('r', 'e', 'd')
                    OR t.typinput = 'array_in(cstring,oid,integer)'::regprocedure
                    OR t.typelem != 0

Maybe someone from you can give me a hint, especially from a non ruby point of view.

Cheers,
Patrik

Posts: 4

Participants: 2

Read full topic

Error when trying to get to the /users URL

$
0
0

@Nicholas_Tolstoshev wrote:

I'm trying to go to the user leaderboard described here:


on my Discourse site.

But when I do I get the following error message:
:frowning:
Access Denied
while trying to load /directory_items?period=weekly&order=likes_received
Something went wrong.

Any ideas on where to start troubleshooting?

Posts: 6

Participants: 3

Read full topic

Email polling problem

$
0
0

@knittingtoday wrote:

I set up the pop3 email polling and now all of my gmail emails have been sent a reply and they have been added to the forum. What do I do to get them off and how do I troubleshoot my set up to see why this happened?

Posts: 2

Participants: 2

Read full topic

It is impossible to create a backup


Site settings search broken

$
0
0

@pfaffman wrote:

I'm running Discourse 1.7.0.beta6. All searches of site settings return no results. I don't think this is related to this or this.

I recently changed the hostname. Could that have broken it? (It seems like it has worked since then, but I could be wrong.)

Is there some rake task that rebuilds that search index or something?

Posts: 8

Participants: 4

Read full topic

Post Edit History view icons missing

Read Only API user

$
0
0

@ross wrote:

Hi there,

I'm trying to create an API integration from a website that will show some overall Discourse stats (from the /about page), and some stats for some specific categories.

I'm just wondering how best to do this with users. Is there any way I can create a site-wide, "read-only" user for pulling this kind of information out of Discourse? What would you advise?

Thanks

Ross

Posts: 2

Participants: 2

Read full topic

Adding Tags in composer is not fully internationalize?

$
0
0

@enigmaty wrote:

I have tried to translate the section where we can add tags to a new topic but without any lock. I have tested all the languages. the all fall to English. Is there any trick that I can use to translate this part.

It shows "Searching..." normally, and "Loading failed" when there is no network.

Posts: 1

Participants: 1

Read full topic

Undefined method `email' for nil:NilClass

$
0
0

@fefrei wrote:

It looks like some bounce emails aren't being processed for me – I have 14 of these errors in my logs:

NoMethodError (undefined method `email' for nil:NilClass)
/var/www/discourse/app/controllers/webhooks_controller.rb:136:in `process_bounce'

Here's the backtrace:

/var/www/discourse/app/controllers/webhooks_controller.rb:136:in `process_bounce'
/var/www/discourse/app/controllers/webhooks_controller.rb:48:in `block in sendgrid'
/var/www/discourse/app/controllers/webhooks_controller.rb:42:in `each'
/var/www/discourse/app/controllers/webhooks_controller.rb:42:in `sendgrid'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/abstract_controller/base.rb:198:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/rendering.rb:10:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:88:in `__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:778:in `_run_process_action_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:81:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/abstract_controller/callbacks.rb:19:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/rescue.rb:29:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/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.7.1/lib/active_support/notifications.rb:164:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/notifications.rb:164:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/abstract_controller/base.rb:137:in `process'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7.1/lib/action_view/rendering.rb:30:in `process'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal.rb:196:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_controller/metal.rb:237:in `block in action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/routing/route_set.rb:74:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/routing/route_set.rb:43:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/journey/router.rb:43:in `block in serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/journey/router.rb:30:in `each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/journey/router.rb:30:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/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/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.7.1/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/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.7.1/lib/action_dispatch/middleware/cookies.rb:560:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/query_cache.rb:36:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/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.7.1/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:88:in `__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:778:in `_run_call_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/callbacks.rb:81:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/remote_ip.rb:78:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7.1/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/logster-1.2.5/lib/logster/middleware/reporter.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/rack/logger.rb:38:in `call_app'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/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.7.1/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/message_bus-2.0.2/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.7.1/lib/rails/engine.rb:518:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/application.rb:165:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/lib/rails/railtie.rb:194:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7.1/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>'

And the (censored) environment:

process_id	[232, 244]
application_version	e6047f2b65334c3e7e2dfb96494c942e1ec24b64
REQUEST_URI	/webhooks/sendgrid
REQUEST_METHOD	POST
HTTP_USER_AGENT	SendGrid Event API
HTTP_REFERER	https://my.domain/webhooks/sendgrid
HTTP_X_FORWARDED_FOR	[167.89.125.230, unix:, 167.89.125.242, unix:, 167.89.125.238, unix:, 167.89.125.231, unix:, 167.89.125.250, unix:, 167.89.125.222, unix:, 167.89.125.253, unix:, 167.89.125.249, unix:, 167.89.125.244, unix:, 167.89.125.240, unix:]
HTTP_X_REAL_IP	unix:

Is this a bug? Can I do anyhing about it?

Posts: 3

Participants: 2

Read full topic

Viewing all 60721 articles
Browse latest View live




Latest Images