Error 500 While Trying To Update Flarum

elawrenc01

Trying to update to the latest version. I received a message back

Something went wrong: <!DOCTYPE html> <html> <head lang="en"> <meta charset="UTF-8"> <title></title> </head> <body> <h1>500 Internal Server Error</h1> <p>Something went wrong on our server.</p> </body> </html>

Is this temporary?

luceos

elawrenc01 enable debug by setting false to true behind debug in your config.php file. This might tell you a specific reason.

elawrenc01

Now I get an error 403 I do not have permissions to access this page. I think the error is coming from the Flarum website, I am at my site /flarum/admin trying to update. I put in my admin password and I get this error. It appears the error happens when I try to connect to the update server.

elawrenc01

Oh I see what's happening... it's hitting my server.

Well, I updated with composer update

and then went to the admin section and put in my password.

Ill try a full reinstall

elawrenc01

Can't do that either. Tried running this command

composer create-project flarum/flarum . --stability=beta

In an empty directory and it fails. An error_log is being created in the directory with a PHP Warning regarding IMagick and then the install fails because the directory is no longer empty.

So is flarum trying to install Imagick?

luceos

elawrenc01 can you please post the exact error?

LinuxLefty

I'm not sure, maybe you have to enable the Imagick PHP module?

elawrenc01

PHP Warning: Module 'imagick' already loaded in Unknown on line 0

This is the error that is in the error_log when I try to install...

the composer error I receive is:

[InvalidArgumentException]
Project directory ./ is not empty.

luceos

elawrenc01 PHP Warning: Module 'imagick' already loaded in Unknown on line 0

can you post the exact dump of the error when installing. Sorry to be a stubborn old goat, but sometimes these errors tell you more than just the obvious.

As it's still mentioning that module can you check it's on;

php -i | grep imagick

elawrenc01 PHP Warning: Module 'imagick' already loaded in Unknown on line 0

you must have manually edit some php.ini, the preferred way of enabling php modules is using phpenmod and disabling using phpdismod; when (still) using php 5.* use php5enmod and php5dismod.

elawrenc01

I already have imagick installed

elawrenc01

Here is the dump...

[InvalidArgumentException]
Project directory ./ is not empty.

create-project [-s|--stability STABILITY] [--prefer-source] [--prefer-dist] [--repository REPOSITORY] [--repository-url REPO SITORY-URL] [--dev] [--no-dev] [--no-custom-installers] [--no-scripts] [--no-progress] [--no-secure-http] [--keep-vcs] [--no -install] [--ignore-platform-reqs] [--] [<package>] [<directory>] [<version>]

This is what I get when I check for imagick
imagick
imagick module => enabled
imagick module version => 3.4.3
imagick classes => Imagick, ImagickDraw, ImagickPixel, ImagickPixelIterator
imagick.locale_fix => 0 => 0
imagick.progress_monitor => 0 => 0
imagick.skip_version_check => 0 => 0

luceos

elawrenc01 Project directory ./ is not empty.

Okay so that's the root cause now, what is the command you've ran? Make sure to target a directory that is really empty; use ls -la to see all hidden files too.

elawrenc01

Right that's where Im at at the moment. The whole directory is wiped and when I begin the install, an error_log file is created with the imagick warning.

This is the command I should be running, correct?
composer create-project flarum/flarum . --stability=beta

I created a directory called /forum and I enter that directory and run this command. It's worked for me before. But that was months ago.

luceos

Your php complains that the imagick module was already registered. Did you manually add an entry to the php.ini related to it?

elawrenc01

That was the issue.

I removed the imagick entry in php.ini and it's installing.

elawrenc01

Thank you for your help. Looks like the forum installed successfully. So if imagick is installed as a module there's no need to put an entry in php.ini?

luceos

elawrenc01 I think it was registered elsewhere already and you added an entry which made the registration duplicate, thus causing (just) a warning.