Hello!
I made a screen and placed a trigger overview resource on it. And right now I don't see a green (OK) triggers, only problems. Before the Zabbix update 4.0.3 it worked well.
Screenshot of how it works now
Is possible to make it now?
Right now it happens because of bug. Here is the link to Zabbix bug tracker
https://support.zabbix.com/browse/ZBX-15386
Related
I am new to coding.Have got a few line of code i am working on and anytime time i try to open it with a live server i encounter a problem as shown in the image. I have tried to solve the issue with by looking it up on Google but could not. I need you all to come to my rescue as soon as possible. Thanks
I expected the code to run smoothly on live server but it would not.
For some time now, I'm not able to use the "copy as curl command" anymore. It's just an empty context menu, please see attached screenshot. Anyone else experienced the same issue?
I'm running chrome 90.0.4430.30 on a mac
Seems to be working fine for me on version 89.0.4389.90. I'm guessing that since version 90 is relatively new it has some bugs. Perhaps try downgrading back to the previous version or try reaching out to Google Support.
I've been trying to create a new collection at https://console.cloud.google.com/firestore/data?project={PROJECT} however when I do, nothing happens. Opening the dev tools and looking at the Networking tab shows the requests are not going through (see screenshot). I'm using Chrome 83.0.4103.97 on OSX 10.15.4 (19E287). I have tried to go to Site Settings and change unsafe content to Allow, however that did not make a difference.
Anybody got any idea how I could make it work?
#Alice and #Frank resolved it however I think this is worth creating an answer.
In such situation first thing to check if incognito window is behaving the same way. There might be some extension that are blocking request.
In this situation there was "Disconnect" extension which was blocking.
I hope it will help someone in future!
We have a site that is not working in Google Chrome V44. It works well in IE and Firefox. All of sudden after updating chrome browser to V44, we unable to login to the system and just receiving this problem.
We're trying to figure out as why this is happening. We have 2 instances of our system in our server. Our live site is the one that is not working in Chrome V44 while the other - our demo site is fine. The only difference of the these sites is that our live has SSL. So our first impression is that there's a problem with Chrome V44 with our site with certificate.
I think Chrome can't establish secure connection with the site.
Has anyone experienced this issue?
Please help. Thanks.
This is due to a SSL in Chrome V44 where it incorrectly sends a HTTP_HTTPS header to be set, however the HTTPS header is still set correctly. It has been quite widely reported: http://www.zdnet.com/article/brand-new-chrome-44-release-added-a-bug/
https://ma.ttias.be/chrome-44-sending-https-header-by-mistake-breaking-web-applications-everywhere/
In order to stop this, in PHP, I added the following to the very top of my index.php file:
<?php
if (!isset($_SERVER['HTTPS'])) {
$_SERVER['HTTP_HTTPS'] = 0;
}
?>
Ensuring there is no space between the ?> and the next
I've recently had the chrome redirect loop on gmail.
Possibly significantly, I was doing some work involving changing my system time and it hasn't worked since. This guide helped to do that.
There is an available work-around, which is to use gmail in incognito mode, which does still work, although requires you to log in each time
In that case I would say this is an internal problem with you organization's setup. I would speak with your SysAdmin or IT staff. But just to be sure, use your phone carrier's internet, or a cafe nearby, basically something off your network to check if you can reproduce the error.
The issue with my MVC solution was, i had recently updated complete Nuget packages in my solution. After the update i forgot to update
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
section with new dll bindings which installed while update. So in my hosting server due to connectionstring issue, i was not overwriting the current .config file. So once i did the update in assemblyBinding section in .config file the issue gone.
There might be many reasons for the redirect loop. If you are confident your setup is done properly without any errors, then it might be the issue with your browser. You can try the following
Deleting cache and cookies
Correcting your system time (if it is not set to automatic)
Resetting the browser
Source
You should be able to fix this problem, you can try to clear your cookies in your browser
Open your Chrome browser.
Type "chrome://settings/clearBrowserData" in the address bar and press Enter.
Make sure you are clearing items from the Beginning of time. Then select Cookies and other site data. Click the Clear browsing data button.
If find from google search, this tutorial could helps you https://windows10freeapps.com/fix-err_too_many_redirects-error-google-chrome-browser
I used "chrome://inspect" for a few days. Everything was fine. Today, for some reason, when I click "inspect" the result is "404 Not Found The resource could not be found."
What could be the reason for this ?
I was able to find only this topic: https://code.google.com/p/chromium/issues/detail?id=329979
I guess the drivers are OK if the device appears ? I`m able to transfer files, to "focus tab" or "close tab" and "reload" but i can't "inspect".
Chrome Version: 37.0.2062.124 m
DevTools URL : chrome-devtools://devtools/remote/serve_rev/#180870/devtools.html?&remoteFrontend=true&dockSide=undocked&toolbarColor=rgba(230,230,230,1)&textColor=rgba(0,0,0,1)
Edit:
I tink this comment is important so...
A bug was opened in the Google tracker: Link Please star it! Remember that you don't have to add a comment to it if you don't have new information :)
by MM
Edit 2:
DevTools are actually broken for ANY kind of Android devices, regardless device's version, Chrome version or OS. URLs of such kinds - http://chrome-devtools-frontend.appspot.com/serve_rev/#180870/devtools.html - that must return DevTools code - now returns 404. That could be fixed by Google without any change in the Chrome code, it's completely server-side problem.
by vrid...#gmail.com at bug tracker
Edit 3: At this time http://chrome-devtools-frontend.appspot.com/serve_rev/#180870/devtools.html is OK but slow. I realy cant get why I need usb driver to send data over the internet... to this page just to debug.
I had the same problem, but it was caused by chosen AOSP WebView instead of Chrome Stable at Developer Options > WebView Implementation. If you do not have Chrome Stable option available, then try to install Chrome and check again.
Just had the same issue. VPN was on, turnning it off fixed it.
That was a cloud storage glitch. Things have reverted to normal since then.
After updating chrome version on Android device worked for me.
This still occurs and workaround is to open chrome://inspect and click on inspect link under Remote target assuming the command node --inspect server.js is already hit.
Workaround:
disable chrome updates. Instructions: https://www.makeuseof.com/tag/stop-automatic-chrome-updates-windows/
uninstall latest Chrome on desktop.
install previous version: (I used slimjet: https://www.slimjet.com/chrome/google-chrome-old-version.php)
Open chrome://inspect/#devices url and choose inspect-fallback instead of inspect.