Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTTP 500 Error #4151

Closed
nbickfud opened this issue Mar 18, 2018 · 10 comments
Closed

HTTP 500 Error #4151

nbickfud opened this issue Mar 18, 2018 · 10 comments

Comments

@nbickfud
Copy link

If you have the ChurchCRM software running, please file an issue using the Report an issue in the help menu.

On what page in the application did you find this issue? Login

On what type of server is this running? Dedicated / Shared hosting? Linux / Windows? Shared, Ubuntu Linux

What browser (and version) are you running? Chrome vs 65 (Android) and Samsung browser

What version of PHP is the server running? 7.0.25

What version of SQL Server are you running? 5.7.21

What version of ChurchCRM are you running? 3.0.0

I performed a fresh install of churchcrm 3.0.0 about 24 hours ago. Once I got it up and running, everything ran smoothly (accept for the images folder which I will address after this error). Four hours ago I accessed the website and everything was fine. But now when I try to access the website, all I get is an http 500 error.

I have attempted clearing cookies and browser cache, and have tried a browser that has never accessed the site before.

Folder and file permissions are set to 755. Mod rewrite is working.

There is another website on the same server that is working without issue.

No updates have been performed on the server since installing churchcrm.

Any help would be appreciated.
~ Nathaniel

@DawoudIO
Copy link
Contributor

Please check the logs dir for PHP errors

@crossan007 crossan007 added this to the User Support milestone Mar 18, 2018
@nbickfud
Copy link
Author

The only log files I can find end in app.log and orm.log

Neither of those logs mention anything about pho, or even other errors.

@DawoudIO
Copy link
Contributor

check file perms in case they got changed

@nbickfud
Copy link
Author

Ok. Tried out permissions. Doing 755 again did absolutely nothing. So out of curiosity I tried 777 and now it works. However, I know that is very insecure, so I don't want to leave it that way.

My other website on the same server is running mostly 755 for folders and 644 for files and isn't having a problem.

In case it is related, I have also had problems with the Images folder not being writeable. I previously tried making that folder 777, but it did not help. However, now that I have made the entire churchcrm folder 777, the Images folder seems to work.

@DawoudIO
Copy link
Contributor

You don’t need 777 just 755

@nbickfud
Copy link
Author

Right, but I still got the http 500 error with 755. It only corrected itself when I switched everything to 777.

I have now switched everything back to 755, and everything is working the way it did with the initial install (so I can access the site), but that also means the Image directory is not writeable once again.

@nbickfud
Copy link
Author

So the same problem just occurred again: I was suddenly confronted with an http 500 error when attempting to access the site. The only way to fix it was by applying 777 permissions. Once done, I could access the site and reset permissions to 755.

@DawoudIO
Copy link
Contributor

Looks like a hosting issue we don’t change file permissions

@nbickfud
Copy link
Author

I am hosting the site on my own hardware. As I mentioned above, I am running another website on the same hardware, without issue. With churchcrm, the permissions aren't actually changing, but within 12-24 hours, I have to elevate permissions in order to gain access to the site. This seems odd to me since I do not have the same issue with the other site.

@nbickfud
Copy link
Author

Well, I think I figured out the problem. This was my second install of churchcrm (the first had lots of problems that I suspect were due to corrupted files), and apparently when I installed, I forgot to change ownership of the files and folders. So, if anyone else has a similar problem, make sure the files and folders aren't owned by the root user.

@ghost ghost removed the bug label Mar 22, 2018
@DawoudIO DawoudIO removed this from the User Support milestone Mar 23, 2018
@crossan007 crossan007 added this to the User Support milestone Mar 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants