Some links and avatars show as broken


(Bryan) #1

This error is shown in sidekiq.

Error Class
ActionView::Template::Error
Error Message Invalid :protocol option: "http://http://"

Users can upload avatars but they do not show, and only show a broken image icon. Also, when I tested with mandrill it had the url of my site with an extra “http://”. I am not sure how I can fix this.

Also, after uploading an image to the assets topic, it changes to this url:

http://http//bestindustrygroups.org/uploads/default/5/5b146c5714f66b6e.png

So something is definitely wrong. Can’t find any info on this topic. I know it’s just because I most likely mistakenly added the http to my domain url at some point.


Broken images inside posts
(Bryan) #2

any ideas on this? I am stumped…


(Jeff Atwood) #3

Paste the contents of your app.yml here?


(Bryan) #4

For some reason when I do:

nano containers/app.yml

its just empty…so I can’t see anything.

I tried sftp to find it but I don’t know where the app.yml file is.

EDIT : I found it, and I had added http:// in front of the domain. But how come I can’t see its content over ssh?

doh…


(Bryan) #5
##
## After making changes to this file, you MUST rebuild for any changes
## to take effect in your live Discourse instance:
## 
## /var/docker/launcher rebuild app
##

## this is the all-in-one, standalone Discourse Docker container template
templates:
  - "templates/cron.template.yml"
  - "templates/postgres.template.yml"
  - "templates/redis.template.yml"
  - "templates/sshd.template.yml"
  - "templates/web.template.yml"

## which TCP/IP ports should this container expose?
expose:
  - "80:80"   # fwd host port 80   to container port 80 (http)
  - "2222:22" # fwd host port 2222 to container port 22 (ssh)

params:
  ## Which Git revision should this container use?
  version: HEAD

env:
  ## How many concurrent web requests are supported?
  ## With 2GB we recommend 3-4 workers, with 1GB only 2
  UNICORN_WORKERS: 2
  ##
  ## List of comma delimited emails that will be made admin on signup
  DISCOURSE_DEVELOPER_EMAILS: 'bryan@sonomacountybest.com'
  ##
  ## The domain name this Discourse instance will respond to
  DISCOURSE_HOSTNAME: 'bestindustrygroups.org'
  ##
  ## The mailserver this Discourse instance will use
  DISCOURSE_SMTP_ADDRESS: smtp.mandrillapp.com  
  DISCOURSE_SMTP_PORT: 587
  DISCOURSE_SMTP_USER_NAME: bry.bell@gmail.com      
  DISCOURSE_SMTP_PASSWORD: REDACTED
  ##
  ## the origin pull CDN address for this Discourse instance
  # DISCOURSE_CDN_URL: discourse-cdn.example.com

## These containers are stateless, all data is stored in /shared
volumes:
  - volume:
      host: /var/docker/shared/standalone
      guest: /shared

## The docker manager plugin allows you to one-click upgrade Discouse
## http://discourse.example.com/admin/docker
hooks:
  after_code:
    - exec:
        cd: $home/plugins
        cmd:
          - mkdir -p plugins
          - git clone https://github.com/discourse/docker_manager.git

## Remember, this is YAML syntax - you can only have one block with a name
run:
  - exec: echo "Beginning of custom commands"

  ## If you want to configure password login for root, uncomment and change:
  #- exec: apt-get -y install whois # for mkpasswd
  ## Use only one of the following lines:
  #- exec: /usr/sbin/usermod -p 'PASSWORD_HASH' root
  #- exec: /usr/sbin/usermod -p "$(mkpasswd -m sha-256 'RAW_PASSWORD')" root

  ## If you want to authorized additional users, uncomment and change:
  #- exec: ssh-import-id username
  #- exec: ssh-import-id anotherusername

  - exec: echo "End of custom commands"
  - exec: awk -F\# '{print $1;}' ~/.ssh/authorized_keys | awk 'BEGIN { print "Authorized SSH keys for this container:"; } NF>=2 {print $NF;}'

Now I will rebuild?


(Jeff Atwood) #6

Yep you got it! Remove the http and rebuild.

I wonder if we should add special protection here @sam, this is the second time we’ve had someone add http:// in front of the DISCOURSE_HOSTNAME field…


(Jeff Atwood) #7