-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
core: Unknown or invalid schema signature #511
Comments
This generally happens when you upload osTicket to a Windoze server via FTP in ASCII mode. If that's the case for you, re-upload the files in binary mode |
That worked. Thanks a lot 👍 |
Hmmm...I'm getting this on Windows, but I used git clone. Any idea why that wouldn't work for me? Seems to have worked fine when I downloaded the zip and extracted manually. |
Re-upload the files with your FTP client set to BINARY mode |
I didn't upload or use FTP. I used Git clone. |
It's a newline issue with the files. Perhaps you git is configured strangely where it isn't honoring the file formats in the upstream repo |
I downloaded it as zip and installed as per procedure no problem has occured.. but when I tried to install using a cloned copy I faced this problem download the code as a zip file and unzip and try to install. |
@vikas-DabKick cross posting. Naughty. |
Just change the second part of signatures in the file- |
This worked for me. I pasted in the second signature that it was failing to match against. I truly have no clue what I'm doing, but hey, "it worked"! |
that worked, thanks |
same for me. |
@augustineashal I assume that when you cloned the repo you did not switch to the appropriate branch. In this case you'd clone it and use the Cheers. |
The Schema Signature is an MD5 hash of the Cheers. |
I just downloaded latest version (1.8.0.2) and uploaded it to my webhosting.
The installation keeps telling me this:
core: Unknown or invalid schema signature (6de40a4d5bad7a2923e769a4db1ff3b9 .. 833a0f36e10d073fb9e7fb3c8db4e8ef)
I have googled solution for osticket 1.7, but it was not suitable for me.
Thanks for help.
The text was updated successfully, but these errors were encountered: