Pow used to work for me a few months ago, but now it's not working for my new app, or for the ones that worked before.
I went into ~/.pow and created a symlink, but when I type MYAPPNAME.dev/ in my browser, it redirects to a cox(my internet provider) page saying "Sorry, the website subscriptions.dev cannot be found"
I read through all the docs in the pow page, and tried installing powify as well, but nothings working.
Is there something I may have done in my console (such as changing PATH or things) that may cause this to not work?
I tried restarting my computer as well, but still nothing..
=============================================================
Edit: Actually I just came to my office and it started working. Is it possible that my internet provider at home could be blocking/interfering with pow? I would assume that it's irrelevant since I thought pow was essentially a local host.
DNS hijacking from your ISP. Try setting your DNS server to 8.8.8.8 (google's DNS) and see if the problem persists.
Related
This is weird. On my personal computer at home when I type in my website, I get a 404 error.
No other computer gets the 404 error that I can see from several work computers to relatives, wife's laptop and even my phone using the same WIFI connection.
This only happened after switching my preferred domain under preferred hosting settings from www.xxx.com to xxx.com - perhaps coincidence, perhaps not.
I did this as links in Twitter and Facebook where directing to xxx.com and were giving me 404 errors. Note that the day I made the change the 404 errors went away and I was linking to my website. Then a day later, not working to access my website.
I would suspect nameservers etc but my computer is the only one seemingly exhibiting the problem.
I cleared the browser cache for Chrome and Edge still nothing. I downloaded FireFox and installed fresh and get the same 404 error.
I flushed the dns with ipconfig in administrator mode and it has been over 24 hours since the problem first occurred.
I can get to my website using the IP address fine. I can't using the URL, only on this computer. I even called GoDaddy to make sure it was only my machine and they say they see no problem.
The HOSTS file is virtually empty. and I can use the website with Visual Studio no problem.
Any thoughts? I am stumped on this anomaly.
Thanks again everyone! Your feedback helped me solve the problem. This project was originally started in PHP and moved to from Apache server to ASP.NET. My hosts file still had remnants to xxx.com being local, and not searching outside to the world. Removing 127.0.0.1 xxx.com solved the problem.
THANK YOU!
I have a Windows 2012 R2 server and I managed to install the SonarQube 5.4 server as a Windows Service. I also set up a user so the service can actually start without the infamous "It started then stopped" error a lot of people seem to get. Before installing the server as a windows service, I checked that it worked using StartSonar.bat and it did work just fine, so I was confident when I made it into a service.
But when I try to access http://localhost:9000 there is nothing there, and it appears that shortly after starting the service it stops without any message at all. I can't tell if this is because I try to access the site (which gives me ERR_EMPTY_RESPONSEin Google Chrome) or if it just closes down after a short while.
Anyone got any insight?
I'm a beginner. I came across the same issue and fixed it.
Ensure that the database is running.
My log file (located at sonarqube_home_dir/logs/sonar.log) included the following statement.
Caused by: org.h2.jdbc.JdbcSQLException: Wrong user name or password [28000-176]
Since I'm using the default database, I commented below lines
#sonar.jdbc.username=***
#sonar.jdbc.password=***
at sonarqube_home_dir/conf/sonar.properties.
This must happen due to many reasons like connection problems, permission problems so First, you have to see the logs. /sonarqube-7.6/logs$ tailf sonar.log. then you can find the reason. Once I had the same problem so I did like that. my error is something Directory does not exist: lib/jdbc/mysql
org.sonar.process.MessageException: Directory does not exist: lib/jdbc/mysql reason is I uninstall MySQL and remove all folders name contains "MySQL".
just check whether port 9001 already in used, stop it if already in used.
I am eager to know why localhost.com (without www) redirects to google.com. I also noticed that www.localhost.com gives a 404 page not found. I checked this in Firefox, Chrome and Internet Explorer all does the same. I checked the domain name records and it shows it belongs to Tucows and I am pretty sure Google doesn't own it and I know we can use http redirect to change it to a www or non-www version as the site owner wishes.
Interesting answer posted by Ken Watford, Google employee: http://www.quora.com/Why-does-http-localhost-com-redirect-to-Google
He claims someone bought the domain when the web was still young and kept it ever since, but he does not say who.
It looks like others have had the results as you, check out the links below.
Try here:
http://answers.yahoo.com/question/index?qid=20111105050333AATP1r5
or here:
http://forums.phpfreaks.com/topic/146474-localhost-redirects-to-googlecom/
I think localhost.com should be owned by google as I tried pinging it and it showed the ip of google.com.I still don't know why the DNS records shows tucows as the owner.
I have been searching this from long and finally i found complete solution after going through different answers.
As far as #pradeep's answer is concern, he is right that localhost.com is purchased and points to particular IP so it is redirecting.
But we can override domain names in Windows platform for our local development PC via hosts file residing in C:\Windows\System32\drivers\etc as per #Faysal's answer.
Open hosts file as administrator and enter following line
127.0.0.1 localhost.com
But doing such also did not solve my problem. So i found final solution which will work in chrome browser.
In chrome you have to clear all dns cache via opening following url
chrome://net-internals/#dns
And here clear all cache and finally you will be redirect localhost.com to your local server's home page.
If you are using the Windows platform, then go to your %windir%\System32\drivers\etc and copy the host file to %userprofile%\Desktop. Open it with any text editor and remove the # sign from the front of 127.0.0.1 localhost. Save it and paste it back. Check if the problem is solved.
localhost.com is a website. It does not point to your local IP, instead it most likely has an A record pointing to Google's IP. It practically is Google, and I can prove it.
When the site worked if you connected using HTTPS then it would give a certificate error, the reason being that the certificate is signed to google.com but localhost.com is connecting.
I think the site has now been removed though.... I hope that solves it. It can cause some confusion since localhost points to 127.0.0.1.
So, I struggled with this for the last hour. For some reason, my POW domains always hit a www.website-unavailable.com error in Chrome. Rails servers work great from the traditional rails s and pull up at localhost:3000. I'm using Anvil.app to manage the domains.
No matter what, I hit the www.website-unavailable.com page in Chrome immediately each time I try to visit a .dev domain.
The strangest thing is, the site loads great in other browsers. Just not Chrome. I even tried installing Chrome Canary and it hits the exact same error (fresh install!).
I tried, in this order, to no avail, to get the server running again:
Rebooting.
pow restart in the terminal for various sites.
Reinstalling POW.
Clearing the DNS cache at chrome://net-internals#dns
Nothing seems to work. Any idea what I could do to get this working again? Not a huge deal to use localhost:3000 but I love POW. The strange thing is, it was working wonderfully for weeks.
I ran into the same issue, but changing from OpenDNS to Google's DNS servers didn't help. Apparently, this is an issue with the asynchronous DNS built into Chrome.
There are a couple workarounds:
Use .xip.io domain instead of .dev
Disable asynchronous DNS in chrome://flags
Disable NXDOMAIN helper
I ended up disabling asynchronous DNS and my .dev domains work again.
Here's where I found more information:
Issue reported on Pow
Issue reported on Chrome
How to disable NXDOMAIN helper for OpenDNS
Thanks to user Dan Reedy (see above) I was able to fix this by moving from OpenDNS to the Google DNS 8.8.8.8 and 8.8.4.4 settings. Now, pages load faster and Pow servers are working again. And they seem to actually load much faster. Awesome!
I look up my IP via Network Preferences on a Mac OS X, and navigate to a domain like so :
http://subdomain.name-of-app-directory.ip-address.xip.io
So an example would be :
http://subdomain.website.10.0.0.0.22.xip.io
I am facing a strange issue with azure -
After uploading a new version of my app about an hour back, the public facing url is throwing a runtime error. However the app works fine when I access it through the azure internal domain -- app.cloudapp.net.
Before upgrading it was working fine.
I have rechecked the cname records with my hosting provider (bluehost) but I cannot find any problem. Even otherwise, the problem seems like an ASP.net issue (due to the typical error page rendered) but something that just does not make sense.
Anyone has any ideas as to what I can do?
EDIT: This started working just as mysteriously as it had stopped - I have no clue whether it is due to DNS propagation delay (although in that case it should not have thrown an error page like described above). However if someone knows why this might happen, I will still appreciate it.
There is a DNS service available for Windows Azure called "DNS Azure" that changes your cloudapp's IP address automatically. See dnsazure.com
This solutions helps to avoid the CNAME record because the A record is kept up-to-date.