Guys, I am having an issue where some avatars are missing where you’ve quoted someone in a post. On investigating I noticed ‘:80’ being added to the end of each domain in the image URL for some avatars, but not others. When I copied a failed image’s URL(which begins https://) into a new browser tab and removed the :80 the avatar loaded fine. What is going wrong? Why is port 80 being used within the URL and how best to resolve this? Interestingly when you go and edit your post, the images in the preview work fine - they are missing the ‘:80’. Apologies for my lack of knowledge! Thanks!

You’ll need to set it to nil to fix it.

what does your DISCOURSE_HOSTNAME say in your app.yml file?

forgive me for maintaining privacy, but its basically: www.mydomain.org btw, I think Facebook logon has been broken since forcing https too … as its redirects seem to be using port 80 too …

Do you have any sort of proxy in front of Discourse? NGINX or Apache perhaps?

[image] jomaxro: NGINX or Apache NGINX is running …

This is very likely caused by something in your NGINX config then. Check out Run other websites on the same machine as Discourse for more details.

Sorry, @jomaxro, I’m not very experienced, so please forgive me, but: root@blah:/# ps waux | grep nginx returns: root 4252 0.0 0.0 4244 604 ? Ss 19:21 0:00 runsv nginx root 4257 0.0 0.1 82720 3476 ? S 19:21 0:00 nginx: master process /usr/sbin/nginx www-data 4271 0.3 0.2 84908 5176 ? S 19:21 0:07 nginx: worker process www-data 4272 0.3 0.2 84628 5620 ? S 19:21 0:07 nginx: worker process www-data 4273 0.0 0.0 82888 1908 ? S 19:21 0:00 nginx: cache manager process But i’m only running the vanilla discourse install in a docker container. I didn’t explicitly install nginx Does that change anything?

[image] merefield: Does that change anything? Yes it does. Discourse runs NGINX inside the docker container, so that might be what you’re seeing. That’s not my area of expertise, unfortunately, you’ll need to wait for someone else who can confirm if the NGINX you’re seeing is inside or outside the container.

[image] merefield: On investigating I noticed ‘:80’ being added to the end of each domain in the image URL. When I copied a failed image’s URL into a new browser tab and removed the :80 the avatar loaded fine. So seems port 80 is being blocked? Does the URL of a failing image start with http or https?

[image] schleifer: Does the URL of a failing image start with http or https? https, but suffixed with :80 (which will clearly fail as https doesn’t use this port?) e.g.: https://www.mydomain.org:80/letter_avatar_proxy/v2/letter/b/f475e1/40.png the word ‘proxy’ is interesting!

[image] merefield: e.g.: https://www.mydomain.org:80/letter_avatar_proxy/v2/letter/b/f475e1/40.png That’s not a custom avatar URL. The default capital letters load from our CDN => https://avatars.discourse.org/v2/letter/b/f475e1/40.png

URLs for avatars & emoticons adding :80 to the end of the domain

Product Support Self-hosting

merefield (Robert) January 28, 2018, 11:51pm 20

This seems to be resolved and no restart was required. Thanks for your help guys!

Topic		Replies	Views
Putting a discourse development server behind proxy seems to mess up some (but not most) URLs Development	17	3279	March 11, 2016
Avatar not found after updating to 1.4 beta because of port in URL Bug	9	2065	November 1, 2015
User avatars are not displaying Self-hosting	6	1941	July 1, 2016
Embed Images are set to https://domain.com:80 in email Self-hosting	6	759	September 8, 2019
Lots of problems installing Discourse under CentOS with NGINX forwarding Self-hosting	16	2785	September 2, 2016

URLs for avatars & emoticons adding :80 to the end of the domain

Related topics