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

Cannot Load Interface After Initial Setup #5164

Closed
zimmerzc opened this issue Feb 20, 2020 · 11 comments
Closed

Cannot Load Interface After Initial Setup #5164

zimmerzc opened this issue Feb 20, 2020 · 11 comments

Comments

@zimmerzc
Copy link

I navigated to the correct FQDN and that redirected me to the initial startup page and I put in the correct MySQL Database information and saved it. Then the software redirected me to /session/begin. I was greeted with a "Not Found. The requested URL was not found on this server." So I navigated into the file structure for this install and went into the "Session" directory and there is not a directory called "Begin". I am confused as to why the software is trying to navigate me to that directory if it does not exist.

I am trying to install the latest version, 4.0.1.

Hopefully, this is somewhat clear, but if not, please ask me to provide more information if needed!

@crossan007
Copy link
Contributor

Are you doing a clean install or an upgrade?

@crossan007
Copy link
Contributor

It looks like you're missing .htaccess in the session directory

@zimmerzc
Copy link
Author

Clean install.

@crossan007 crossan007 added this to the User Support milestone Feb 20, 2020
@zimmerzc
Copy link
Author

Annotation 2020-02-20 134259
This is what is in my session directory.

@crossan007
Copy link
Contributor

Does your Apache configuration AllowOverride for the churchcrm directory? If not, the .htaccess fill will be of no use

@zimmerzc
Copy link
Author

It didn't. I changed that and now it works! Thank you!

@zimmerzc
Copy link
Author

Annotation 2020-02-20 135934
But when I log in with the admin credentials, I get this.

@crossan007
Copy link
Contributor

Oh no. I think this might a be a bug in 4.0.1 that affects only clean installs.

I'll look into it, but for now you can probably get going by modifying the only entry in your version_ver table from 4.0.1 to 3.5.5 to "trick" the application into running the upgrade from 3.5.5 to 4.0.1.

@crossan007 crossan007 modified the milestones: User Support, Backlog Feb 20, 2020
@crossan007 crossan007 self-assigned this Feb 20, 2020
@crossan007
Copy link
Contributor

essentially, I think the schema changes in 4.0.0 (https://github.com/ChurchCRM/CRM/blob/master/src/mysql/upgrade/4.0.0-TwoFactorAuth.sql) are missing from the install.sql file(https://github.com/ChurchCRM/CRM/blob/master/src/mysql/install/Install.sql).

You could also manually run the 4.0.0 upgrade file and see if that works

@zimmerzc
Copy link
Author

I updated to version 4.0.2 and everything seems to be working! Thank you for all of your help with this issue! I do have one other question. What do I need to do in order to get the "Application Integrity Check" to properly work?
Annotation 2020-02-21 135812

@crossan007
Copy link
Contributor

crossan007 commented Feb 21, 2020

@zimmerzc integrityCheck.json is created during the call to /api/background/timerjobs after first login and each subsequent page load

it contains the status of validating the files in your installation against the official hash.

if the file doesn't exist, the check may not yet have run, or the process running your web server (www-data, apache, or other), doesn't have permission to write in the app directory

In General Settings | System Settings, what timestamp is listed for sLastIntegrityCheckTimeStamp?

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

2 participants