-
-
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
Trouble getting Cachet to work on custom apache/php setup -- help appreciated! #2064
Comments
Laravel log on the aformentioned 404[2016-08-16 21:09:33] production.WARNING: exception 'Symfony\Component\HttpKernel\Exception\HttpException' in /home/y/share/html/Cachet/app/Http/Middleware/Authenticate.php:51 |
Laravel log for error submitting form when CSRF validation is turned on[2016-08-15 22:41:11] production.NOTICE: exception 'Illuminate\Session\TokenMismatchException' in /home/y/share/html/Cachet/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/VerifyCsrfToken.php:67 |
As you said before, this kind of installation is completely unsupported and without intimate or "on-site" access, we'd be shooting in the dark. We do offer an installation service if that's of any use? |
What session driver are you using please? |
@jbrooksuk I don't think we'll be going for the installation service, unfortunately. @GrahamCampbell I'm using the file driver for sessions and cache |
Try using redis or apc. |
After trying it with redis (our internal version of PHP has deprecated apc), I've had no luck. On login attempts with CSRF token validation enabled, I get the TokenMismatchException. When I remove the CSRF Middleware from app/Http/Kernel.php, I get a 404 at /auth/dashboard. Oddly enough, the non-company-compliant installation I set up seems to redirect at /dashboard after a login, not /auth/dashboard -- although that path may just be an intermediate that it glosses over quickly. Anyway, I installed Redis, configured it in .env, 'require'ed predis/predis, and then ran And restart apache, but to no avail... |
Digging really deep into some really old documentation, I have found that $_COOKIE and $_ENV are disabled in our version of PHP. Even further digging shows that $_COOKIE and $_ENV are only referenced in composer, symfony, guzzlehttp, psr, and vlucas. Also none of the files that are reported in the Laravel stack traces |
Laravel does use them. It loads them into the symfony request object right at the start. |
Closing since this isn't a bug in cachet. Feel free to keep the discussion going if you want though. :) |
Laravel uses all those deps, or cachet does in some way. We didn't just install them for the lols. :P |
I know Laravel uses those, but what I wonder why none of them show up in the stack trace for the errors? Essentially, if I'm committing to patching those out for our installation, I need to know they're actually causing the issues I'm having |
Background Info
Okay, so I understand my situation is not at all supported; really, I could just use a hint from somebody with more intimate knowledge of this software to help me figure out what's going on here.
I'm interning at a company that would like to use Cachet internally; however, this company has strict security rules and heavily customizes much of their software. As a result, I am required to use an internal version of apache and php to integrate Cachet into the corporate environment. I've already gotten it set up using php56 and httpd as a proof of concept, but I'm having difficulties getting it to work on our stack.
Environment
php version --> 5.6
apache version --> 2.4
rm -rf /bootstrap/cache/* --> Didn't help :(
The Problem
After a few tweaks, I've been mostly successful in my efforts; however, I have two problems whose solutions I can't seem to begin to figure out:
Tweaks Made
There may be other differences present, but the gist of it is that I have NO IDEA where to be looking; 2 weeks ago I'd never seen a line of PHP or apache configuration in my life, so I'm a little overwhelmed.
Expected behaviour
Expecting to be taken to the admin dashboard on login
Actual behaviour
Browser attempts to redirect to /auth/dashboard and hits a 404. Laravel logs say it gets stuck at authentication, at a line where it throws a 403 error, I believe due to invalid credentials. However, I've gotten this on 3 separate installations and I am 100% certain the credentials are valid.
Again, I get that this situation is totally unsupported since there's no way you guys can know what's different in my setup, but if I could even know where I should be looking to fix this it would be a great help.
The text was updated successfully, but these errors were encountered: