Closed DAOWAce closed 9 years ago
This is most likely because the PHP module "mbstring" is not enabled. You can check for it using this php -m | grep mb
php -m
returns a list of all installed/enabled php modules, grep mb
filters the output
Example:
vagrant@homestead:~$ php -m | grep mb
mbstring
HTML git is perfectly fine to use.
Not just not enabled, but not even installed!
php-common is installed, but it seem we still have to install a bunch of other extensions not included.
Installed, worked fine.
Writing lock file Generating autoload files Generating optimized class loader Compiling common classes Compiling views Application key set successfully.
I guess I should look up what's commonly installed with PHP packages; doing it manually (and upgrading to PHP5.5, which is not the default on AWS; it's old 5.3) has missed a lot.
Thanks for the help.
Bah, now I'm getting "Error in exception handler." when I access the directory for soldier in a browser. This is so nondescript I can't even trace what's gone wrong.
If I put solder into maintenance mode I get the page telling me it's in maintenance mode, but after bringing it up again it's right back to that 'error in exception handler' error.
Edit: After lots of googling, it seems this is a permissions error. I can't seem to get it work unless I set the permissions to 777.. and then it redirects and spits out "The requested URL /solder/public/dashboard was not found on this server."
Sigh..
Probably haven't given the storage folder write permissions.
Didn't catch your comment (never refreshed webpage or checked e-mail).
I gave the two directories full write permissions and it gets around the error, but as mentioned in my edit it's redirecting to a dashboard location which just doesn't exist at all.
I tried to start over from scratch again to reset all the ownership I was messing around with but no dice; still no dashboard folder.
Giving up banging my head against it at this point and taking a break. Expected to be on my own for many more hours, but hopefully I can get further advice on this issue.
There is no dashboard folder, the dashboard as well as every other page in the application are served via the index.php file. Also the ENTIRE solder folder should be chmoded to 775 with www-data (or what ever group you have setup for ngnix/apache, as the group owner.
The guide only mentioned 2 folders, public/resources and app/storage. And 775 didn't work, it had to be 777 (which is bad).
I'm using a LAMP setup on Amazon Linux (which makes it hard to mirror commands as they're different from something like ubuntu which most people use), my user is ec2-user and my group is just www and has ownership of the entire /var/www folder and its subfolders.
When I accessed the solder/public folder after fixing the permissions it immediately re-directs to public/dashboard. I didn't try going to the index.php file directly as that's what browsers load by default.
I'll try to look into it again after I take a break, but unless I'm being an idiot somewhere, everything should be setup properly..
Check the logs in app/storage/logs
and let me know if that has anything.
There's nothing but .gitignore in the log folder.
Tried accessing index.php directly and it redirects me to index.php/login and spits out the same 'error in exception handler' error.
Edit: After messing with groups, permissions, etc., reinstalling again, installing a whole bunch of other PHP stuff, I managed to get to the login screen when accessing index.php.
After logging in it spits out:
Look's like we've hit a snag!
Something went terribly wrong when we were fetching the page you requested. Please try your request again in a few minutes or follow the help link to find your issue.
500 SQLSTATE[HY000]: General error: 8 attempt to write a readonly database (SQL: update "users" set "last_ip" = xxx, "updated_at" = 2015-01-29 07:51:28 where "id" = 1)
I'm not using MySQL right now as mentioned in my OP, set it to stay on SQLite for the sake of minimizing setup.
Running a migrate:install makes it throw:
[Illuminate\Database\QueryException] SQLSTATE[HY000]: General error: 1 table "migrations" already exists (SQL: create table "migrations" ("migration" varcha r not null, "batch" integer not null))
[PDOException] SQLSTATE[HY000]: General error: 1 table "migrations" already exists
May try switching to MySQL now that it's actually running somehow as I have zero familiarity with SQLite and trying to learn from a command line interface isn't suited to my visual learner personality.
Well if for whatever reason Solder doesn't have write permissions to your sqlite database I could see this happening.
Well.. I just sorted out the issue, mostly.
It was a mismatch between ownership of the public_html directory (/var/www/html). The server is owned by root, but public_html was all owned by the AWS EC2 user, ec2-user.
For some reason, ec2-user didn't have access to things it wasn't the explicit owner of, despite being in the same www group root is in. I am too uneducated in this to understand why.
Additionally, doing a git pull on solder resulted in everything it created to be owned by ec2-user despite setting it all to root beforehand. I had to chown it after that and again after running the install script.
So, solder is working and I have access to the dashboard, though I still have to access index.php. I don't know why accessing the bare /public directory in a browser won't make it work.
Unfortunately, the problems haven't ended yet. I can't change user data or add mods/modpacks. It throws the same 'exception handler' error, which is apparently a permissions error from this whole experience. What could possibly be wrong now, I don't know. root/www now owns everything and the entire public_html folder is chmodded to 775 just to test.
At this point, I'm ready to just blow up the server and start from scratch and not touch permissions, as during setup it said to do a whole bunch of things (followed this tut: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/install-LAMP.html). I really don't know what else I can do aside from trying to switch everything to ec2-user instead of root.
All this just to stop a 250MB (and increasing) download for my modpack when I make a single change. /sigh
Doesn't EC2 have ubuntu distributions? It would have probably made this a lot easier.
I can help you out with this @DAOWAce just ring me up on skype, and I can help you out, it's not the hardest thing to install, just takes some trial and error. Skype: The_Doctors_Life
Doesn't EC2 have ubuntu distributions? It would have probably made this a lot easier.
Aside from the fact I haven't used Ubuntu either..
I administer Windows based PCs, not Linux or Mac; my experience with those is extremely limited, moreso if they're webservers I have to SSH into without having full remote control like a normal desktop PC.
I can help you out with this @DAOWAce just ring me up on skype
Thanks, but I'm one of the few people who don't actually use Skype, though I threw it on a VM just to test it out so I suppose I could talk there.
Followed the directions to setup Solder by the book, but I've run into an error.
When running the composer install --no-interaction command it goes through a whole bunch of stuff then spits out this error.
The php artisan commands don't work.
I have PHP5.5 and the required extensions using a MySQL database.
I don't know what's wrong, at all. This is my first time managing a linux webserver. I'm running an AWS EC2 server with Amazon Linux as well.
Been learning to setup AWS services all day so I'm really burned out and heading to bed.
Also, the SSH git command doesn't work for me, gives a "permission denied (publickey)" error, but the HTML git works just fine so this isn't much of an issue.