I'm new to divolte collecting. After installing divolte collector on wsl2 and starting the server on localhost:8290, I tried to access the server from a browser at http://127.0.0.1:8290/. I got "This site is inaccessible: 127.0.0.1 does not allow connection.". I thought the problem was with the port, so I added it to pare feu to autorise the connection, but it is still not working. I checked the devtools and I get "Request URL: http://localhost:8290/""strict-origin-when-cross-origin." from both chrome and firefox.
I'm really a bit stuck here.
enter image description here
enter image description here
Related
My application runs on localhost (both front-end and back-end, but on different ports). FE runs on http, but BE is on https.
All modern browsers allow adding exception so that https://localhost is accessible.
Except IE and Edge.
I've tried every option I have came across but none worked. I've added both http and https versions of localhost to Trusted Servers under "internet options". Did not work. I've checked host file, cleared cache, checked security options ...
What baffles me is that the request should be POST, but somehow the IE network panel shows it as GET. Other browsers send OPTIONS followed by POST, but IE fires GET and blocks it. It never hits the server.
What should I do to fix this?
And yes, unfortunately I DO HAVE TO support old IE, damn!
Whoa, solved by accident.
There is also Swagger running on my BE localhost. When I've tried to access it in IE, it showed warning about the invalid certificate. And only then was I able to install that certificate to IE, so that even IE would accept it.
So now when IE finally has the certificate, the request passed.
No usefull error message has been shown at all, so it took me considerable time to solve it. Damned IE.
Using Chrome, when I'm trying to change values of an input located in an IFrame of another app on our server, I get an error in Chrome:
"Blocked autofocusing on a form control in a cross-origin subframe."
On production (when the two apps are hosted on the same domain) it's working, but on localhost development I can't make it to work.
I've already tried starting Chrome with the following:
--disable-web-security
--ignore-certificate-errors
--disable-site-isolation-trials
--allow-external-pages
--disable-site-isolation-for-policy
but none worked.
Has anyone has an idea how to make it work?
If any change on server side needed, it's also an option.
For me the issue was a chrome extension ( Dashlane ). I disabled it on that site an it worked. I don't know if this helps you in any way but I had the same issue and this worked for me.
edit: I also had the issue on localhost however haven't tried it yet on server.
Go to chrome://flags
Disable SameSite by default cookies
Relaunch chrome
I have been using chrome to run my nodejs server.js file for the past couple days now and all of a sudden I'm getting ERR_CONNECTION_REFUSED on chrome. I've looked at other similar questions and everybody says to just type 127.0.0.1:port#. That didn't work. I also tried deleting localhost on chrome://net-internals/#hsts and restarting chrome to no avail. On the cmd line I'm getting 404 "not found" when I run my nodejs app. Using Windows 10. Any suggestion as to what is going on?
edit:
network tab
edit2:
cmd line
Please Give Code Snippet, and also your Browser's Developers tool Screenshot (Console and Network tab) so that we can better assert the problem.
Also are you making sure that your app isn't breaking while serving?
(Remember that browsers by-default send GET requests, so if your app is being route is being served at POST or any other route, it may not work).
When I try to visit http://www.taobao.com/ in Chrome I get taken to an ISP error page (http://hndnserror4.wo.com.cn:8080/issueunziped/hn20150626/index.htm?sf=&UserUrl=www.taobao.com). This doesn't happen in Firefox. I've trying clearing the DNS cache both system-wide and in Chrome.
How I can diagnose the issue?
Edit: I've simplified the question for the bounty. This problem happens on Arch Linux. I've tried using DNSCrypt. I've changed /etc/resolv.conf to use various DNS servers such as Google's. I've tried clearing the host cache from chrome://net-internals/#dns. I've disabled using a web service to help resolve navigation errors in Chrome's settings. Nothing works and every time I try to open taobao.com in Chrome I get the ISP error page. It opens the error page instantly without a redirect or waiting for the hostname to resolve. When I enter "taobao.com" into the address bar and hit enter with the Network tab open I see the first request is recorded as having a request URL of http://hndnserror4.wo.com.cn:8080/issueunziped/hn20150626/index.htm?sf=&UserUrl=www.taobao.com. How is "taobao.com" getting transformed into that between hitting enter and the page loading?
I've submitted a bug: https://code.google.com/p/chromium/issues/detail?id=510680&thanks=510680&ts=1437020912
I resolved the issue by clearing the browser data. Strange, but it worked. I went to Settings -> History -> Clear browsing data. With the defaults checked (clear following items from the past hour) it allowed me to visit http://taobao.com again. Creating a new profile didn't help. Nor did clearing the DNS cache from chrome://net-internals. I don't know if it's a bug in Chromium but I'm content to have resolved the issue.
I am new to Hadoop. Using Windows Server 20008 R2 and Oracle VirtualBox, I imported an image of Hortonworks Sandbox and on Login, when it asks for username and password, I gave root and hadoop (as mentioned in documentations) but it doesn't log in somehow. It gives this screen which look like command prompt or something:
The question is, what do I do next? The documentation says you open a browser and type the URL but there's no Linnux screen appearing, this command prompt is the only thing displayed. Please help.
EDIT:
When I open the URL 127.0.0.1:8888/ in the browser, its like this:
Does't give any URL in the description above.
Do an ifconfig and get the IP of your sandbox image.
Go to the browser and type http://IP_of_your_sandbox please ensure your sandbox gets a proper IP and not something like 127.0.0.1, if IP is 127.0.0.1 please check the network settings of your VM player.
On your browser you will be prompted to register the sandbox, post registration you will walk through a guided tutorial.
You can use either browser or terminal to execute the instructions.
Hope this helps.