@jesselperry wrote:

I would like to better market how many users are on my Discourse installation. Has anyone implemented something that appears at the top of the topic list that shows how many registered users there are?

Posts: 4

Participants: 3

Read full topic

@axfelix wrote:

After a recent upgrade, it seems like users are no-longer auto-subscribed to topics they post in. The config still seems like it should be producing this behaviour (and hasn’t changed); is this a known issue with 1.9.0 beta 8?

Posts: 2

Participants: 2

Read full topic

@haikuos wrote:

Running a discuss instance that has been upgraded quite a few times.
Users are reporting an issue around password resets.

When password resets are clicked, they reach a 404 “Oops…” page… if you provide an “incorrect” password reset id, discuss does show an "Sorry, that password change link is too old. " page.

Any ideas on what could be wrong? It feels like the password change page is redirecting to some incorrect location internally. Logs don’t show much useful info.

Posts: 1

Participants: 1

Read full topic

@barryvan wrote:

When you partially enter an emoji’s name which includes a fairly common string – for example, :cross – there are often more results than can be displayed in the picklist. It’d be great if clicking “More” opened the picker with the text you’ve entered set as the search term. This way, you can easily find the one you’re chasing, even if you can only remember part of its name.

In other words (or rather, in pictures):

should open the picker pre-searched:

so that I can get to the green cross box.

(Aside: why are the emojis in the picklist in a different order from the picker itself?)

Posts: 2

Participants: 2

Read full topic

@burningman wrote:

What is the difference between discourse page count view vs adsense count page view.
I am asking this because yesterday I noticed a huge difference between both of these.
Discourse page view count shows 1.4k page view but on adsense it shows only 200 page view. Too much confused in this.
Can any one explain here a little.

Posts: 2

Participants: 2

Read full topic

@Brock_Busby wrote:

All of our servers, site and Discourse community (discussions.ftw.in) sit behind Cloudflare.

Can we set at the Discourse server level to only allow Cloudflare IPs and deny all other IP traffic?

We’ve been under a DDoS layer 7 attack and learned our main site IP was exposed.
To fix this, we updated our .htaccess on our main site server to only allow traffic from Cloudflare IPs and deny all other traffic. This does not let our origin server IP get exposed.

We are not exactly sure how to do the same above for our Discourse server at the server level. In my searches, I’ve seen cloudflare.template.yml mentioned and that it’s set to make sure we are seeing our user IPs, but I’m not sure.

Thanks in advance!

Posts: 2

Participants: 2

Read full topic

@yedward wrote:

Install discourse in docker by this guide ：GitHub - discourse/discourse_docker: A Docker image for Discourse

After a short time running, the containner often down unexpectedly。

By run docker logs，that shows：

run-parts: executing /etc/runit/1.d/00-ensure-links
run-parts: executing /etc/runit/1.d/00-fix-var-logs
run-parts: executing /etc/runit/1.d/anacron
run-parts: executing /etc/runit/1.d/cleanup-pids
Cleaning stale PID files
run-parts: executing /etc/runit/1.d/copy-env
run-parts: executing /etc/runit/1.d/enable-brotli
Started runsvdir, PID is 36
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 ]
supervisor pid: 43 unicorn pid: 57
Shutting Down
run-parts: executing /etc/runit/3.d/01-nginx
ok: down: nginx: 0s, normally up
run-parts: executing /etc/runit/3.d/02-unicorn
exiting
ok: down: unicorn: 1s, normally up
When using programs that use GNU Parallel to process data for publication please cite:

  O. Tange (2011): GNU Parallel - The Command-Line Power Tool,
  ;login: The USENIX Magazine, February 2011:42-47.

This helps funding further development; and it won't cost you a cent.
Or you can get GNU Parallel without this requirement by paying 10000 EUR.

To silence this citation notice run 'parallel --bibtex' once or use '--no-notice'.

ok: down: nginx: 1s, normally up
ok: down: unicorn: 1s, normally up
ok: down: cron: 0s, normally up
ok: down: rsyslog: 0s, normally up
run-parts: executing /etc/runit/1.d/00-ensure-links
run-parts: executing /etc/runit/1.d/00-fix-var-logs
run-parts: executing /etc/runit/1.d/anacron
run-parts: executing /etc/runit/1.d/cleanup-pids
Cleaning stale PID files
run-parts: executing /etc/runit/1.d/copy-env
run-parts: executing /etc/runit/1.d/enable-brotli
Started runsvdir, PID is 31
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 ]
supervisor pid: 37 unicorn pid: 52
config/unicorn_launcher: line 44: kill: (52) - No such process
config/unicorn_launcher: line 10: kill: (52) - No such process
exiting
supervisor pid: 75 unicorn pid: 78
config/unicorn_launcher: line 44: kill: (78) - No such process
config/unicorn_launcher: line 10: kill: (78) - No such process
exiting
supervisor pid: 101 unicorn pid: 104
config/unicorn_launcher: line 44: kill: (104) - No such process
config/unicorn_launcher: line 10: kill: (104) - No such process
exiting
supervisor pid: 127 unicorn pid: 130
config/unicorn_launcher: line 44: kill: (130) - No such process
config/unicorn_launcher: line 10: kill: (130) - No such process
exiting
supervisor pid: 153 unicorn pid: 156
config/unicorn_launcher: line 44: kill: (156) - No such process
config/unicorn_launcher: line 10: kill: (156) - No such process
exiting
supervisor pid: 179 unicorn pid: 182
config/unicorn_launcher: line 44: kill: (182) - No such process
config/unicorn_launcher: line 10: kill: (182) - No such process
exiting
supervisor pid: 205 unicorn pid: 208
config/unicorn_launcher: line 44: kill: (208) - No such process
config/unicorn_launcher: line 10: kill: (208) - No such process
exiting
supervisor pid: 231 unicorn pid: 234
config/unicorn_launcher: line 44: kill: (234) - No such process
config/unicorn_launcher: line 10: kill: (234) - No such process
exiting
supervisor pid: 257 unicorn pid: 260
config/unicorn_launcher: line 44: kill: (260) - No such process
config/unicorn_launcher: line 10: kill: (260) - No such process
exiting
supervisor pid: 283 unicorn pid: 286
config/unicorn_launcher: line 44: kill: (286) - No such process
config/unicorn_launcher: line 10: kill: (286) - No such process
exiting
supervisor pid: 309 unicorn pid: 312
Shutting Down
run-parts: executing /etc/runit/3.d/01-nginx
ok: down: nginx: 0s, normally up
run-parts: executing /etc/runit/3.d/02-unicorn
config/unicorn_launcher: line 10: kill: (312) - No such process
exiting
ok: down: unicorn: 0s, normally up
When using programs that use GNU Parallel to process data for publication please cite:

  O. Tange (2011): GNU Parallel - The Command-Line Power Tool,
  ;login: The USENIX Magazine, February 2011:42-47.

This helps funding further development; and it won't cost you a cent.
Or you can get GNU Parallel without this requirement by paying 10000 EUR.

To silence this citation notice run 'parallel --bibtex' once or use '--no-notice'.

ok: down: nginx: 1s, normally up
ok: down: unicorn: 1s, normally up
ok: down: cron: 0s, normally up
ok: down: rsyslog: 0s, normally up
run-parts: executing /etc/runit/1.d/00-ensure-links
run-parts: executing /etc/runit/1.d/00-fix-var-logs
run-parts: executing /etc/runit/1.d/anacron
run-parts: executing /etc/runit/1.d/cleanup-pids
Cleaning stale PID files
run-parts: executing /etc/runit/1.d/copy-env
run-parts: executing /etc/runit/1.d/enable-brotli
Started runsvdir, PID is 31
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 ]
supervisor pid: 36 unicorn pid: 52
Reopening logs

My host machine is Centos 7，4U 16G，docker version is 17.06.2-ce。

Posts: 2

Participants: 2

Read full topic

@Tumi wrote:

Ok Css i know how to edit. But should i need to know how to edt template. Shall i did it btw.

Pls tell me that one. I want to move icon of category ^^^ like on this picture. " float:right dont work as i want"

Bez nazwy1.png1366x768 59.4 KB

Posts: 4

Participants: 3

Read full topic

@Sujan wrote:

In the community I am moderating (support community for a Javascript framework) we have the problem that users are really bad at creating titles:

• Although we have categories for different library versions and they use them, the also tend to include the version numbers in the title like “How do I do x with software v3?” which adds a lot of unnecessary noise - especially as the library version is irrelevant in 99% of the cases.
• Many don’t actually describe their problem, but write something like “Problem, how to fix?” or “Build doesn’t work” an leave all the interesting stuff to the post body (or just leave it out completely - but that is a different problem)

If we just accept these topics as they are, new users (95% of users are first time users) see these topics and create titles that are similar: They all include irrelevant version numbers or just state that they have a problem. That is why we, the moderators, try to “police” the topic titles and edit them.

Right now my workflow for this is opening the list of new topics, opening all the ones with “bad” titles in new tabs and go through them one by one. This takes a lot of clicks and tabs and also marks these topics as “read” by me, which I didn’t actually do.

I imagine a topic view where I can directly edit topic titles with few clicks and maybe even read a preview of the post body without opening the actual thread. Does something like this exist?

Posts: 1

Participants: 1

Read full topic

@hnaseri wrote:

Recently, when I share streamable videos as onebox, They don’t show at all. while the link is ok.

https://try.discourse.org/t/testing-streamable-videos/825

https://streamable.com/iqph4

Any idea?

Posts: 2

Participants: 2

Read full topic

@LeoMcA wrote:

We’ve been having some upload issues on our Discourse instance recently: most of the time, if you upload an image it will never finish. Occasionally it will, but only after a lengthy wait.

After doing some investigation, it seems to be down to a problem with MessageBus. If I subscribe to the /uploads/composer channel on the server, I’ll get a message containing a working url almost as soon as I’ve clicked upload. The message will usually never get to the client.

This doesn’t just affect uploads, but seemingly all MessageBus channels. Post edits won’t appear before a refresh, and if I subscribe to a test channel I create on the client and push messages to it from the server they won’t arrive.

The one scenario where messages will arrive (more often than not) is if I have two discourse tabs open - when I switch to the second tab, the message will arrive in the first tab.

This is definitely a misconfiguration we have on discourse.mozilla.org - as uploads are working fine here - but I’m not sure what it could be. We only put static assets behind a CDN, and dynamic content is behind ELB and HAProxy - but we’ve changed none of that since we’ve started seeing issues.

Anyone got an idea what could be going on here? I’m pretty stumped…

Posts: 4

Participants: 3

Read full topic

@nixie wrote:

Some images are not getting posted in their full size in my discourse site.

Here is an example of one such image:

IMG_3497.JPG1237x3857 636 KB

It is getting posted perfectly here.
[EDIT: It is NOT getting posted perfectly here either. In edit window it was showing correctly. But once the post became LIVE, it is no more showing up correctly]

Here is how the same image is showing up in my site:

image.jpg791x615 117 KB

Image settings in my site:

image.png817x285 19.3 KB

Posts: 1

Participants: 1

Read full topic

@Falco wrote:

We can try switching the topic share icon action to the web share intent on supported plataforms ( Chrome android for now)

Posts: 1

Participants: 1

Read full topic

@digitaldan wrote:

HI, I’m a member of the openHAB team, we are one of the largest open source home automation projects. We are also affiliated with the Eclipse Smart Home project which we contribute to, and use as the base of our own project (think of us a the reference implementation) .

Our community forums have been down for the last 24 hours and we are struggling to get them back online.

The Issue

Unicorn processes seem to be killed after 30 seconds, we see this in shared/standalone/log/rails/unicorn.stderr.log

E, [2017-09-21T14:29:18.466973 #261] ERROR -- : worker=0 PID:13791 timeout (43s > 30s), killing
E, [2017-09-21T14:29:18.467612 #261] ERROR -- : worker=2 PID:13823 timeout (36s > 30s), killing
E, [2017-09-21T14:29:18.467874 #261] ERROR -- : worker=1 PID:14395 timeout (33s > 30s), killing
E, [2017-09-21T14:29:18.547036 #261] ERROR -- : worker=0 PID:13791 timeout (43s > 30s), killing
E, [2017-09-21T14:29:18.547289 #261] ERROR -- : worker=1 PID:14395 timeout (33s > 30s), killing

Once this starts happening, we have to restart the container or this happens indefinitely. Most times it requires more then one restart to be functional again.

We doubled the size of our hardware 2 days ago, and now can not keep the site up for more then a few mins,

What we have done so far
For the last couple weeks this has been happening more frequently, and we have needed to restart it to bring it back online.

We were using a Digital Ocean 2 cpu / 4gb instance and made the decision to double that hoping that more mem and cpu will help handle the load.

After upgrading to 4 cpu / 8gb memory and rebuilding our container with an appropriate app.yml our problem seems to be worse now, not better. We still have the exact same errors, but now our site can’t seem to be up for more then a few minutes at a time. Our current settings look like the following

db_shared_buffers: "2GB"
db_work_mem: "40MB"
UNICORN_WORKERS: 4

I have also tried increasing the shared buffers, workers and a combination of both together, but nothing has seemed to help. Restarting no longer help as well.

Git log shows we are running revision ee9a607677106603ace3e90f3c5bd9ca84a11ef7 which was commited on Fri Sep 15 08:27:27 2017 +0800

Next Steps
We are currently out of ideas after doubling the hardware. I’m not sure why the unicorn processes are hanging and then being killed under load, and why doubling the hardware has made things worse, not better.

any help by the community would be very, very appreciated.

Thanks
Dan-

Posts: 1

Participants: 1

Read full topic

@tritum wrote:

Hi there,

I have a huge problem. We are running an interal forum for our employees. A couple of weeks ago, we migrated to Discourse and imported all the users, groups, categories, threads and comments. Some categories are only accessible for concrete user groups. However, users without being in such a group are able to access those protected categories via the “Latest” view. They can read the topic and access the whole thread and download attachments.

Is this the way to go? What am I doing wrong? Even when only granting access to such a category for admins only, the threads can be seen and accessed.

I appreciate any help.

Thx, Björn

Posts: 2

Participants: 2

Read full topic

@jack2 wrote:

When using the API to create a topic that contains a new tag, if the user identified by api_username cannot create tags, the query creates the topic but silently fails to add the tag.

Posts: 1

Participants: 1

Read full topic

@jack2 wrote:

Right now, in order to create a tag with the API, I create a temporary topic with the new tag, then delete the temporary topic. Is there a cleaner way?

Posts: 6

Participants: 3

Read full topic

@jordan1909 wrote:

We have standardized on a specific naming convention for staff on our forum. Is it possible to restrict a specific substring in a username to prevent other users from using it? It is a very specific string that could not be used inadvertently.

Posts: 4

Participants: 2

Read full topic

@Fsantiago wrote:

hello again. using discourse running via docker on centos 7.4. i use csf via webmin as my firewall frontend.

so i’ve noticed that allowing csf to auto-update itself forces a csf restart each update which then breaks the docker’s networking until i restart docker, to have its own iptables rules re-applied. which ultimately causes issues with my instance of discourse.

i’ve read about using the built in csf function csfpre.sh to define rules to be automatically applied at each csf restart.

how can i interpret the rules precisely as docker applies them to place into csfpre.sh? any suggestions? Thanks.

Posts: 4

Participants: 2

Read full topic

@MichaelDunn wrote:

I’m trying to post a message to my discourse server using the API. The title of the post I’m trying to make is
[2017-09-21] events.linear_spotlight_attribution_rate.events.ga_landing_content_type_bucketed.Doctor.Media..w..Lists.

Discourse responds with a 422 error, saying “Title seems unclear, is it a complete sentence?”

I would like to turn off whatever is checking the title. Having read other topics on this issue, I have allowed uppercase posts and I’ve set the min title entropy to 0 and the server continues to throw the error. I also turned off prettyifying of titles.

Trying to post the message via the UI results in the same error being thrown.

Any idea how to actually turn this off?

Posts: 3

Participants: 2

Read full topic