So I am experiencing this frustrating issue for quite some time already. The scenario is when I am using admin panel, it will automatically log me out frequently(especially when I click on Save or Edit button). Sometimes it was as bad as each action click it will log me out once, so I have to repeatedly login for each action I performed( Save or Edit).
It is even worst that this is not a constant issue which means it is not every time I click on this module will have this issue which makes me impossible to trace under what circumstances this issue will comes out. By the way, after the system log me out, the message appeared at the login page was 'Invalid session token'.
And recently I got feedback from my customer that even front end is having this issue. My customer make an order after filling up all the details and confirm the payment, when try to click next button, he is being logout !! No order confirmation email send to him. And when he re-login to his account, his order details is incorrect(showing other customer details). This has seriously impact my website reputation. I believe both these front end and backend issue were from the same root cause.
All this while I have been trying to look for solution for this, I have seen similar post on Opencart forum before but can't get a solid solution. So I am opening this topic again here and hope to get a solution from stackoverflow. Solid solutions/advise/idea are all welcome. Thank you.
You may check at following things,
delete system/logs/error.txt;
check if problem has gone;
if not - check where is your disk_space (you may contact your hoster for support)
I also had the same issue.
I have changed the string of code in the htaccess file from "http" to "https" and that worked for me.
Related
Is anyone else having this issue with Heroku?
Something went wrong. If you're using an ad-blocker, please try disabling it. You can also check the Heroku Status site to see if there are any incidents impacting our service.
And in the top corner shows Unknown error
Screenshot of the issue
I was using my dashboard normally until 2 days ago, then I started getting this splash and even disabling my adblocker this still remains. And in Firefox I get an eternal loading page (after authentication).
I'm pretty new using Heroku, but it seems that a free user just can't create a ticket or email them anyway... LOL
I'm being able to do what I need through terminal/cmd by now, but eventually a dashboard would be great!
One possibility is that the site is experiencing some sort of problem. It is the website itself and not you.
You can check in Status to see if there is a real problem reporting (but if the problem just happened, it may not happen so quickly)
I suggest that if you really have a question, you write an email to ask.
outage-support#heroku.com
Their reply is very fast (my experience is that they reply after 2 minutes), here is their reply
We're seeing similar reports and looking into this, possibly an incident brewing. We should have a status post shortly: https://status.heroku.com/.
I am in the process of building a shop on wordpress using woocommerce. All is well except that at checkout there is an endless spinning wheel blocking the payment processing.
I have checked the error logs - which show no errors
I have disabled all plug ins - which makes no difference
I have reverted to the default woocommerce shopfront theme - which has the same result.
The console shows no errors.
I have also followed the instructions here https://docs.woocommerce.com/document/endless-loadingspinner-on-the-checkout-page/ which assumes its a memory limit issue. This did not work.
So, after a bit of digging I found some reference here https://mikejolley.com/2015/11/12/debugging-unexpected-token-in-woocommerce-2-4/ and here https://www.maxsangster.com/blog/woocommerce-endless-loading-spinner-on-checkout/
Referring to these two pages I have been able to see that the json response from /?wc-ajax=checkout is just returning HTML which I would imagine is where the issue is.
However I am running an Apache server rather than Nginx as has been mentioned in some threads and articles. Assuming there is a server misconfiguration of the server or something that needs changing what might that be? Bearing in mind that I do not have direct access to this, so will need to be asking someone else to sort it out for me.
And finally if there is something else I can try what might that be?
Thank you to #plushyObject for generating the spark for this one.
The issue turned out that I had a legacy static html holding page in place as the site's homepage rather than having one set up with wordpress. Simply removing the .html page and letting wordpress's homepage take over solves the problem.
The moral of the story create your holding page in wordpress.
Go to Google Developer Tools, then Go to the Network tab. Click the button and make the request and let that bad boy spin out.
You mentioned the response is returning HTML. Click on the request that goes out that appears to be taking forever (/?wc-ajax=checkout) and then click on the Preview tab to display that HTML. I bet it shows an error or a clue, anyway.
In my case the checkout was working fine on Desktop but not on Mobile. After many search on internet I read the solution of #UntitledGraphic.
I had set a redirect in ht-access. The redirect was showing a different home page for mobile. When I removed it, the error gone. I checked back & forth and was sure the ht-access redirect was the problem.
If you have set any redirect in the Htaccess then remove it. This will solve your issue in this case.
I also checked the redirect code on function.php instead of htaccess again the problem appeared. So finally removed the redirection.
In my own case the redirection was the issue. So I had to delete the redirect I created via Cpanel.
I'm at the end of my rope here and I'm here to get some help. I'm going to try and explain it as best as I can.
I have a website running on Joomla 3.7.2 which you can visit here: https://www.meteordesign.nl
For some reason my contact form does not work anymore. Whenever I click 'send' the page reloads but no confirmation or an email being sent.
I have tried the following:
Switched from PHP mail to SMTP and send a test mail (came in fine).
Used several other contact form modules and components and even an HTML one which you can find here https://bootstrapious.com/p/bootstrap-recaptcha
They all don't work. I have tried disabling my .htaccess file to see if that solved it but to no avail.
You can find the contact form here:
https://www.meteordesign.nl/contact
I don't know if this is important but recently my hosting provider switched to https. Could that be causing it?
I hope I explained it well. If not feel free to ask me more questions, I really need your help fixing this!
So I finally figured it out...
The problem was the cache settings on Joomla at Global configuration > System > System Cache. I had it on Progressive and after setting it to Conservative my contact form worked again!
You are likely running into a JavaScript issue. Just tested this and you seem that you have solved it. Please let us know what the issue was so that others can learn from your experience.
This is a very strange one for me and I've been battling with it for a while now. I really hope someone can help.
I have a fairly typical MVC 3 Website and I only seem to be getting this problem in IE and Firefox. Chrome plays along nicely. Lucky for me, the majority of our company's clients uses Chrome at the moment.
Problem is at a seemingly random point in time, the browser will automatically redirect me to the Account/LogOff action when I click on a link, and from there it will obviously go back to the Login page. This link will then continue with the same behavior.
I say "seemingly random" because today that link will work, tomorrow it won't and all other (or the majority - I have never had more than on problem link giving this problem at a time) links will be fine. Sometimes restarting the server/dev environment will take care of the problem, other times it won't. The browser will just keep redirecting to LogOff.
I have tried looking at the Referrer URL, but the controller/action being referred to will never be reached. (If I place a breakpoint in the action, it is missed and the next point reached would be the LogOff action)
If I look at the stacktrace when in the LogOff Action, I can't see any info from where the application has come from. I have also tried what was suggested in this page: Posting the Stack Trace on ASP.NET MVC, but I cannot see why I am being redirected to the LogOff action.
The only place I seem to be able to have a breakpoint get hit before hitting LogOff, is Application_BeginRequest in the Global.asax, but can't see where it is going from there on.
My guess is that somewhere along the line, ASPNET Auth decides the user isn't authenticated any more and redirects to the LogOff action. Problem is that the cookies associated with ASPNET Auth all still exist, have data in them and they haven't expired yet.
Anyway, I hope I have given enough info on the problem.
Thanks in advance.
[Edit]
OK, so I might have gotten a step closer. I came across this link and looked to see what is happening in my Application_AuthenticateRequest in my global.asax.
I am not quite sure why, by when I click on a link, Application_AuthenticateRequest gets accessed 3 times. When a link works (as in I can follow it and it doesn't log me out), the value of the .ASPAUTH cookie stays the same. I checked this by adding a breakpoint and a watch over
HttpContext.Current.Request.Cookies[".ASPXAUTH"].Value
When the link does not work, the first time the cookie has a value, then the other two times it is null. Thus, because the ASPXAUTH cookie is null, the system automatically redirects to the LogOut action.
If I consider the solution they posted in the link, I am not sure if this applies to me. As far as I can tell, the encrypted cookie is still small (as in a few hundred characters long) and not close to 4096 bytes. Also, I have only 3 cookies going at the time I when tested the broken link and I have a maximum of 5 cookies at any given time.
Any idea?
OK, so I had a hunch about cookies expiring. So I looked at whether there is a way to keep (force) cookies in Forms Authentication alive and that led me to http://www.codeproject.com/Articles/221889/How-to-Generate-Machine-Key-in-IIS7
The only way I could test this theory was to keep working and debugging the site as normal. (And that's why it took me so long to post this answer.) Since I introduced this solution it seems that the problem has been solved.
Interestingly I spoke an Architect the other day, with 20 years dev experience, about my problem. He looked at my code and is convinced this is a bug in the Forms Authentication code.
I hope this helps some people who are experiencing the same problem I have.
We are having an issue with logging in a second time on our site ever since we installed the lightspeed module. At first I thought this might have to do with the need for hole punching, but now I'm not sure.
If you try to log into our website the first time, it works well. However, if you log in a second time, it won't work. It just remains on the customer/account/login page with no effect.
I tried to test this on my end, and echoed the user's email in the loginPost function in the account controller. When echoing directly from the controller, it was obvious that the user was being logged in, but upon the redirect to a page on the site, the user was no longer logged in and appeared as a Guest in the Magento backend (where you view online customers).
It appears to me as if the session is being lost after the redirect. I am not sure if this has anything to do with a switch between https and http as described in the stackoverflow problem here (http://stackoverflow.com/questions/7823994/magento-session-lost-when-switching-to-https-from-http ) where they had also installed lightspeed. The person there resolved the problem, but did not post the solution. Their problem wasn't the same as ours, but I was thinking there may be a connection between the two.
Has anyone seen a problem like this before?
Thanks in advance,
Brenda