Robert C

Send private message

You must be logged in to send a private message.

Friends

No friends yet.

Group membership

Activity

  • Robert C replied on the discussion topic Installation fails with "The site secret is not set."
    @Nikolai: That thread is still revolving around permissions issues with the elgg directories. I've already checked all of that several times over. I use CentOS because I'm familiar with the Red Hat ecosystem and use it for all of my... view reply
  • Robert C replied on the discussion topic Installation fails with "The site secret is not set."
    Hi, Thanks for replying so quickly. I have triple-checked and can tell you for certain that `apache:apache` owns all of /var/www/html and all children, including /var/www/html/elgg-config. It also has the correct SELinux context... view reply
  • Robert C added a new discussion topic Installation fails with "The site secret is not set." in the group Elgg Technical Support
    Following http://learn.elgg.org/en/stable/intro/install.html , installation abruptly stops with "The site secret is not set". Doesn't matter if I do it through the web installer (by visiting mypage.example/install.php ) or by using...
    • Only this...

      I can’t help you anymore because I don’t use CentOS (in fact, I don’t understand why people choose it).
      I believe this is a common bug for all CentOS users.

      If you don't find help here then refer to specialized sites with advanced CentOS users.

    • Robert,

      When I installed Elgg 3.3.16 on the same system as yours, I did not have the site secret issue. But I encountered it later when trying to migrate Elgg 2.x data to Elgg3.x database.

      I did not use 'vendor/elgg/elgg/elgg-cli' like you did when installing Elgg. I do not know if that is the cause of this issue or not. What I did was running 'vendor/bin/elgg-cli install' inside the project directory.

      With that being said, below is how I debug this site secret issue. 

      1. If you have an access to your MariaDB server, you can get the site secret from the config table - select value from {prefix}config where name like '%site_secret%';. 

      2. If the query above returns a value, then copy it (only string inside the double quotes) and paste it to the elgg-config/settings.php - $CONFIG->__site_secret__ = 'paste your site secret here';

    • @Nikolai:

      That thread is still revolving around permissions issues with the elgg directories. I've already checked all of that several times over.

      I use CentOS because I'm familiar with the Red Hat ecosystem and use it for all of my projects. I've not had any major issues configuring a CentOS server to run anything to this extent before.

      If this actually is a really common scenario, that apparently there's something about the CentOS environment that is consistently causing issues for people, would it be worth it at this point to file a bug on the Github issue tracker? I was originally thinking that my issues were rooted in dumb newbie mistakes that could be easily rectified, so I avoided posting my issue there. Now that I'm seeing that issues with CentOS are not particularly rare, I'm becoming more inclined to file an issue.

      @seri_ng:

      Thanks much for the hint about the config value in the settings file. I tried setting my own temporary dummy site secret in the hopes I could at least get Elgg to 'boot' properly and let me reset it automatically, but alas there is now a different error about an SQL query failure, which implies there's more deep-seated breakage in the database than I have much of a chance at fixing by hand being completely new to Elgg.