we discussed (on github and in the community) how to configure elgg 1.9 for nginx previously and i did have a working config file here. however, i recently lost the config file while upgrading the local OS and have not been able to locate a working one in the community here or in github.
when i run the one i grabbed from a discussion in github, i just see 'pageok' in the browser window.
from what i can tell this may be related to a domain routing issue, rather than an nginx mis-configuration.. however, so far, i haven't found the cause of the issue.
can anyone point me in a helpful direction to get 1.9rc7 running with nginx?
thanks
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.
We're running all our Elgg websites on nginx with this
nginx.config:
and this site-available:
Also, I'm using SSL + nginx + Elgg
by Srokap
and including your recommended config
ok great, thanks. i'll play with this soon and see what i can do here.
i have played with these configs for a while here. i have run through the 1.9.1 install process successfully.
however, when i load the site, i see an infinite redirect if i use this config:
http://z.wzm.me/?308b4be8617d94fd#H1dhAvCEXnLCS6EidzBCuNOy24E1E2+B+ShWprC1Nvo=
and i just see a blank white page when i use the srokap config.
there are no errors logged for nginx, php-fpm or the site.
any tips welcomed.
Note that top server definition is only redirect from port 80 to 443 when using ssl, if you happen to switch ports, you could create redirection loop indeed. You can remove first part completely if you plan to access server directly for testing or want to switch to non https only.
ah, i should have said already.. this local installation is http only. i had already removed any ssl specific parts.
i have gone through and commented out many parts, yet so far have not made any change in the resulting rendering of the site.
oh, so i went back to RvR's version and accessed upgrade.php -
i am seeing the error:
You must update your .htaccess file so that the path is injected into the GET parameter __elgg_uri (you can use htaccess_dist as a guide).
@ura soul Do you use Apache+nginx, or nginx as standalone only?
nginx standalone - latest stable version
(i have elgg 1.8.20 running fine on the same dev machine)
Should the same rewrite rules for elgg 1.8 work for both cases: installing elgg on root of web site (http://www.mydomain.com) and installing in a subfolder (http://www.mydomain.com/elgg)?
Using these rewrite rules at http://thomas.deuling.org/2012/01/elgg-community-1-8-2-rewrite-rules-for-nginx/
works fine when elgg is the root of the web site, but not when elgg is subfolder under the root of the web site.
Please help.
- Previous
- 1
- 2
- 3
- 4
- Next
You must log in to post replies.