Investigating Unknown Network Error in Firefox - firefox

There is something weird happening on the website of the company I'm working for.
On both Firefox and Firebug console log, I get an unknown network error.
There is no code reference for the error, and I can't track it on other browsers.
However, it's there, and I don't know how to solve it, nor what it is.
Other sites with the same theme, same domain registrar and on the same server work just fine, showing no problems at all.
What the heck is that??

It seems that the latest update of Contact Form 7 Plug-in solved the problem!

Related

what is this error "An unexpected error occurred. Please try again later. (8869003)"

i am unable to publish any apps on my Google Play Developer account is says
An unexpected error occurred. Please try again later. (8869003)
can anyone please help me to get out of this?
Had same issue today.
In my case I had to logout and login.
Then everything worked.
In used incognito window and worked. Clearing cookies, cache might also work
It happens due to conflict between chrome signed in account and google console signed in account, signing out from console and resigning in will solve the conflict. Solaza suggested the same solution
I ran into a similar Android Developer Console Issue today.
I was trying to promote a Closed Testing Track (Beta) to Production.
I always got the following error (with random error codes):
An unexpected error has occurred. Please try again. (Random-Error-Code)
The solution was to create the new release by hand in the Production Track, rather than promoting up the existing Closed Testing Track.
This happened to me as well. It could have been because I changed my account email on the same day. I got it working the next day.
Things to try:
Use a different computer.
You have to select at least one country from the list of countries to test.
Give it 24 hours for Google to refresh your email change, and try again.
If nothing works, contact Google Play Console Customer Support, they have a chat window.
I faced this issue when update my developer profile on google play developer account. There is a featured app selection at the end of the page. I selected an app that is not published yet, caused the problem.
I didn't select that app as featured and it worked.
in my case it's due to the network issues that my laptop by default will use our company's system proxy, I guess it'll go through some internal firewalls before reach the outside world, the latency caused the error, i switched to no proxy mode, then everything working fine

500 error on local Laragon website

I usually don't have any problem with Laragon as it works pretty good. I had no problem using Laravel.
But recently, my laptop made a Windows update, and since it restarted, nothing works anymore.
By nothing, I mean that when I try to load my virtual host "foo.dev", I have a 500 error without any info. So I tried the old way by going on localhost/www/foo/public and it loaded my website. Great !
But new bad news, impossible to connect to the database, even using a software, as if the password had been changed...
I don't have any idea on how to fix these problems and where does the problem comes from...So I'm asking for your help, if anyone has already faced a similar problem and reached to solve it.
Thank you.
I guess when updated your windows, Chrom also updated and apparently Chrome made new release that forces .dev, .app, and a few other TLDs to use HTTPS. The best fix is to use .local instead of another TLD.
see this question for more info

Laravel 'Whoops, something went wrong'

I've created a Laravel booking application that is currently being used in schools. When I test the live (production) version of the website on my own machine, the application works fine.
However, some schools are reporting that they are not even able to see the initial login screen, and are getting the Laravel 'Whoops, something went wrong' screen. I can confirm that the school firewall is not causing the issue, and that the website has worked ok in the past.
What reasons could there be for the same code to work on my machine but not on the live version? So far I have tried resetting the browser cache, and also flushed the DNS but to no avail...
Any suggestion are welcome.
Thanks.
It seems like folder permissions problem.
As the error is not shown, nobody can really help you..
What I suggest, is first to check the log file (storage/logs/laravel***.log).
There you should be able normally to see the problem and then you can fix it.
Another solution, in your ".env" file, switch from production to development mode, so you can be able to see the exception.
Check capitialization on the view name. I've had issues where everything works fine locally, but then get not found issues when live as the server behaves differently and is case sensitive.

Codekit with Ampps browser refreshing not working

Was hoping if someone could help me figure this out. When I click on "preview" in codekit I get
"Unable to preview
CodeKit's internal server is not running. Various network issues can cause this, including certain VPNs. Disable any VPNs and/or reboot your Mac and try again"
If I turn off the servers in Ampps, codekit attempts to but I just get an error since Ampps isn't running to serve the page.
Any ideas on what to do? I've been goig through all the settings in Ampps trying to find something, but I'm coming up empty.
Thanks in advance
Sorry. It was a firewall causing the issue. TCP block to be specific. I disabled it and all was good.

Site throwing error and crashing in IE 8

I am having an issue with a site I am working on throwing an error in IE 8. My client is reporting that anytime they go to the site and click on anything an error is then caused forcing the site to crash. This only seems to be happening in IE 8. I am on a mac and run windows only through boot camp. I cannot seem to replicate the problem, or debug it. I'm hoping someone here can replicate the error and advise me how to fix it. Here's a link to the site. http://www.eacpds.com Any help would be greatly appreciated. Thank You!
Moving respond.js to the footer seems to have done the trick if anyone else is having a similar issue.

Resources