I followed the tutorial for setting up simple authentication (http://book.cakephp.org/2.0/en/tutorials-and-examples/blog-auth-example/auth.html) and I am having issues with Internet Explorer 8 and Chrome. Whenever I try to login, it just keeps redirecting me to the login page. This only works in Firefox. Could this be a cookies issue? I am not sure how to troubleshoot this.
Edit:
I realized this only works in Firefox. I have added a line in the core.php file under the Config folder to disable the checkAgent and it still does not work.
I can't be sure that this is the same problem, but it may be useful in the future... have you checked the date on your host machine?
When a cookie has a bad date from an de-synchronized host machine (which happens frequently in my virtual machine environment), Chrome correctly rejects it, which causes the PHP session variables to be lost. Firefox is more lenient.
It's a simple fix, and it's caught me out more than once in the past!
App Controller sample:
https://github.com/hugodias/cakeStrap/blob/master/app/Controller/AppController.php
Users controller sample:
https://github.com/hugodias/cakeStrap/blob/master/app/Controller/UsersController.php
Users model sample:
https://github.com/hugodias/cakeStrap/blob/master/app/Model/User.php
Login form sample:
https://github.com/hugodias/cakeStrap/blob/master/app/View/Elements/form_login.ctp
Working in all browsers
After further investigation, it was an environmental issue. I was running my webserver/mysql database in an Ubuntu 11.04 virtual machine. I noticed very odd issues occurring. When I created a new virtual machine and loaded my project files, everything was functioning correctly. That was very bizarre.
Related
I am having a weird problem with my Laravel 5.5 app deployed on IIS.
The App has been running for 6 months with no problem, with people adding data into it.
Since yesterday (No changes on Code Side) when the people try to save a form the app just hangs, no error what so ever, even if I put debug mode On.
Now for the weird(er) part, this doesn't happen on all forms and only happens when using the app "over the internet”, When I Remote into the Server and use the App “locally” then The app works Fine with No Problems.
I suspect its a php.ini problem but cant be sure
Thanks.
I have a laravel project which is installed with laragon and I was working for few days nicely. Now after a sudden stop of my pc (because of electricity unavailability) I can no longer access the local site in chrome and it is forcing me to an https location. I then opened the site in mozila and it's working there perfectly.
Here what chrome shows as error
This site can’t provide a secure connection
school.dev sent an invalid response.
Try running Windows Network Diagnostics.
ERR_SSL_PROTOCOL_ERROR
What could be the reason and the solution for it?
Thanks in advance.
It has nothing to do with Laravel and everything to do with Chrome. They recently put a release that forces .dev, .app, and a few other TLDs to use HTTPS. The best fix is to use .local instead of another TLD.
src: Chromium transport_security_state_static.json changelog
I face similar issue yesterday, it took me lots of time to actually understand this issue but not to waste much of time, i decided to switch to other browser like Mozilla Firefox and use http instead of https to continue my work.
My magento website is not loading in chrome and firefox.It works fine in IE only. I cleared the chrome cache and history but it not display my website it shows like "This webpage is not available ERR_SSL_VERSION_OR_CIPHER_MISMATCH ". How to solve this error i am working on this issue for last 2 days.
That's nothing to do with your website as such, that's a server configuration issue.
Most likely your server is still trying to serve https requests using SSL3, which has been removed in Chrome 40 (and I guess firefox as well, but I don't have the changelogs to hand to check)
This is a good tool to check your SSL settings:
https://www.ssllabs.com/ssltest/
This will confirm any issues, and advise on fixes.
If you don't have full server access, then you'll need to speak to your host.
I am having a really difficult time trying to resolve a very mysterious issue, and I hope somebody can help. I am using Wordpress. I developed my own theme for Wordpress. I have used that theme for several sites in different hosting with no issue. It was working fine on this server I am having the issue with, but for a time now it is getting more common. I am getting a redirect loop error on Chrome ERR_TOO_MANY_REDIRECTS, but it seems to be working fine on Firefox. And sometimes it works fine on Chrome, but not on Firefox. I did the delete cookies and temp files and cache from my browser, and it worked for a moment, after a refresh on Chrome, the issue started again. Right now it is working on Firefox, but not on Chrome. So this is what I have tried:
Check .htaccess file. I deleted it and re-saved Permanent link settings to recreate .htaccess file. Did not work.
Modified the site_url and home values in the database from domain.com to www.domain.com and http://www.domain.com and http://domain.com and did not work.
Disabled all plugins, even moved all them to a different folder. Did not work.
Since I am using my custom theme, I disabled my theme and enabled the Wordpress default theme, and did not work.
Checked permission for a couple of folders. They were all fine.
Checked with the Chrome Inspector, and I see a lot of 302 Moved Temporarily.
Now, I am out of ideas, and I cannot find any scenario that matches mine. I am not sure if it is related to cache or cookies, or permissions on certain folder, or I don't know. I believe it is something related to cookies and permission, but I cannot find any help on how this works on Wordpress and I am not even sure it is the issue.
The other thing, is this is a Linux Server with Apache. So I dont know if it may be a Apache configuration issue or something with the server CPANEL or something. I only have access via FTP to the root folder of my Wordpress installation, access to the database via PHPMYADMIN and access to the Wordpress administrator. I need to make sure there is nothing else that can cause this issue in Wordpress and a way to prove if the issue is related to the Apache configuration or server related. I am very frustrated right now, since I am out of ideas and did my best to fix this. I really do appreciate if someone has an idea of what else can be done.
I have encountered this same problem recently and what was causing it in my case was a new 'feature' in an updated version of Plesk control panel. Plesk now automatically does a 301 redirect to the preferred domain. Now if the preferred domain in Plesk and WordPress are different or you have conflicting redirection set in your .htaccess file this could result in a redirect loop. The solution is to either change the preferred domain in Plesk or disable the redirect altogether. You mentioned that you are using Cpanel - I'm not sure if Cpanel has this wonderful 'feature' but it's another possible cause to eliminate.
I know this kind of thing cannot be adequately answered without a link to the live example. Unfortunately, I can't set one up right now as it's a back-end login and creating a safe public login would be too much to do at this point. Sorry. I'm hoping for ideas and input from people who may have experienced something similar in the past.
I am setting up a CMS for a client with a DSL connection in Spain.
The CMS is hosted on a straightforward standard, LAMP based, shared hosting package in a network center in Germany.
It comes with a .com domain.
When my client tries to log in to the CMS using Internet Explorer 7, everything works fine.
When she tries to log in using Firefox, she gets to the login form, submits it - and then the connection times out.
When she logs in using Firefox but using "domain.com" instead of "www.domain.com", everything works fine.
This happens on all computers that are hooked up to that line. One Windows XP, one Windows Vista.
The front-end part of the site, as well as a second, older CMS, work fine in all browsers.
I do not have access to the raw access logs.
I have not been able to reproduce this behaviour on any other connection.
Debugging ideas are welcome. Remote diagnosis is extremely difficult as the line is too slow to set up a proper remote connection.
If you are limited by how you can troubleshoot this, have the client install Fiddler - Web debugging proxy and then run the trace, and send you the logs, Fiddler will analyze the traffic (be it proxy or DNS timeout, etc)
Take a look if you have not used it before:
http://www.fiddler2.com/Fiddler2/version.asp
Check that Firefox and IE are using the same proxy settings.
DNS issues? can you put here your A records to check is everything is ok?