When running any suite or single test I don't see the page in browser refreshed or with any progress. Tried in chrome and ie.
The suite runs ok, I can see it by the logs.
What can be the reason of this behavior?
The problem was that fiddler web debugger ate the traffic from fitnesse to browser.
Have you tried running FitNesse on a different port? We experienced a similar problem and it was fixed by switching to another port number. Strange, but we suspect some kind of corporate software.
Related
PageSpeed Insights (https://pagespeed.web.dev/) is no longer working on my PC. It just spins. I've tried using multiple different URL's to analyze. I've tried it in Incognito. I've cleared cache. I've reinstalled Chrome. I've even tried it with the Edge Browser.
This seems to correspond to the new Pagespeed Insights Release. I've never had a problem with this until recently. This has always worked before.
I don't know if it's a cookie issue, or the new PageSpeed Insights release, maybe a new firewall issue that cropped up. Or, does it now require a KEY or something? Or, could my IP have gotten blocked by Google for this?
Note: I can run Lighthouse from Inspect. That works. But not https://pagespeed.web.dev/
Windows - Chrome is up to date Version 96.0.4664.45 (Official Build) (64-bit)
I'm baffled. It's probably something obvious but I can't figure it out.
Any ideas out there?
Thanks,
Bob
For us, the lighthouse report in Chrome dev tools is not working behind a VPN. It was working earlier. Not sure what is the issue.
We were looking to test new page templates on the dev environment. Unfortunately, the PSI is not warming on staging on a VPN
EDIT This issue seems to only affect Chrome and Safari on my Macbook Pro. I can't replicate this issue on other computers and browsers. I thought it might have been malware or virus, so I reformatted my Macbook. Didn't fix the issue All of a sudden, I am running into this issue when developing on my local server as well with MAMP. Assets are missing everywhere and some pages fail to load all together
I've noticed recently when I refresh my Vue SPA with the cache disabled, the page tends to look messed up with missing images/resources.
When I check the console, I see a lot of ERR_CONNECTION_REFUSED for resources that are definitely there. If I refresh the page, the errors go away. It tends to happen after I clear cache and load up the webpage for the first time, or if I disable cache in the developer console.
It turns out there had recently been a DDos attack against my IP address so my hosting service forced rate limit connections to my IP address. So if you ever run into the same issues, check with your hosting company first.
my website opens with xx.xxx.xxx.xxx IP address till friday it was working fine..after wards not able view the site in webbrowser...what could be the problem ? how can we solve it?
My server with this IP is working and can able to view the updated data in database ..but not able to view, or open the page of website.before the website under IIS configuration was stooped and now started again..still no use..am couldnt view Login page at all.My application was developed in classic asp long back.Kindly give me any suggestion to this...its very urgent...
I tried browsing the website in IIS manger(server) .It showing page cannot be displayed.
Thanks in advance.
First, Don't Panic. Staying calm can avoid further damage.
While it's hard to tell what could be the problem, the first thing you can do is to "ping" the domain from terminal.Can you login remotely? "wget" (on linux) will download the files from website, and could help you see if the files on the site are still accessible. Check from different browsers or machines, if possible. I'm no expert in asp or IIS, so won't advice on that front. But once I had faced the same situation with my website. So I just called up the hosting service provider, and it turned out it was their problem, and they brought the server online. If it's okay from their end, you might have changed some configurations in your server or application or there might be some up-gradation changing parameters, or even an accidental deletion/ moving/ renaming of files. Just try to remember what are the things you did with your server and application, before it went down, and also ask your server administrator. That will surely help you understand the problem better, if not help to solve it right away.
Good Luck.
I'm developing a cross-platform NPAPI+XPCOM extension for Firefox and Google Chrome (Windows, Linux and Mac). I was wondering if anyone could enlighten me on the best practices of handling component crashes.
As I understand it, currently Mozilla's Crash Reporter submits mini-dumps and crash reports created to Mozilla Dev. I experimented with blocking SIGSEV to Firefox and creating my own core in the plugin code. Although that works just fine, I'm sure I'm not supposed to do that.
And Google Chrome doesn't even seem to create any core dumps! Any suggestions?
The firefox crash report database is publicly searchable, so you don't have to do your own handling. If you ask nicely (i.e. prove you're the plugin author) I'm sure they'll even give you the minidumps from your plugin's crashes.
This is awfully late, but yeah, don't do that. You will wind up catching a lot of things that aren't just your plugin, and you will screw up our crash stats. You should be able to find your plugin crashes in our crash report site. If you need better reporting, you can file a bug on us and we should be able to help you.
I am getting into strange situation regarding the RSS viewer on SharePoint
I have two environments of SharePoint (production & testing)
I was showing a specific RSS news (ABC) on both of them , and it was working after setting the proxies and other stuff.
Suddenly (may be due to some changes done on the production without testing), the RSS viewer on the production is not showing the RSS news it is showing protocol error, while it is still working fine on the testing environment.
Now the strange part is if I change the RSS of the one our management wants and put BBC or CNN news these works well on both the production and the test environment.
But the one we want it to work (which was working fine on both) do not work on the production and works fine on testing.
Any suggestions of how can I figure it out?
Sounds like a network problem. If the logs don't show anything more helpful for the protocol error I would try wireshark and see if you can see anything different bettween test and production.
Can you show us the error you're getting? And, can your firewall be not well configured and the abc news be rejected?