I am using grafana version 6.5.3 and I am trying to make a grafana dashboard be displayed in an iframe on a webpage in my blazor server app. The iframe is rendered but displays the following message "xxx.xxx.com refused to connect".
<iframe src="http://xxx.xxx.com/mygrafanacharts"
frameborder="0">
</iframe>
The Grafana server is configured with
allow_embedding = true
I have no clue if the Grafana server is not configured correctly or if there is some configuration that needs to be changed on my website.
I encountered the same problem and was sure, I changed the
allow_embedding = true
setting, but when I wanted to confirm this and looked under http://[yourGrafanaServer]/admin/settings
I saw, that it was still false.
When I opened the grafana.ini, I realized, that I had forgotten to remove the ; at the start of the line to uncomment the setting. After doing that, the iframe worked fine!
Maybe this was the issue here too.
Related
Facing ERR_CERT_COMMON_NAME_INVALID, while loading css and js files in chrome browser.
While loading login.aspx page related css and js files are loading in IE and Mozilla where as in chrome its not loading. We have deployed the existing application in new server, same application is working on different server. Is there any configuration to be modified in IIS? I have verified both the environment which looks identical, any specific related configuration is helpful. please find the screen shot below
Screen shot
ERR_CERT_COMMON_NAME_INVALID is a very popular SSL error during loading the website. In most cases, the issue is due to certificate misconfiguration on a server. However, it may appear due to antivirus and firewall or aother third-party extensions. so you can try the following methods to solve the problem.
Check date and time are proper
Your Chrome browser will show ERR_CERT_COMMON_NAME_INVALID error in case the date and time are wrong on your computer or mobile device. Please recheck and adjust it on your via PC settings.
Check browser extensions
In some cases, the problematic browser extension could be a reason for the error. First of all, try to open the website in Incognito window and if that solves the issue then no need to check extensions. Otherwise, follow the next steps:
1.Click the "three dots" button on the top right corner of your browser window
2.Select More tools and Extensions
3.Turn off extensions one by one to find culprit extension and delete it to fix the browser error.
Check Installed SSL certificate
In Chrome, you have to click to the "Not Secure" button located on the left side of the address bar, and then click to "Certificate". There you will see the details of SSL certificate using the field "issued to".
Clear the SSL cache
The browser's SSL cache can be an issue. You have to try clearing the cache to resolve the error. click "Three dots" button on the top right side of the browser, find the "Settings". There you will find "Advanced settings" at the bottom of a page. Now find "Open Proxy Settings" and there you will see the "Content" tab with "Clear SSL state"
i am surprised, domain stopped suddenly browsing and it shows default cgi page.
www.eddsp.gov.np not working properly. but sometimes its content page loads correctly like eddsp.gov.np/contact loads perfectly while cgi error comes in eddsp.gov.np | Again sometimes eddsp.gov.np/contact shows 404 error.
while if same site content loaded from subdomain
eddsp.imagingtrade.com.np
it works fine everytime and in every condition.
I came to know that it's caused by A record. Which are changing time to time. After talking with my DNS Providers. They had corrected it.
When I put into html file this code, it does not show website.
<iframe src="https://www.ge-tracker.com/names/claws">
Can somebody help?
It is because your target site to put into the iframe does not allow itself to be loaded into an iframe that is hosted on a a different domain. It uses the X-Frame-Options http header to advise this to any browser that requests it.
You can examine this by looking at the error console in your chosen browser.
For instance, using Chrome, you will see:
Refused to display 'https://www.ge-tracker.com/names/claws' in a frame because it set 'X-Frame-Options' to 'SAMEORIGIN, SAMEORIGIN'.
I have a test web page in Azure cloud where I have login page in https. My problem is that if I get to the login page via redirect, neither the CSS or images get loaded in WP7 default browser - IE. Certificate is a self signed one - so I get the warning from browser before getting to the actual page.
The strange thing is that if I just click on refresh button after the initial loading - CSS and images gets loaded OK. Also, if I go to the https login page directly without going through redirect - everything works OK again.
Server side is done with MVC3 and https redirect is done by adding [RequireHttps] attribute before the controller.
Fiddler logs do not show anything that would help me. In the redirect case I can see that after the html page has been loaded there is handshaking for getting the https tunnel up, but no requests for css or images. When I click refresh, Fiddler log seems to start the same way, but this time also CSS and image is loaded.
I have done quite a bit googling on this and none of the answers that I have found seem to help. CSS and image are loaded with relative links, so that should not be the issue. Directory access rights should be OK as well, because it works without redirect. It also works OK in Desktop IE and other mobile browsers that I have tried on.
Any help would be greatly appreciated.
Im trying to use the DotNetOpenAuth library for openid authentication.
I have used the default project template that they provide and have successfully run the setup.aspx.
Now the problem is that when i get redirected from myopenid site back to my site, i get a javascript error[object error] in LoginFrame.aspx and the window closes.
Is it because i am working on localhost (cassini server) although i have white listed localhost in the web.config.
I need help to get this working.
Thanks in advance.
If you are using IE, yes it may just be because you're using localhost. IE has a bug where redirects across zones screws up the javascripts. Try a different browser than IE when using localhost to see if that works for you. Once you go live, try IE again and it should work.