VisualSVN messed up my localhost in Chrome - google-chrome

EDIT:
The localhost seem to be working fine in my firefox, IE and even Chrome's incognito mode. These is a problem specific to chrome. Any ideas?
PREVIOUS:
I just uninstalled VisualSVN Server from my Windows 7. But now when I try to hit localhost, I get redirected to localhost/svn. I am using WAMP and developing something that requires the root access. I can not put the project in a sub directory. I have also tried netstat -ao but no process is using ports 80 or 443.

You may have solved the problem....but for future, those who came here like me looking for a solution to this, this seems to be a prob for browser cache....clearing browser cache history solves the problem.....did for me...

If you uninstalled VisualSVN Server, then it's some other application which runs on 80 / 443 port that redirects you to /svn. Some steps that may help you to determine the root cause:
Verify that VisualSVN Server has been successfully uninstalled.
Start appwiz.cpl and see whether VisualSVN Server is listed as the installed application,
Start services.msc and see whether "VisualSVN Server" service is listed.
Run netstat -anbv and see which app runs on HTTP(S) port.

Related

Proxy server for Gatling

Recently I installed Gatling for performance testing on Ubuntu 14.04. And to run the recorder I needed to configure a proxy server in my browser. I tried to change proxy settings in Google chrome, but I don`t have rights. So I tried to do it using network settings in Ubuntu (Network -> Network proxy). But when I open a website which I need to test, nothing happens in the recorder.
So I do not really know is there a problem with the proxy server or Gatling itself? And how to check if the proxy server is configured correctly?
I would appreciate any help!
It's a bit too late, but I had a similar problem today. Was able to solve only by setting global IP address like xxx.xxx.xxx.xxx. Nor localhost nor 127.0.0.1 worked for me Chrome. After that I was able to notice http requests in Recorder inside Executed Events
Hopefully it could help somebody else
Edit : this is how setting looks like in Chrome, taking into account you have specified in Recorder Listening port to be 8000 also:

Chrome service-worker process running on port 3000?

The following error shows up in my Rails app logs and in my Chrome JavaScript console, but only on Chrome, and only when the app is running on localhost on port 3000:
Started GET "/service-worker.js" for 127.0.0.1 at 2015-12-15 09:31:04 -0800
ActionController::RoutingError (No route matches [GET] "/service-worker.js"):
Apparently someone else has had this same problem, but solved it by reinstalling the OS (!). This isn't an option for me.
According to lsof, there is some other some other process running on port 3000:
COMMAND PID FD TYPE NODE NAME
Google 49368 174u IPv4 TCP localhost:55612->localhost:hbci (CLOSE_WAIT)
ruby 57985 17u IPv4 TCP *:hbci (LISTEN)
Other things of note:
NodeJS is installed
Chrome Version 47.0.2526.80 (64-bit) on OS X 10.10.5
The stuff in chrome://flags/ has been reset to default
I've disabled all Chrome extensions
If I kill that Google process, it just reappears
What is this uninvited process?
Visit chrome://serviceworker-internals/ to view a list of service workers.
Click the "Unregister" button to remove the registration of the offender.
The Google Web Starter Kit installs a service worker that may continue running after using its local development server.
ALL CREDIT for this answer goes to Jeff Posnick. Just thought this question should have a formal answer that's easy to find since it was driving me to madness before I came across this page :)

MAMP not connecting to localhost

Just updated MAMP to version 3.2.1 on Yosemite. Both Apache and MySQL servers are green but when I go to my localhost I keep getting: This webpage is not available ERR_NAME_NOT_RESOLVED in browser (Chrome). I’ve tried incognito browsing and Firefox with the same result, tried both the MAMP default port settings and ports 80 & 3306, tried a reinstall of MAMP and rolling back to previous install of MAMP; all without success.
Can anyone suggest how to fix this…it’s starting to drive me crazy!
Possible Thoughts;
In your /Applications/MAMP/htdocs/ folder, is there something in there for your browser to load? Some sort of index.html or index.php file? Could it have gotten removed accidentally?
When you launch MAMP and go to Preferences -> Ports, what is the Apache port? You mentioned you tried the default (8888/8889) and 80/3306, but could the port number somehow have gotten changed?
Is there any chance that some other Apache service is running? This is unlikely as you mentioned that MAMP shows Apache status as green, but it could be worth stopping MAMP, opening Terminal and doing sudo apachectl stop, returning to MAMP and changing the ports to 80/3306, then returning to Terminal and doing sudo apachectl restart. Then return to MAMP and start services again.
If none of the above work, what if you set the Apache port in MAMP's preferences to something random, like 8712, and then try http://localhost:8712/ to see if it loads.
Let us know if you've tried those already!
Had a similar issue. If 127.0.0.1 is working then you just need to point localhost to 127.0.0.1. Edit /etc/hosts file (requires sudo) and include
127.0.0.1 localhost
That resolved it for me.
This still happens occasionally when updating macOS.
Going through all local Wordpress sites and changing the dev url isn't ideal, though necessary when changing the port.
What rather solved the issue for me was restarting Apache as suggested by #ZbadhabitZ, keeping original port number:
sudo apachectl restart
I had this issue because I had Docker Desktop running at the same time; I shut this down and it started working so it must have been a port conflict.

problems running xamp

I am using a open source document repositary kordil edbms which works fine in my windows 7 machine .
But when i installed it in windows small business server, xamp is not running. when i start task manager httpd itself is not getting shown. I went to xamp control panel and it says error running mysql busy.I have share point in that machine which also has localhost 80.
So I changed the apache port.
I changed the apache port in httpd.conf file in 2 places
listen
server name
It seems i need to change the port for mysql also. Now what is the option to change the port for xamp mysql or am i going wrong some where else. Please also look at the screenshot of xamp control panel.
Quit Skype and then restart all services from your XAMPP and let me know if its work or not.
Port conflict as Skype also consumes 80 by default
Click on SCM and manage services by starting and stopping.
EDIT
check this link for both to work with - http://www.binodranabhat.com.np/blog/using-xampp-and-iis-together/
MYSQL not working because xampp which path excepting that path not getting automatically .
that is reason behind xampp mysql not start
go to window +R press then open cmd with run as administration then type this command
sc delete mysql
then after start mysql problem resolved.
Fixing Apache Port Conflicts
Another error message that is pretty common to see when working with XAMPP is a notification in the XAMPP control panel that the ports Apache needs to use, ports 443 and 80, are already being used by another application.
A message from the XAMPP control panel letting us know Skype is using ports 443 and 80
In the case of the error message in the image above, this is a pretty easy fix. The offending application is Skype. If you see the same message, close Skype completely and restart XAMPP to solve the problem. Skype is a frequent-flier on the port-blocking scene and pretty easy to identify and remediate. Unfortunately, things aren’t always so simple.

Can't Access localhost or 127.0.0.1 in wamp

I was using wamp 2.1a for my wordpress blog and a website. It was working fine. Then I caught a google redirect virus. I tried hard to get rid of it, finally i fixed it. Then, suddenly my wamp server stopped working, I mean both the services were running but when I opened localhost or 127.0.0.1, it just kept loading, and went on forever till I closed the browser's tab. Then I upgraded to wamp 2.2a and the problem is still there.
I've also checked the hosts file, tried to change the port to 8080 for apache, but it didn't help. I do not have skype (and never used it) so there's no port 80 conflict. When I restart the services, the apache service starts but the mysql service doesn't. When I click wamp tray menu, click on the remove service for mysql, a message box appears saying - mysqld.exe has stopped working. The only option I have there is close program.
I can't access my blog so I can't so any testing. Please tell me if this happened to you or if you have a solution to this. Any help is appreciated.
Did you try different web browser? I guess it is browser problem, clear your browser cache, might solve your problem.
I have found the following solution in another post here (from Sergiu Butnarasu) which worked for me.
Modify the apache HTTPD.CONF file. Change "Listen 80" to "Listen 0.0.0.0:80 http://forum.wampserver.com/read.php?2,93143