I have a webserver running in an VM (VirtualBox, configured with vagrant) which is assigned the private ip 10.0.0.20. I can reach the webserver with Google Chrome, but not with Microsoft Edge. I have activated Allow Localhost Loopback in about:flags.
Does anybody what could be the problem?
Not sure about the root cause of the problem, but here are some options to work around this:
Configure VM Networking to be Bridged rather than NAT;
Use a proxy, e.g. Fiddler;
Port forward, using netsh, ssh or other utilities.
For option 2 and 3, see this answer for details.
I have the same problem and can't find a workaroud -- even after 2 years. I guess the final answer is: Stop using Edge.
Looks like Microsoft is dumping it: [https://arstechnica.com/gadgets/2018/12/post-mortem-tying-edge-to-windows-10-was-a-fatal-error/]
Go to the start menu and type "Internet Options" Select internet options and open he security tab click on Local Intranet then press the sites button.
Control Panel > Internet Options > Security > Local Intranet > Sites
Uncheck "include all local (intranet) sites not listed in other zones" and "Include all sites that bypass the proxy server".
Restart Edge and try again.
If your machine with the webserver has internet access you could use a tool like ngrok to create a tunnel with a public URL to your machine.
http://www.sitepoint.com/use-ngrok-test-local-site/
I'm running the latest win 10 V 1809 build 17763.253.
I have checked several threads that don't show any solution, but I found one thread with a workaround by adding the local IP range to the trusted sites, it works for me.
Second workaround is using the server name instead of the IP address.
Example: http://Computer-name/ which gets resolved to IP version 6 address.
Since this is bug only happens with MS EDGE and works fine with all other browsers, where is the official MS solution ?
enter image description here
Related
SETUP
I have a windows 10 PC connecting to my linux server (ubuntu 18.04.2). I run/edit code on my powerful server by remotely accessing the server through VS code's ssh ability. It is super convenient to edit my code on the server with VS code...
THE ISSUE
Visual Studio code won't connect to my Linux server. What is weird is that I am able to ssh into the server from the terminal within VScode by just literally typing ssh <username>#<server-hostname>
However, when I do the Remote-SSH option within VScode then it does not want to connect to the server...strange...
Here is how I remotely SSH into server with VScode built in functionality (marked with red rectangle). Also part of this screenshot is my config file, which I have triple checked as correct (IP address and .ssh/id_rsa_gpu_1_solarpv_ssh location)
HERE IS THE ERROR OUTPUT
MY ATTEMPTS
I have made sure that the config file is setup correctly and that the IP address is correct.
I have ensured that the server's IP address is also in the 'known_hosts' file located at /Users/.ssh/
I even generated my own private key for SSH connection as advised by the great documentation here: https://code.visualstudio.com/docs/remote/troubleshooting#_quick-start-using-ssh-keys
Still getting the error of failed to create hard link...
With all of my back-end stuff done right, I am absolutely clueless regarding why this is an issue.
After spending literally 9 hours on this issue...here is the answer:
When you launch VScode and remotely access the linux server, the linux server is instructed to download and install a vscode server so that you (on the other side) can remotely connect to the server.
If the server does not have internet just make sure the following setting is ticked
This allows the remote server (without or with internet connection) to get the vscode server running.
To eliminate the "failed to create hard link error" go to the directory mentioned by the error, which in this case on linux server is
navigate to /home/<username>/.vscode-server/bin/0ba0ca.../
then remove/delete the hardlink file and target file which also has
the same name as the directory.
Then just attempt to remotely access your server again through
vscode and all should be fine
Here is also a discussion regarding the issue...if you still have problems https://github.com/microsoft/vscode-remote-release/issues/2507
I solved this by enabling the option Lockfiles in Tmp:
i just deleted the whole library and it works, i don't see anything wrong with doing that.
rm -r /path_to_project/.vscode-server/
if i'm wrong feel free to correct me :)
Try this
Just in case others need to try the same here is the detail
ctrl-shift-p and choose:
Remote-SSH: kill VS Code Server on Host...
Chose the host name
Selected the platform type (linux)
https://github.com/microsoft/vscode-remote-release/issues/4307#issuecomment-762882247
worked for me.
I have installed the Windows 10 Insider Program. Everything works, except Apache. When I try to start it, it says that port 80 is blocked. Is there a way to unblock it or tell Apache to use another port instead?
I was using Windows 7 before. I had trouble with port 80 with skype, but i have disabled it.
I had the same problem on windows 10, IIS/10.0 was using port 80
To solve that:
find service "W3SVC"
disable it, or set it to "manual"
French name is: "Service de publication World Wide Web"
English name is: "World Wide Web Publishing Service"
german name is: "WWW-Publishingdienst" – thanks #fiffy
Polish name is: "Usługa publikowania w sieci WWW" - thanks #KrzysDan
Russian name is "Служба веб-публикаций" – thanks #Kreozot
Italian name is "Servizio Pubblicazione sul Web" – thanks #Claudio-Venturini
Español name is "Servicio de publicación World Wide Web" - thanks #Daniel-Santarriaga
Portuguese (Brazil) name is "Serviço de publicação da World Wide Web" - thanks #thiago-born
Alternatives :
Another solution is to shutodwn the service via an admin console with command sc stop W3SVC
see community wiki from Tobias Hochgürtel Apache Server (xampp) doesn't run on Windows 10 (Port 80)
Edit 07 oct 2015: For more details, see Matthew Stumphy's answer Apache Server (xampp) doesn't run on Windows 10 (Port 80)
This answer is intended as an addendum to the highest rated answer on this thread by paaacman. I just wanted to add some helpful detail for users like myself who don't know their way around Windows 10 as well.
Windows 10 runs IIS (Internet Information Services, Microsoft's web server software) automatically during Startup on Port 80. In order to use Apache Server on that port, IIS must be stopped.
paaacman's response refers to the IIS server as "W3SVC", or the "World Wide Web Publishing Service". I suppose that's because Windows 10 runs IIS as a service. In order to disable it or modify how the service runs, you need to know where to find "Services" in your system.
I found the easiest way there was to click on the search button next to the start menu button in the Windows 10 taskbar and type "Administrative Tools". You can either hit return or click on the "Administrative Tools" link that Windows finds for you.
A control panel window will open with a list of tools. The one you want is "Services." Double-click it.
Another window will open called "Services." Locate the one named "World Wide Web Publishing Service." Some other users in this thread have listed what it is called in other languages, if your list is not in English.
If you only want to turn off the IIS server for this Windows session, but want it to run automatically again the next time you start up Windows, right-click "World Wide Web Publishing Service" and choose "Stop." The server will stop, and Port 80 will be freed up for Apache (or whatever else you want to use it for).
If you want to prevent the IIS server from running automatically when you start up Windows in the future, right-click "World Wide Web Publishing Serivce" and select "Properties." In the window that appears, locate the "Startup type" dropdown, and set it "Manual." Click "Apply" or "OK" to save your changes. You should be all set.
With Windows 10 IIS runs on Port 80 by default which can be changed:
Run appwiz.cpl use Turn Windows features on or off and install the IIS Manager Console.
Run InetMgr.exe and go to "Connections -> Sites" and open with right-mouse click the context menu on the default entry "Default Website". In Context Menu select "Bindings" to open the Server address and port configuration.
https://technet.microsoft.com/library/hh831681.aspx#Site_Bingings
I had the exact same problem and solved it running the folowing command from the command line as an admin :
1) first stop the service with the following
net stop http /y
2) then disable the startup (optional)
sc config http start= disabled
Type in command line
netstat -aon | findstr :80
You'll see PID of process which uses port 80.
Then try to configure this app to use another port, or just kill it
UPDATE:
I'll write my comment here to be more clear: according to this link, in Windows 10, it is the MsDepSvc service which occupies port 80. It's for IIS or Web Matrix 2. If you will not use IIS or Web Matrix 2 for any web development, you can try shutting down the service
And for the second part of your question, you can tell Apache to use another port by editing [Apache folder]/conf/httpd.conf. It has "Listen 80" string. Change 80 to whatever free port you want and reload Apache
You may need to terminate SQL Server Reporting Services as well.
In my case I need both XAMPP for Apache development & IIS Express for .Net 2013 development; so I do the following:
In Command Prompt typed services.msc, this loads "Windows Services" where I located "World Wide Web Publishing Service" and stop it.
World Wide Web Publishing Service STOP
The I start XAMPP Control Panel click on "Config", then choose "Apache httpd.conf". Search for "80" then change that to "8080" in both "Listen 80" and "ServerName localhost:80". Save the file from "Save As" & choose "All files" to not save it as text from "Save As Type" & the "Encoding" should be "UTF-8".
Apache httpd.conf
Quit XAMPP Control Panel, then start it again and from "Action" start Apache & MySQL. Now you will see the port changed. As you know now you have to get to your Apache server by using "localhost:8080" instead of "localhost". Also you have both Apache & IIS Express running in the same Windows 10 PC.
I read a post some where were the writer suggested to use port "9080" but it did not work for me.
The problem happens whenever a process uses port 80.
You can run Netstat which is available in XAMPP Control Panel and check which process uses port 80 in your system.
For me it wasn't IIS, but Skype.
Turn off that process/application and then start the Apache services.
I know that maybe this problem was resolved but I had the same problem with different solution. For that, I am going to explain another possible solution. In my case, the port 80 was occupied by Skype (pid: 25252) and I did not know what programme was.
To see the program's pid which is using the port 80 you can use the command that other people said before:
netstat -aon | findstr 0.0:80
To kill the process using the pid (in the case that you do not know the programme) you have to open the CMD with administrator permission and use the next command:
taskkill /pid 25252
Other options with this command are here.
I think it simple to change your Apache server port
Go to C:\xampplite\apache\conf
Open httpd.conf files
Search for Listen 80
Change 80 to any other like 9080
Now XAMPP restart try to start server
NB I am using Server version: 5.1.41 with windows 10
I know this MIGHT not be the cause of your issue, but I've spent a few hours hitting my head against the wall to solve this issue and this is my solution.
(running Windows 10 x32)
So I had installed XAMPP in a deeply nested directory and all the conf files make reference to root\xampp\apache, whereas my files were some_dir\another_dir\whatthehelliswrongwithme\finally\xampp\apache
so my options were to either go through and edit all \xampp\apache references and point them at the right place, OR, the much simpler option... reinstall XAMPP at the root, so the references all point to the right place.
A little annoying, but I guess that's what we get when Mac and Windows try to be friends..
Hope it helps a few of you.
In case you need to run IIS on port 80/443 but on different IP address, you may use netsh http add iplisten xxx.xxx.xxx.xxx as described here:
https://support.microsoft.com/en-us/help/954874/iis-binds-to-all-ip-addresses-on-a-server-when-you-install-iis-7-0-on
More details about netsh http add iplisten can be found here:
https://msdn.microsoft.com/en-us/library/windows/desktop/cc307219.aspx
Shutting down "some system process" may be tricky... you should rather edit the [Apache folder]/conf/httpd.conf as mentioned by #Sergey Maksimenko and if you want to configure virtual host, use the new port in [Apache folder]/conf/extra/httpd-vhosts.conf (I used 4900 instead of 80 and 4901 instead of 443 in [Apache folder]/conf/httpd-ssl.conf). And remember to use the port when accessing page on localhost (or your virtualhost), for example: localhost:4900/index.html
This fixed node.js not running on port 80 under Windows 10 as well, I was getting a listen eacces error. Start > Services, find "World Wide Web Publish Service" and disable it, exactly as paaacman described.
I had the same issue and none of the above solutions worked for me.
Apache uses both ports 80 and 443 (for HTTPS) and both must be ready to be used for Apache to start successfully. Only port 80 might not be enough.
I found in my case that when running VMWare Workstation I had the port 443 used by the VMware sharing.
You have to disable sharing in the VMware main Preferences or change the port in this section.
After that as long as you have no other server hooked to the port 80 (see above solutions) then you should be able to start Apache or NGinx on XAMPP or any other Windows stack application.
I hope this will help other users.
While many are taking the approach to stop/disable IIS, it may be helpful to know that you can simply modify the XAMPP port, which has been answered here. This is the route I had to take as I need both running.
Beside the quite obvious reason (IIS), there is another reason that is common enough for this problem. It is worth to quote this question and its answer here:
http://stackoverflow.com/questions/22994888/why-skype-using-http-or-https-ports-80-and-443
So, if you have Skype installed in the computer, be sure to check this as well. The solution is quoted here:
To turn off and disable Skype usage of and listening on port 80 and port 443, open the Skype window, then click on Tools menu and select Options. Click on Advanced tab, and go to Connection sub-tab. Untick or uncheck the check box for Use port 80 and 443 as an alternatives for incoming connections option. Click on Save button and then restart Skype to make the change effective.
First, open regedit run as administrator
see image
open HKEY_LOCAL_MACHINE\SYSTEM\CurrentCurrentControlSet\Services\HTTP
open Start, change value from 3 to 4
see image
then restart your computer
I am trying to run a simple HelloWorld app on my MacBook using Eclipse Luna and I am getting this message:
The current server configuration is set to "localhost". Therefore the
Worklight build uses the primary IP address of this computer
(???.???.?.???) instead. It is recommended to set the server
configuration to use the fully qualified hostname or IP address of
this computer. To configure the setting, in the "Servers" view
double-click the Worklight Development Server entry and edit the "Host
name" field.
Clicking the Worklight Development Server opens a sub menu with different files. I believe that I need to replace localhost by my IP address. Which file and which entry need to be modified?
It is only a recommendation and typically in most cases for local development there is no need to change this value.
If you still prefer to change it, it is where the message says so.
Open the Servers view and double-click on the "Worklight Development Server" entry (no need to expend it):
I just solved the same problem. I had to change the Host Name to the name of my PC and it worked.
#Simon, Can you do a DNS flush on your mac once and give it a try. Sometimes DNS flush causes some sort of unwanted issues which doesnt resolve the ip address and acts funny
refer :- link
I've trawled through the boards but cant find a solution to my problem.
I've run a netstat, and nothing else is using port 80. I have disabled every bit of security on my system, just to be doubly sure nothing is stopping it.
MySQL boots up just fine, but Apache does not start up. Using the built in port 80 tester also says that port 80 is clear, but when I click the start service button on Apache in WAMP nothing happens.
Any help is appreciated.
Run cmd.exe as administrator. Then execute:
httpd -t
httpd -k start
Are there any error messages displayed?
If not, temporarily disable any firewall and anti-virus software you have. Try again.
If you're still not getting any error messages, uninstall your WAMP and try one of the other distributions - http://en.wikipedia.org/wiki/Comparison_of_WAMPs
I have had the same problem but I have resolved it by logging out of Skpe, stopping Skype's service called Skype C2C Service and started wampapache Service. After I started wampserver, I then logged in Skype After. Both Skype and amperver work well after this process
Ok just do one thing. If you are running skype then close it. restart all services, It might work as it worked for me.
Some times this occurs when Windows Event log Service is disabled.
I recently faced the same problem,and browsed various answers around web in vain.
But later I remembered that I disabled Windows Event Log Service in Oder to run a game smoothly.So I Enabled that service again and now every thing is working fine.
Download and install vcredist_x86.exe from http://www.microsoft.com/en-us/download/details.aspx?id=8328
I opened up services.msc from the command prompt and disabled SQL Server reporting services
& SQL Server analysis services. These services were using port 80.
Then I restarted WAMP Server and it started working properly as before.
Check DocumentRoot directory location if it exists.
DocumentRoot "C:/wamp/www/"
I have solved my problem just following the below steps. Hope this will help to you.
Go to Wamp/Apach/httpd.conf
Under httpd.conf search for Listen in my case its Listen 0.0.0.0:80
Just change the last digit that means your Listen will be Listen 0.0.0.0:81
Save the file, after that start Apache
Thanks,
Amzad
From time to time, with the updates, Microsoft set the 'World Wide Web Publishing Service' startup type to 'Auto'. Try to see if that is your case.
Right-click on your Start button to open the WinX Menu. Select Run. This opens the Run box. Now type services.msc in it and hit Enter to open the Services Manager.
Locate that service and edit with double-clik then set the startup type to 'Disable' to avoid it comes into conflict.
hi the solution is simple.
all you have to do is to right click on wampserver icon on the taskbar and select exit.
after doing that right click on the wampserver.exe icon and select run as administrator option from the context menu.
that's it.
it will solve your problem
I installed Oracle 10g express. Installation went well, But the home page is not coming up.
I can connect using sqlplus but not with Sql Developer.
I checked tnsnames.ora and listener.ora everything looks fine.
Listener is also started. I can always reinstall and see. But I thought better inquire the cause.
Regarding the home page. This is the address that comes up in browser. Localhost:8080
http://127.0.0.1:8080/apex
I did a netstat to see whether there is any port conflict for 8080, but that port is not in use.
Have anybody faced this issue?
Yes. It is practically a FAQ on the XE Oracle forum.
Firstly, can you connect to Oracle using
sqlplus user/pass
If so, Oracle is up an running (which appears to be your situation, but may not be for a future reader with a similar problem). If not, you can try
sqlplus / as sysdba
startup
Once Oracle is up, check that the listener can see the Oracle instance by
sqlplus user/pass#xe
If not, then either the listener is not up, or the 'listener does not know of the service'. Make sure the listener is started (lsnrctl, then start). Make sure the database is registered with the listener
sqlplus / as sysdba
alter system register;
Now you should be able to connect using the '#xe' syntax. Worthwhile verifying the embedded PL/SQL gateway is set up to use the 8080 port
select dbms_xdb.GETHTTPPORT from dual;
On Windows you can use netstat -ab to see if tnslsnr.exe is listening on the port.
Then I'd suggest looking at browser settings (specifically any proxy settings that might be forwarding your request to a machine that has no idea what to do with it) and firewalls (which could well be set to ignore or hide any access to the port).
I had the same problem. I tried this and it sorted out my problem...
1. goto start->run
2.type services.msc and hit enter
3.In the applet that opened, scroll down(in right pane) to figure out the option of "OracleServiceXE" and right click on it. 4. In general tab do->>> startup type "Automatic" and click the "start button".
5. Repeat step 4. for the option "OracleXETNSListener".
close the window.
now, i hope, the problem should be solved....
Check your windows firewall,If it is on it blocks the opening of the homepage.Either you shut down the windows firewall or allow these following ports :
1521: Oracle database listener
2030: Oracle Services for Microsoft Transaction Server
8080: HTTP port for Oracle XML DB and the Oracle Database XE graphical user interface
See software requirements in the below URL:
http://download.oracle.com/docs/cd/B25329_01/doc/install.102/b25143/toc.htm#BABEBCDB
It worked for me!
Try this ( I'm assuming Windows system )
using
netstat
without anyother parameter would tell you if port 8080 is already open.
Also you can try this:
telnet localhost 8080
If the server answers ( the screen goes blank [or black] ) then the server is up and running.
Try using your hostname instead of localhost.
See if you're using a proxy and not skipping the local addresses.
Also you can see what's the executable that starts the home page and see if it could start successfully.
Thanks for the response guys.
I finally figured out how to solve the issue, but not really the root cause.
Problem 1 - Can not login to oracle admin console.
It was the problem with not adding 127.0.0.1 in the IE intranet sites.
Go to tools>internet options>security>local intranet sites>advanced>
add http://127.0.0.1:8080/apex in the list.
It works fine after this.
But if I go back to the same place again and see the sites, I cant find the url I added sometimes back... Dont know why that is happening. May be some company security is messing up.
Anyways the admin console is now coming up.
Problem 2 - Cannot connect using SQL Developer.
After I did the fix for problem 1, this is also magically working.
I still don't know how security settings in IE affects SQL Developer?
Any comments on this?
hey guys one important fact if u r using IE7 (explorer7) then u wd face certain problem in using 10g, such as not displaying home page.
For Windows 8 simply click on Get Started With OracleXE.... When internet explorer opens up, select the View on the desktop option in the Page View icon (icon with a wrench).
You should now be able to view your page.
I had a similar problem, I was able to connect to SQLPLUS using terminal but on access in browser as it was showing error as you have described. So, I went back to terminal and mounted my database using
startup
and it resolved my problem. This might be the case.