A nice little change was proposed by @supermathie and @sam – indicate the keyboard shortcut for close on our editor education panels:
Since these are desktop only CSS rules they wouldn’t affect mobile, and arguably since more people have the keyboard option on iPad every day, it is still relevant on iPad and other touch devices too.
I think there are other opportunities for ambient indication of return and esc options in the UI, too… but this is the lowest hanging
Hello there!
I am encountering this problem after installing Discourse in Vultr (1GB installation with swap. Ubuntu 16.04).
Followed all the steps here:
Server mail was not working (although it did get through the registration) so I decided to wipe out the server and start again with Mailgun. But after inputting the details for the registration and clicking on submit I get HTTP 500.
Here the log bit:
Completed 500 Internal Server Error in 230ms (ActiveRecord: 36.7ms)
NoMethodError (undefined method `strip' for nil:NilClass)
/var/www/discourse/app/controllers/finish_installation_controller.rb:15:in `register'
Also getting this:
Error connecting to Redis on localhost:6379 (Errno::ECONNREFUSED) subscribe failed, reconnecting in 1 second. Call stack ["/var/www/discourse/vendor/bund
le/ruby/2.3.0/gems/redis-3.3.3/lib/redis/client.rb:345:in `rescue in establish_connection'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.
3/lib/redis/client.rb:331:in `establish_connection'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.3/lib/redis/client.rb:101:in `block in
connect'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.3/lib/redis/client.rb:293:in `with_reconnect'", "/var/www/discourse/vendor/bundle/
ruby/2.3.0/gems/redis-3.3.3/lib/redis/client.rb:100:in `connect'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.3/lib/redis/client.rb:364:
in `ensure_connected'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.3/lib/redis/client.rb:221:in `block in process'", "/var/www/discourse
/vendor/bundle/ruby/2.3.0/gems/redis-3.3.3/lib/redis/client.rb:306:in `logging'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.3/lib/redis
/client.rb:220:in `process'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.3/lib/redis/client.rb:134:in `block in call_loop'", "/var/www/d
iscourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.3/lib/redis/client.rb:280:in `with_socket_timeout'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/r
edis-3.3.3/lib/redis/client.rb:133:in `call_loop'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.3/lib/redis/subscribe.rb:43:in `subscript
ion'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.3/lib/redis/subscribe.rb:12:in `subscribe'", "/var/www/discourse/vendor/bundle/ruby/2.
3.0/gems/redis-3.3.3/lib/redis.rb:2765:in `_subscription'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.3/lib/redis.rb:2143:in `block in
subscribe'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.3/lib/redis.rb:58:in `block in synchronize'", "/usr/local/lib/ruby/2.3.0/monitor
.rb:214:in `mon_synchronize'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.3/lib/redis.rb:58:in `synchronize'", "/var/www/discourse/vendo
r/bundle/ruby/2.3.0/gems/redis-3.3.3/lib/redis.rb:2142:in `subscribe'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.5/lib/message_b
us/backends/redis.rb:302:in `global_subscribe'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.5/lib/message_bus.rb:513:in `global_su
bscribe_thread'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.5/lib/message_bus.rb:461:in `block in new_subscriber_thread'"]
Job exception: Error connecting to Redis on localhost:6379 (Errno::ECONNREFUSED)
Tried to to git pull+rebuild and nothing…
Any ideas? Let me know if you need any further details…
Thanks!!
The last line of a ./laucher rebuild app has the docker command that cranks up the container. If you subsequently do a rebuild and it fails due to a bad plugin or whatever, you’re sort of stuck. Is there some way to re-start the previously running container and deal with the rebuild later on?
I’ve looked at the configs and I can’t figure out how to change the host that email is being sent from, other than changing the DISCOURSE_HOSTNAME variable. However, based on the comments, If I change that to say… example(dot)com, then if I visit VPS.provider.example(dot)com, I will no longer see the discourse service.
Alrighty, let’s see if I can make that a bit clearer now… (my real domain is replaced with example.com)
My VPS hosting discourse is on a different machine than my email server (due to the fact that I don’t trust the discourse-setup and launcher scripts being run as root).
My email server serves email from example(dot)com
Discourse is running on myvps.do.example(dot)com
Discourse is logging into smtp.example(dot)com to send emails
Discourse is sending emails from noreply@myvps.do.example(dot)com
Google receives the email and throws it away due to strict SPF and DKIM rules
Google sends me an email of said rejection by the next day via the DMARC system
I’m not sure what I can do to fix this, is there anyway to change the sending address? (I’ll be taking a look into spoofing the header.from=myvps.do.example.com from the postfix side to see if that helps at all) I’m able to login to the system since I can send emails to example(dot)com and be just fine, but sending to other email providers is another story.
We’re on 1.9.0.beta7 and have had two new users blocked with what appears to be copy/pasting in the Welcome Bot journey while they tried to get the ‘certified’ badge.
We did get a mod message and approved it but it was a while till we noticed the ‘block’ in the log.
Just wanted to provide feedback, and see if there is some way to get around having to look out for this? I know they shouldn’t be copy/pasting as part of the new user welcome training, but it looks like some people do.
#!/bin/bash
# This script should be located on each Jenkins slave, and the jenkins user should have permission to run it with sudo
# Attempts to cleanly stop and remove all containers, volumes and images.
docker ps -q | xargs --no-run-if-empty docker stop
docker ps -q -a | xargs --no-run-if-empty docker rm --force --volumes
docker volume ls -q | xargs --no-run-if-empty docker volume rm
docker images -a -q | xargs --no-run-if-empty docker rmi -f
# Stops the docker service, unmounts all docker-related mounts, removes the entire docker directory, and starts docker again.
service docker stop
while [[ -n $(mount | grep -E "^none") ]]; do
echo "Unmounting none"
umount none
done
umount /var/lib/docker/aufs
echo "Deleting content of /var/lib/docker"
rm -rf /var/lib/docker/*
I am self-hosting Discourse on Digital Ocean and I received an upgrade notice. When I try to use the web option, it says I have to log in via SSH and run the upgrade command. But when I log in using SSH, it always wants to run the configuration script that I already did when I first installed. How do I bypass or disable this so I can get to the command prompt? thanjs
If you are on a forum which has enabled a maximum amount of likes per day, and you reach this maximum, but really like a post you saw, and talke away a like you gave on another post, and proceed again to try to like the post you really liked, itll still say you "have reached your maximum likes per day. Try again in xx hours
So I recently switched to a new server. I have multiple servers with them. The site was working fine and the host shut off the wrong server. When they tried to bring it back up I get a 502 error on the site.
I accessed the server and they said to try port 3000 to launch the app. I went into app.yml and changed the port to 3000 (maybe in wrong place?) and when I go to rebuild i get these errors.
LOG: could not open configuration file "/etc/postgresql/9.5/main/pg_hba.conf": Permission denied
2017-08-19 15:52:13.733 UTC [44] FATAL: could not load pg_hba.conf
I, [2017-08-19T15:52:18.547133 #15] INFO -- :
I, [2017-08-19T15:52:18.547828 #15] INFO -- : > su postgres -c 'createdb discourse' || true
createdb: could not connect to database template1: 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"?
I, [2017-08-19T15:52:18.634427 #15] INFO -- :
I, [2017-08-19T15:52:18.634701 #15] INFO -- : > su postgres -c 'psql discourse -c "create user discourse;"' || true
psql: 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"?
I, [2017-08-19T15:52:18.715596 #15] INFO -- :
I, [2017-08-19T15:52:18.715966 #15] INFO -- : > su postgres -c 'psql discourse -c "grant all privileges on database discourse to discourse;"' || true
psql: 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"?
I, [2017-08-19T15:52:18.779628 #15] INFO -- :
I, [2017-08-19T15:52:18.780018 #15] INFO -- : > su postgres -c 'psql discourse -c "alter schema public owner to discourse;"'
psql: 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"?
I, [2017-08-19T15:52:18.843265 #15] INFO -- :
I, [2017-08-19T15:52:18.844098 #15] INFO -- : Terminating async processes
FAILED
--------------------
Pups::ExecError: su postgres -c 'psql discourse -c "alter schema public owner to discourse;"' failed with return #<Process::Status: pid 70 exit 2>
Location of failure: /pups/lib/pups/exec_command.rb:108:in `spawn'
exec failed with the params "su postgres -c 'psql $db_name -c \"alter schema public owner to $db_user;\"'"
15a5b5711ba8a90c848d928552e957e3a44ee6ca51b915c605ba65a34507205f
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one
FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle install --deployment --verbose --without test --without development' failed with return #<Process::Status: pid 359 exit 7>
Location of failure: /pups/lib/pups/exec_command.rb:108: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'"]}
5d1ddc450c71623db162884cdd854e23d9108eb10a45ba3b12833491667ede2a
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one
As it said I should read the former lines for more error messages, I checked the message in ./launcher rebuild app and found the only more message is
2017-08-20 04:27:13.878 UTC [56] postgres@postgres ERROR: database "discourse" already exists
2017-08-20 04:27:13.878 UTC [56] postgres@postgres STATEMENT: CREATE DATABASE discourse;
createdb: database creation failed: ERROR: database "discourse" already exists
I, [2017-08-20T04:27:13.880744 #15] INFO -- :
I, [2017-08-20T04:27:13.881052 #15] INFO -- : > su postgres -c 'psql discourse -c "create user discourse;"' || true
2017-08-20 04:27:13.966 UTC [67] postgres@discourse ERROR: role "discourse" already exists
2017-08-20 04:27:13.966 UTC [67] postgres@discourse STATEMENT: create user discourse;
ERROR: role "discourse" already exists
And here is the docker images that might help.
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
f8b075b4656b sameersbn/gitlab:latest "/sbin/entrypoint...." 3 months ago Up 21 minutes 443/tcp, 0.0.0.0:10022->22/tcp, 0.0.0.0:10080->80/tcp gitlab_gitlab_1
d2dd063db080 sameersbn/redis:latest "/sbin/entrypoint...." 11 months ago Up 21 minutes 6379/tcp gitlab_redis_1
e875efc4b0b5 sameersbn/postgresql:9.4-21 "/sbin/entrypoint.sh" 11 months ago Up 21 minutes 5432/tcp gitlab_postgresql_1
Could you please help me？
I checked meta, and found some perhaps similar answers, but I tried rebooted the server, and nothing happened.
Is it because this is a server in China, and now some of the websites are blocked by the great Chinese firewall?
What’s more
It’s not only not rebuildable, but also the server encounters 502 Badgateway(nginx) error.
I checked the docker is running.
I restarted the discourse, rebooted the server, but still nothing happened.
How can I acquire exact vote numbers in some votings? We are currently voting for trust level 4 people. People have 5 votes. There are 40 candidates, which I had to split into 2 polls because it only accepts 20 per poll. That is, 5 votes split between the two polls. This means that the total of votes differs per poll so the percentages do not correspond.
For exact resolving, I would need to acquire the exact numbers of votes in the polls. How is this done?
We’re having a bit of a problem on https://community.infinite-flight.com
Seems like the IP address lookup is partially failing.
As far as i can tell, it only fails to retrieve the location & ISP data of the IP address in question and duplicate accounts are displayed properly. I’m not 100% sure of the duplicate detection though, as i haven’t seen any recent lookup of new members displaying duplicate accounts and we usually have a few each day.
Previous install sendgrid settings are kept the same. Nothing changed there when I first moved the server. Worked fine. Now Im moving back to another server and the same credentials are not working? Was there any change on that? This is what I am currently using.
Let me know if you need any further details…
