It's not a bug but feature ;)
I haven't encountered a problem like this before.
Maybe it has something to do with the setup (it being behind a reverse proxy)
- the site url configured in the site settings is correct (even http vs https matters). If for example the reverse proxy is handling the ssl encryption it'll send an http request to the webserver. However Elgg still needs to know it's https
- is the website installed in a subdirectory (like http://example.com/elgg/), then please check the RewriteBase in the .htaccess
PS: please check if you can update to Elgg 3.3 as Elgg 2.3 is in LTS and will not get any bugfixes anymore (except security fixes). See http://learn.elgg.org/en/stable/appendix/support.html
Thanks Jerome,
I had added the https, and amended the .htaccess as it's in a subdirectory.
Good shout about upgrading to 3.3 - I'll make that my next step forward as I'm still exploring and learning.
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by RaĆ¼l Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.