Flarum encountered a boot error.

KBExit

boohoo you can customize your path but you didn't have it set properly.
Easiest way to install Flarum is the way I described. You deviate from what I suggested, you can break your install or be back to square one to where you had files exposed that shouldn't be.

Just move your document root to what I suggested and be done with it after you detach Softaculous. It doesn't take that much time.

Tip-toeing and avoiding Composer/SSH is only going to cause you more headaches down the road.

boohoo

When you say all of that, do you basically mean follow the flarum instructions that use composer and copy over the files you mentioned? Does this deviate from the flarum instruction list?

GreXXL

boohoo what you actually just need to do is point your document root to your /public directory instead of /public_html or wherever it's pointed now and you will have a much better installation.

KBExit

boohoo follow the install instructions from Flarum, but prior to doing so, point document root to /public.
After you have everything set up, upload your backups and run composer update and your site will have your old content and you'll have a secure install.

boohoo

GreXXL @KBExit

So both of you contradict each other. I can easily scrap my Softaculous record of Flarum installation and copy everything back over to where it was and put the database back and fix the document root (maybe). Or should I rebuild everything?

I have no public folder because I removed flarum. Do I make a folder public_html/public? My file structure is I have everything in my main site in public_html, like index.html. Then I have some website folders there and one is brainchildforum. Do I have to contact my web admin to point the document root to public_html/public? I have some other files from my main website that I don't want to change anything for. Doesn't making a public_html/public folder that I put my files from brainchildforum in not work because the public folder is not within the branchildforum website folder?

Are you saying I have extra file space in public_html that no one can see and store everything that's on the web in public_html/public, but then I lose the chain public_html/website666....which is my url chain

I'm just a newb that barely figured out ssh.

Or I could do the thing where I put all my public files out of the public folder and into the website folder.

KBExit

I suggested my approach to detach from Softaculous entirely because they do an improper install of Flarum and I know the software handles updates as well. I don't want you to have issues down the road.
Best approach is to do a proper clean install with the method I've suggested. @GreXXL is suggesting to just move Document Root to /public, but I don't know if he ran Flarum Softaculous before. I am relaying my experiences from using the software when I started out using Flarum.

boohoo

KBExit Okay. I am doing that. I am just wondering whether SQL Dump of the current database is free from installation problems. SQL Dump is a really big pain for me, and I want to know that it's a perfect idea...

KBExit

boohoo dumping the SQL is just downloading what's in your tables currently. It's how you should perform backups. If you haven't been doing it before, I strongly advise you to do it from here on out.
Along with proper security updates, SSH Hardening, audits, etc. If you have issues with these, I strongly advise going for a managed hosting solution so you can just worry about the content and community at hand. There's a lot of moving parts when managing communities, especially when users are trusting you to handle their data safely.

boohoo

I am worried about it going down and losing everything. I don't have the money for flarum hosting or your service but probably if my site gets bigger and as those security issues become more important I will try to migrate it over to some sort of flarum hosting since I don't know any of those extra things. Okay, I am trying a normal install now.

KBExit

boohoo for long-term sustainability of a website, especially communities, you have to have a healthy budget in mind.

Standard install is the best way to go. Softaculous has known about their installation being insecure for about 3 years now. Really shows you how much they care.

boohoo

Well, I got pretty far installing on my own. Just saying. Now, I got horribly stuck, and I didn't want to do a new thread because it has to have happened before. I have not seen the topic searching, though.

Nginx
Flarum includes a .nginx.conf file – make sure it has been uploaded correctly. Then, assuming you have a PHP site set up within Nginx, add the following to your server's configuration block:

include /path/to/flarum/.nginx.conf; -> for me: /flarum/.nginx.conf

My 2 .nginx.conf's files don't have anything like "server." What is a server's configuration block? This is a massive headache. I have shared hosting, so I don't know how things are this way.

clarkwinkelmann

boohoo perhaps you can share the content of the files you found (if they don't contain any sensitive information) so we can get a better idea.

Nginx configuration files are structured in blocks enclosed in brackets {}. It always starts somewhere with a server[...]{} block. If you are on a shared hosting, perhaps your host hides those root files and instead shows you a config file that is being included from those hidden root files. In that case you might be able to put the Flarum code directly in there (either the include instruction, or the contents of the included file)

boohoo

This is my outer .nginx.conf file:

# Uncomment the following lines if you are not using a `public` directory
# to prevent sensitive resources from being exposed.
# <!-- BEGIN EXPOSED RESOURCES PROTECTION -->
# location ~* ^/(\.git|composer\.(json|lock)|auth\.json|config\.php|flarum|storage|vendor) {
#   deny all;
#   return 404;
# }
# <!-- END EXPOSED RESOURCES PROTECTION -->

# The following directives are based on best practices from H5BP Nginx Server Configs
# https://github.com/h5bp/server-configs-nginx

# Expire rules for static content
location ~* \.(?:manifest|appcache|html?|xml|json)$ {
  add_header Cache-Control "max-age=0";
}

location ~* \.(?:rss|atom)$ {
  add_header Cache-Control "max-age=3600";
}

location ~* \.(?:jpg|jpeg|gif|png|ico|cur|gz|svg|mp4|ogg|ogv|webm|htc)$ {
  add_header Cache-Control "max-age=2592000";
  access_log off;
}

location ~* \.(?:css|js)$ {
  add_header Cache-Control "max-age=31536000";
  access_log off;
}

location ~* \.(?:ttf|ttc|otf|eot|woff|woff2)$ {
  add_header Cache-Control "max-age=2592000";
  access_log off;
}

# Gzip compression
gzip on;
gzip_comp_level 5;
gzip_min_length 256;
gzip_proxied any;
gzip_vary on;
gzip_types
    application/atom+xml
    application/javascript
    application/json
    application/ld+json
    application/manifest+json
    application/rss+xml
    application/vnd.geo+json
    application/vnd.ms-fontobject
    application/x-font-ttf
    application/x-web-app-manifest+json
    application/xhtml+xml
    application/xml
    font/opentype
    image/bmp
    image/svg+xml
    image/x-icon
    text/cache-manifest
    text/css
    text/javascript
    text/plain
    text/vcard
    text/vnd.rim.location.xloc
    text/vtt
    text/x-component
    text/x-cross-domain-policy;

**Tell me if there is something I should keep a secret.  Second file:**

> # Pass requests that don't refer directly to files in the filesystem to index.php
location / {
  try_files $uri $uri/ /index.php?$query_string;
}

# Uncomment the following lines if you are not using a `public` directory
# to prevent sensitive resources from being exposed.
# <!-- BEGIN EXPOSED RESOURCES PROTECTION -->
# location ~* ^/(\.git|composer\.(json|lock)|auth\.json|config\.php|flarum|storage|vendor) {
#   deny all;
#   return 404;
# }
# <!-- END EXPOSED RESOURCES PROTECTION -->

# The following directives are based on best practices from H5BP Nginx Server Configs
# https://github.com/h5bp/server-configs-nginx

# Expire rules for static content
location ~* \.(?:manifest|appcache|html?|xml|json)$ {
  add_header Cache-Control "max-age=0";
}

location ~* \.(?:rss|atom)$ {
  add_header Cache-Control "max-age=3600";
}

location ~* \.(?:jpg|jpeg|gif|png|ico|cur|gz|svg|mp4|ogg|ogv|webm|htc)$ {
  add_header Cache-Control "max-age=2592000";
  access_log off;
}

location ~* \.(?:css|js)$ {
  add_header Cache-Control "max-age=31536000";
  access_log off;
}

location ~* \.(?:ttf|ttc|otf|eot|woff|woff2)$ {
  add_header Cache-Control "max-age=2592000";
  access_log off;
}

# Gzip compression
gzip on;
gzip_comp_level 5;
gzip_min_length 256;
gzip_proxied any;
gzip_vary on;
gzip_types
    application/atom+xml
    application/javascript
    application/json
    application/ld+json
    application/manifest+json
    application/rss+xml
    application/vnd.geo+json
    application/vnd.ms-fontobject
    application/x-font-ttf
    application/x-web-app-manifest+json
    application/xhtml+xml
    application/xml
    font/opentype
    image/bmp
    image/svg+xml
    image/x-icon
    text/cache-manifest
    text/css
    text/javascript
    text/plain
    text/vcard
    text/vnd.rim.location.xloc
    text/vtt
    text/x-component
    text/x-cross-domain-policy;

I think they're nearly the same. I've installed this so many times and moved my original copy's files back a folder (and tried from the .zip folder also) that I think I have some duplicates? I can delete everything I think is flarum and reinstall it, but I'm not so sure what was in there originally. It might be risky...

boohoo

clarkwinkelmann
I replied. I forgot to say I replied.

clarkwinkelmann

boohoo I think you're just looking at Flarum's nginx file.

Somewhere else on your server filesystem, or somewhere in the server management panel, there should be an nginx configuration file for your particular site. The content varies depending on the hosting, in its simplest form it can be a file that contains just a line that says root <path to site on filesystem>

Including Flarum's .nginx.conf file is not strictly required. As long as your host included a default try_files directive in their own nginx configuration, the forum should be accessible. Including Flarum's additional configuration is mostly for performance improvements through file caching and headers. The try_files directive must exist only once, so if you include the one from the Flarum file, you usually remove it from the server global configuration.

boohoo

clarkwinkelmann Is only one of Apache, Caddy, or Nginx needed?

KBExit

boohoo you only need what your server needs. If your server is nginx, you need nginx. If your server is apache, that's what you need

boohoo

clarkwinkelmann Well, I'm working on "Something went wrong while trying to load the full version of this site. Try hard-refreshing this page to fix the error.
All Discussions"
but at least there' s stuff online about it.

A lot of my permissions are d or -rwxrwxr-x. Do I want that? Wouldn't I always want group to be the same as other - 755?

drwxr-x--- 3 aaa nobody 4096 Jan 28 15:01 ./
drwxrwxr-x 5 aaa aaa 4096 Jan 27 19:24 ../
drwxrwxr-x 4 aaa aaa 4096 Jan 28 15:14 assets/
-rw-r--r-- 1 aaa aaa 520 Jan 28 15:01 error_log
-rwxrwxr-x 1 aaa aaa 7122 Jan 2 2024 .htaccess*
-rwxrwxr-x 1 aaa aaa 860 Jan 2 2024 index.php*
-rwxrwxr-x 1 aaa aaa 1490 Jan 2 2024 web.config*

I think some of these files are from when the web hosting account started, which doesn't make sense. But do I keep 775s, or should they all be 755?

boohoo

KBExit

I'm keeping my permissions ast 775.

I am uninstalling and reinstalling once I understand all of the steps.

SSH Using Terminal and go to your root directory, run the Flarum Installation Command.
composer create-project flarum/flarum:¹.8.0
OK

Change the document root from public_html to public_html/public
I have a root/flarum/public folder after installation. I add a public folder to public_html and do what since my flarum folder is up one level from public_html? I ask my hosting service to point to public_html/public but then what about my url brainchildforum, which is not my primary site at public_html? Do I move my public files at flarum/public to public_html/public and ask my web host to point brainchildforum to public_host/public? Wouldn't that cause files not be able to find another if you change what directory they're in? I think part of it is I don't know what the document root is. I'm taking it to mean the weirdly-named-folder above my public_html.

Go to your website, complete the Installation Wizard.
You mean extension manager?

Upload and override those files in the Flarum Directory, upload your SQL Dump to your database to recover your website details, and run composer update in your Flarum Directory.

Thanks for the help, but I am very confused about the "Change the document root from public_html to public_html/public"

KBExit

boohoo public_html/public was merely an example.
What is the current root directory to which your site holds? Example: if it's: public_host, your want your public folder to be public_host/public. Then you'll configure the root directory to that. This will serve your flarum website securely. Your essential files are in public_host and we don't want the public to be able to snoop there at all.

Once you have all that set up, when you visit your website: brainchildforum, your flarum install wizard will populate to go through the steps.

« Previous Page Next Page »