but, why http://domainname.com -> redirect to http://www.domainname.com/ -> and work ? is this normal nginx behavior because the domain is not configured yet?
It's normal 🙂
server { listen 80; server_name domainname.com; [...] }Good morning from US Northeastern region.
As you can see above, the user hexth has broken link to his avatar. Upon inspection, I found out that the account is registered via Twitter SSO. And upon a bit deeper inspection, it seems like he changed his avatar on Twitter.
My question here is: how to make sure the user avatar doesn't go blank like that, if the user registered his/her account via Twitter SSO?
In nodebb:
Admin > Location & APIs > SSO > Twitter > Add new api token.
In Twitter:
(User menu > Settings > API > generate SSO.