Ok so this may be a dumb question or possibly something that just isn't supported but haven't had much luck finding an answer.
I'm testing out Light Table for use as my day to front end editor and have been trying to get a page loading in the internal browser without success. I have a weblogic server running my app which I can access from Chrome and other browsers but when I try to point Light Table's browser at the same url I get the generic proxy can't connect to destination.
My first thought was that this I needed to configure Light Table to work with the company proxy but I am able to get to other sites from light table using the built in browser and I have the env variables http/https_proxy set. Has anyone seen this issue or know of a fix/workaround?
Ubuntu 14.04
Light Table 0.7.0
Chrome 36.0.1985.125
It's weird but sounds "reasonable" that you don't really need any proxy to access localhost. I'd check using 127.0.0.1 in your url rather than localhost if you already didn't.
I recall a weird issue probably unrelated on Ubuntu that prevented the right name resolution. The resume is to check that /etc/hosts should contain just 127.0.0.1 localhost rather than your_machine_name 127.0.0.1
lein repl error:Connection refused
Related
I am developing a website using Roots.io stack (Trellis + Bedrock + Sage).
I am working, locally, on several sites and they're all working fine. Until today I reboot my computer > execute vagrant up > attempt to access the local development URL https://mysite.dev > but suddenly get an error, in Chrome, stating "NET::ERR_CERT_AUTHORITY_INVALID".
Normally, I do get a similar error, but I have the option to dismiss it. But now I do not.
Via BrowserSync, I can access the site via localhost:3000 but not using the development URL.
If you're familiar with Roots, you know that Trellis generates the SSL locally as self-signed in an automated process. So I know very little about how it works outside of their documentation.
I understand that this issue seems to be a mix-match with the SSL certificates locally, but I don't really know how to troubleshoot that. I'm thinking there is a file locally that needs to be deleted and replaced. But I don't know how to generate a replacement if that's the case.
I have spent about an hour reading any articles I could find on the topic but none seem to really explain precisely what's going on in a way I can apply.
Update: Ultimately I'm looking for a way to add an exception for the ticket in Chrome. I was able to do it in Firefox and it's working there.
Thank you.
Short Answer: Don't use .dev extensions in your local URLs as this is now a real domain name extension no longer reserved for localhost.
Long Answer: https://ma.ttias.be/chrome-force-dev-domains-https-via-preloaded-hsts/
You can either
Import this certificate using Chrome's Options > Manage Certificates > Import
Or simply ignore SSL errors launching chrome with args --ignore-certificate-errors like /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --ignore-certificate-errors &> /dev/null & (not recommended).
I can't figure it out for the life of me.
I have a laptop (Macbook Pro) that I'm using as a web server to develop Wordpress websites. MAMP Pro 3.0.5 is running on it to serve the sites. As well, I'm also using Squidman 3.3.9 as proxy so I can connect to the laptop with other machines or other devices (phones, tablets, etc.). Everything was working fine for a good long time, which has been since I set the whole thing up a few months back. Fast forward to today, and stuff's somehow busted.
Viewing sites from the laptop (which is where it's all hosted) all sites load and function perfectly fine. However when I try to connect to any of my host entries in MAMP from my desktop machine or whatever remotely, I get bizarre urls returned. Below is exactly what winds up in the browser's address bar when trying to navigate to "examplesite.com":
examplesite.comhttp/examplesite.com/
Character per character, that's exactly how it gets returned. The URL not only gets doubled, but there's a colon missing and forward slash missing.
Another funny thing is that when I go to the wordpress back-end for any of these sites, I can reach it just fine. So, at the same time as having busted root URLs, this somehow still works when I try to connect from a remote machine:
examplesite.com/wp-admin
Additional note: Even with static sites that are just stand-alone files (and not wordpress installations) I still get the same problem with the doubled-up, mangled URL. It appears to happen only when try to connect through a MAMP host address entry.
Anyone have any idea what could be going on? Again, everything used to work fine previously. Now, for some reason, it doesn't.
Many thanks in advance,
-- MP
Ok, figured it out. On the device or machine that I was connecting to the proxy with, there was no port number specified.
(I guess that with no port number declared (to match the HTTP port specified in squid) somehow there was a double lookup that was going on. Maybe once when the root was hit, and then a second time when the port number was looked up. Perhaps? I'm still not totally clear why the ":" and the "/" were removed from the address though. Perhaps the slash or the colon are somehow escaping themselves.)
I've searched around and found a lot of advice saying to modify the hosts file as such:
127.0.0.1 mydomainname.com
I've done that, but my actual site at mydomainname.com is still being used. Any other troubleshooting steps I could take? Any other suggestions?
Restart your browser, try ipconfig /flushdns (I'm a bit hazy on Windows DNS caching so that may or may not help here) or restart your computer. Unless you've done something really weird, the hosts file should have priority, so something must be caching the DNS result.
simply setup your canvas address as localhost. Unless you're using FBML, it works. See http://fbgraph.computerbeacon.net/tutorial/section1/createnewapp.aspx for an example.
Just make your redirect_uri your localhost address like:
https://graph.facebook.com/oauth/authorize?client_id={consumerKey}&redirect_uri=http://localhost:4403/Handshake
I have mine set up in visual studio to switch between localhost and live return_url's depending on whether debug or release is selected
I used to run web applications all the time on my laptop, no problems, I am using VWD 2008 Express, i have the latest framework, Windows Vista Home Basic...etc..
Now, when ever i try to run a website, or even chose to Show a Page in Browser from Within VWD, the browser (both IE and Firefox) keeps looking for www.localhost.com...
I tried to copy the address of and paste it directly in the title bar, nothing, same problem i tried to get that address from the balloon notification (the one that pops up when you run any ASP.net project), still nothing happens...
My colleague is facing the same problem, but for him, he can simply copy and paste the url in the address bar, but its not working with me....Heeeeeellllllllllllllllp
Check your hosts file, it should be redirecting localhost to 127.0.0.1 and nothing else. The entry that will cause this error should look like this:
127.0.0.1 www.localhost.com
If you find this, remove it or change www.localhost.com to localhost.
You can also try to post one of these in the adress bar:
127.0.0.1
http://localhost
Note that the hosts file is a popular victim of viruses, so if is has been modified, you might run a check on viruses.
Also see the discussion here.
If that also doesn't work, open up nod32 (you probably have it installed on your system if the above methods don't work) go to advanced setup, on the left menu, select protocol filtering, and select HTTP and POP3 ports... ;)
I got the same problem in firefox 3.6 when my server was down.
In my case it was not a problem with etc/hosts where the line
127.0.0.1 localhost
was there and OK.
The solution that worked for me was to disable the "cleaver" URL fixing that Firefox carry out when the page is not found. The procedure taken from here:
Type about:config in the address bar and hit return.
find browser.fixup.alternate.enabled
double click the “true” value. The line will become bold, and the
value will change to “false”
This fix directly the problem. No firefox restart needed. If your server is down you get "page not found" as expected.
Hope it helps.
Thank you for your solution ... this works fine...
I got the same problem in firefox 3.6
when my server was down. In my case it
was not a problem with etc/hosts where
the line
127.0.0.1 localhost
was there and OK.
The solution that worked for me was to
disable the "cleaver" URL fixing that
Firefox carry out when the page is not
found. The procedure taken from here:
1. Type about:config in the address bar and hit return.
2. find browser.fixup.alternate.enabled
3. double click the “true” value. The line will become bold, and
the value will change to “false”
This fix directly the problem. No
firefox restart needed. If your server
is down you get "page not found" as
expected. Hope it helps. link|flag
answered Sep 3 at 7:55 joaquin
2,237112
A couple of random things to check...
localhost is the conventional name for the IP address 127.0.0.1. If that address doesn't work, then you have a network configuration problem.
There will be a hosts file somewhere, probably in somewhere like C:\Windows\System32\Drivers\Etc\hosts which should usually contain only that definition for localhost. If it has more names in it and you didn't put them there, then you have another problem entirely.
There is also the forehead-slapping possibility that your web server is not currently running. :)
My development machine (Vista) was working perfectly fine for over a year and then suddenly (without explicitly installing anything) I am unable to run the websites using ASP.NET development server.
The development web server starts fine, but IE cannot display the page:
Internet Explorer cannot display the
webpage
Firefox says - Failed to
Connect, The connection was refused
when attempting to contact
localhost:49447.
Here is what I have tried so far:
Disabling firewall
Stopping anti-virus
Stopping Windows Defender
It worked when I stopped all services using MSConfig and tried again.
However, that disables most of the services, so is not a feasible long term solution.
After stopping all services, I tried starting services one by one to find out which one is causing problem.
These are the steps and results:
I found DNS Client Service was
causing problem.
So I started all others and
stopped DNS Client service, but then
Network Location Awareness service
started causing problem
I stopped DNS Client Service and
Network Location Awareness and
started all others, btu again
something else is causing problem.
Clearly there is something common and fundamental at the root of this.
I do not know much about networking. Can someone guide me in right direction?
Note: I have found another person who
is having same problems since this
morning. Looks like it could be
related to one fo the windows updates!
Is anyone else getting affected like
me?
I was able to fix this on my computer by doing the following:
My host file contained this line for the localhost entry, which is how the host file ships with Vista, and i've never modified this line
::1 localhost
Replaced "::1 localhost" with the this:
127.0.0.1 localhost
"::1 localhost" has worked fine for me for well over a year, until this morning. Windows defender installed two updates, one yesterday and one this morning, my guess is that something in one of these updates caused this entry to not work anymore.
I have solved this problem.
The problem comes because somehow the entry in host file is removed for localhost.
you have to add entry in host file which is kept in System32/etc folder.
just add this at the end of the file.
127.0.0.1 localhost.
save this file and try to ping localhost from cmd prompt.
i think this will resolve your problem.
now try running you website.
All the best.............
If stopping all the services made it owrk, try stopping one at a time. Eventually you will find out which one it is.
Hopefully someone will know which it is from experience, but if not you can find it yourself.
Sounds like you have a proxy server issue - have you checked this out?
KB886388 - You may receive a "Failure to connect to Web server" error message when you browse local Web applications
I also started to get this problem tonight, think I installed a windows update package yesterday.
I'm running VS 2008 (9.0.30729.1 SP) and Vista Ultimate SP1 (32-bit).
Replacing localhost with 127.0.0.1 worked for me.
http://localhost:49227/testsite/Default.aspx
http://127.0.0.1:49227/testsite/Default.aspx
I'm having the same problem. Was working on my website last night, one minute the site worked in the broswers next minute it could not connect to the localhost.
Replacing localhost to 127.0.0.1 worked for me. I'm still inexperienced in asp.net, is there a file where you change
http://localhost:49227/testsite/Default.aspx to
http://127.0.0.1:49227/testsite/Default.aspx
As I am just changing the url in the browsers
This one also worked for me. What I did was:
Go to the Property Page of my Project.
Then under Start Options, look for the Server, instead of 'Use default Web Server', i changed it to 'Use Custom Server'.
Typed the http://127.0.0.1:49227/MyProject/ in the Base Url.
That's it. It automatically opens the site using this link.
Same problem here using visual studio 2008 express
Changed "localhost" to "127.0.0.1" and the page came up.
This problem seems to have an effect on internet explorer and firefox
Opera hasn't seen this problem :-)
Grtz
Changing "localhost" to "127.0.0.1" worked well for me, as well.
but just to clarify the whom are not familiar with vista here are the guidelines to change:
Browse to Start -> All Programs -> Accessories
Right click "Notepad" and select "Run as administrator"
Click "Continue" on the UAC prompt
Click File -> Open
Browse to "C:\Windows\System32\Drivers\etc"
Change the file filter drop down box from "Text Documents (.txt)" to "All Files (.*)"
Select "hosts" and click "Open"
Make the needed changes and close Notepad. Save when prompted.
The problem comes because somehow the entry in host file is removed for localhost.
you have to add entry in host file which is kept in System32/etc folder.
just add this at the end of the file.
127.0.0.1 localhost.
save this file and try to ping localhost from cmd prompt.