I have Windows 10 Pro and have installed CodeReady Containers (with "user" network mode due to being on VPN). When I initially do "crc setup" to create the virtual machine, it works fine, and "crc start" works as does "crc console". However, if I restart my computer, the console URL https://console-openshift-console.apps-crc.testing/ unexpectedly shows the IIS "welcome page". I've tried navigating to IIS, right-clicking my localhost server and clicking "Stop", but still the "welcome page" displays. If I open a CLI and execute "iisreset /STOP", when I navigate to the crc console URL, Chrome shows "This site can't be reached / ERR_CONNECTION_REFUSED". Also if I try to execute "crc stop" I see an error:
dial tcp 127.0.0.1:2222: connectex: No connection could be made because the target machine actively refused it.
Also "crc status" shows: OpenShift: Unreachable (v4.8.2)
I need to be able to have IIS coexisting with CodeReady Containers, ideally with both running simultaneously. How can I make this happen? There must be something with the initial crc setup that allows the console URL to work.
Related
I have an Asustor NAS connected to my router, on a Mac Studio. The router shows the unit as connected, with IP address 192.168.0.102.
If I open that URL in my Chrome browser, I get a page that says 'This site can't be reached. 192.168.0.102 refused to connect.' This happens if I use port 8000 (http) or 8001 (https).
I can connect to the NAS with Finder, and see the data stored on it, so the device is connected and responding, but I cannot connect to the OS (called ADM) through the browser.
Does anyone have any idea what could be the issue here?
You are not going to believe this. When Chrome says the site can't be reached, all you have to do is enter the text 'thisisunsafe' anywhere in the browser window. This bypasses the Chrome security features.
See https://cybercafe.dev/thisisunsafe-bypassing-chrome-security-warnings/
After installing google chrome(version 75.0.3770.100) in windows 10(update 7/7/2019), I lost Internet connection.
The error is:
The DNS server isn't responding.
I tried to solve it but it was not successfull. for example in CMD:
netsh winsock reset
ipconfig /flushdns
ipconfig /renew
But when I remove google chrome from Windows 10, Internet connects again!!!
I do not no why! It's very strange!
How can I solve this problem, while keeping chrome?
Have you tried changing both ipv4 and ipv6 dns to:
The Google Public DNS IP addresses (IPv4) are as follows:
8.8.8.8
8.8.4.4
The Google Public DNS IPv6 addresses are as follows:
2001:4860:4860::8888
2001:4860:4860::8844
If changing that DNS solves the problem, you have to call you internet company and tell the problem, or change internet company. (if you don't want to use google dns)
Try the following possible solutions:
Change The DNS Server
If there is a problem with your IP DNS server, you can try to change your DNS server to Google's Public DNS, a free alternative Domain Name System (DNS) service offered to Internet users around the world. The public DNS service and servers are maintained and owned by Google. It functions as a recursive name server providing domain name resolution for any host on the Internet. You will have to change the DNS manually, and we show you how.
To change your DNS server to Google's DNS server, go to your Network Connections settings. Right-click the Start menu and select "Network Connections", or go to Settings and click" Network & Internet".change dns server
Change dns server step 1
In the Network & Internet settings window, select your connection type (in our case, "Ethernet") on the left pane and then click "Change adapter options" on the right pane.
Change dns server step 2
Right-click on your connection and select "Properties" from the drop-down menu.
Change dns server step 3
Select "Internet Protocol Version 4 (TCP/IPv4)" and click "Properties".
Change dns server step 4
In the Internet Protocol Version 4 (TCP/IPv4) Properties window, select "Use the following DNS server addresses", enter 8.8.8.8 as the "Preferred DNS server" and 8.8.4.4 as the "Alternate DNS server". Click "OK" to save changes and check if this helps to fix the problem with the "DNS server is not responding" error.
Change dns server step 5
Disable IPv6
Internet Protocol version 6 (IPv6) is the most recent version of the Internet Protocol (IP), the communications protocol that provides an identification and location system for computers on networks and routes traffic across the Internet. IPv6 was developed to deal with the long-anticipated problem of IPv4 address exhaustion. Disabling the IPv6 feature might help to fix the "DNS server is not responding" error.
The easiest way to disable IPv6 on the Windows operating system is via the Network and Sharing Center. To open it, go to Control Panel and click "View network status and tasks" under "Network and Internet".
Disable ipv6 step 1
Click your connection (in our case, "Ethernet").
Disable ipv6 step 2
In your connection status window, click "Properties".
Disable ipv6 step 3
In your connections properties window, find "Internet Protocol Version 6 (IPv6)" and unmark the checkbox to disable it. Click "OK" to save changes and see if this helps to fix the "DNS server is not responding" error.
Disable ipv6 step 4
Reset Your Router
Simply restarting your router or modem may help to fix this problem. We suggest you try this possibility first. If there is an "On/Off" button on your router, simply press it to turn off your router, wait a while, and then turn it on again. If there is no button on your router, disconnect it from power supply. When your router has restarted, try restarting your computer as well and see if this helps.
There might be a problem with your router configuration - this can also cause this "DNS server is not responding" error. To fix it, reset the router to its default settings. Open your router's configuration web page and find the "Reset" option. If you cannot access the router's web-based setup page and you want to reset the router to its default factory settings, press and hold the Reset button for 10 seconds. Bear in mind that resetting your router to its default factory settings will also reset your router's password.
Enter MAC Address Manually
A Media Access Control address (MAC address) of a device is a unique identifier assigned to network interfaces for communications at the data link layer of a network segment. MAC addresses are used as a network address for most IEEE 802 network technologies, including Ethernet and Wi-Fi. MAC addresses are used in the media access control protocol sublayer of the OSI reference model. These MAC addresses are often assigned by the manufacturer of a network interface controller and stored in its hardware such as the card's read-only memory or other firmware mechanism. To fix the "DNS server is not responding" error, you will need to enter the MAC address manually, but first you need to find it using an elevated Command Prompt and one of the commands.
Command Prompt is the input field in a text-based user interface screen, a command line interpreter application available in most Windows operating systems. It is used to execute entered commands, most of which are used to automate tasks through scripts and batch files, perform advanced administrative functions, troubleshoot and solve certain types of Windows issues. In the early days of computing, Command prompt used to be the only way to interact with the computer, so a basic set of commands with rigid syntax was developed to perform all system functions. Command Prompt's official name is Windows Command Processor but it is also sometimes called the command shell or cmd prompt, or even referred to by its filename cmd.exe.
To use Command Prompt, you must enter a valid command along with any optional parameters. It then executes the command as entered and performs its specific Windows task or function. Some commands available in Windows require that you run them from an elevated Command Prompt i.e. with administrator level privileges. The command we need to use requires an elevated Command Prompt to be opened with administrator privileges. To open elevated Command Prompt type "command prompt" in Search and right-click the "Command Prompt" result. Choose "Run as administrator" to run it with administrative privileges.
Enter Mac address manually step 1
When you select "Run as administrator", a User Account Control prompt will appear asking if you allow the Command Prompt to make changes to your computer. Click "Yes".
Enter Mac address manually step 2
Elevated Command Prompt will appear. In opened the Command Prompt window, type the "ipconfig /all" command and press Enter on your keyboard. You will see a list of information about the configuration. Find "Physical Address" and take a note of it somewhere - you will need it to proceed to the next step.
Enter Mac address manually step 3
Now that you have your MAC address, you can configure your network connection manually. To do so, Right-click on the Start menu and select "Network Connections", or go to Settings and click "Network & Internet".
Enter Mac address manually step 4
In the Network & Internet settings window, select your connection type (in our case, "Ethernet") on the left pane and then click on "Change adapter options" on the right pane.
Enter Mac address manually step 5
Right-click on your connection and select "Properties" from the drop-down menu.
Enter Mac address manually step 6
In the Properties window, select "Client for Microsoft Networks" (it should be selected automatically) and click "Configure".
Enter Mac address manually step 7
Now select the "Advanced" tab and then select "Network Address" under "Property:" Select "Value:" on the right pane and enter your MAC address (Physical Address), which you received when you entered the "ipconfig/ all" command in Command Prompt.
Enter Mac address manually step 8
Click "OK" to save the changes and see if this helps to fix the "DNS server is not responding" error. There is a higher chance that it will be fixed if you were using Google DNS before entering the MAC address manually.
Reset Your IP And Clear DNS Cache
This method includes entering and executing "netsh" and "ipcofig" commands into Command Prompt.
Netsh is a command-line scripting utility that allows you to, either locally or remotely, display or modify the network configuration of a computer that is currently running. Netsh also provides a scripting feature that allows you to run a group of commands in batch mode against a specified computer.
Ipconfig is a command-line tool that displays the current configuration of the installed IP stack on a networked computer. Using tool, we can flush and reset the contents of the DNS client resolver cache and renew DHCP configuration.
The commands require an elevated Command Prompt opened with administrator privileges. To open elevated Command Prompt, type "command prompt" in Search and right-click on the "Command Prompt" result. Choose "Run as administrator" to run it with administrative privileges.
Reset ip and clear dns cache step 1
When you select "Run as administrator", a User Account Control prompt will appear asking if you allow the Command Prompt to make changes to your computer. Click "Yes".
Reset ip and clear dns cache step 2
Elevated Command Prompt will appear. In the Command Prompt window, type these commands:
netsh int ip reset
netsh winsock reset
ipconfig /flushdns
ipconfig /renew
Press Enter on your keyboard after entering each command. When all commands are executed, restart your computer and see if this helps to fix the "DNS server is not responding" error.
Start Your Computer In Safe Mode
Safe Mode is a diagnostic start-up mode in Windows operating systems used to obtain limited access to Windows when the operating system does not start or function normally. It is the opposite of Normal Mode, which starts Windows in the usual manner. Safe Mode is available on Windows XP, Windows Vista, Windows 7, Windows 8, Windows 10, and most older versions of Windows.
One of the most common steps when troubleshooting a computer is to boot into Safe Mode. Safe Mode starts Windows in a basic state, using a limited set of files and drivers. It can help to troubleshoot problems on your computer. Read this article about how to boot your Windows 10 into Safe Mode.
Check if you are still having network connection problems when Windows starts in Safe Mode. If there are no problems with the network connection, you probably have third-party software installed in Windows that is causing the problem. Third-party applications can affect the DNS - almost any network-related or security application can interfere with your DNS, so find the problematic software and uninstall (or re-install) it.
Update Your Drivers
By update we mean that you should install the latest network adapter drivers on your computer. This problem might be caused by an old or incorrect driver. In this case, you need to get an updated/new driver for your network adapter. There is an easy way to do this automatically with Snappy Driver Installer. You will need a computer with a working internet connection in order to download it.
Snappy Driver Installer (SDI) is a powerful free driver updater tool for Windows that can store its entire collection of drivers offline. Having offline drivers gives Snappy Driver Installer the ability to have access to fast driver updates, even if there is no active internet connection. Snappy Driver works with both 32-bit and 64-bit versions of Windows 10, Windows 8, Windows 7, Windows Vista, and Windows XP. Drivers are downloaded through Snappy Driver Installer in what are called driverpacks, which are just collections (packs) of drivers for various hardware like sound devices, video cards, network adapters etc. It can also show duplicate drivers and invalid drivers and it separates the updates that require you to restart your computer so it would be easier to distinguish them from the rest. You can download Snappy Driver Installer from here.
Update drivers step 1
After you have finished updating and installing drivers, restart Windows 10 for them to take effect and try to connect to the internet to see if it works.
You can also update your drivers manually, but you will need a computer with a working Internet connection. Go to the network adapter manufacturer's website and download the latest driver, copy it onto your USB drive. Go to Device Manager (type "device manager" in Search and open it). Expand the "Network adapters" section, select your network adapter, right-click on it, and then choose "Update Driver".
Update drivers step 2
You will be asked how do you want to search for drivers and given two options: 1) to search automatically for updated driver software, and; 2) to browse your computer for driver software. The first option requires an Internet connection. Since you have problems with your Internet connection, choose the second option. Locate the driver on your USB drive and follow the instructions.
Update drivers step 3
When you have finished installing the new/updated driver, restart your computer for the changes to take effect and see if the network connectivity problem is fixed.
Disable Your Antivirus
The "DNS server is not responding" error can occur due to installed antivirus software. Temporarily disabling it might help to fix the problem. If disabling the antivirus software fixes the problem, you might want to consider switching to a different antivirus program. This error usually occurs when you have installed third-party antivirus software, but you should not be concerned about your safety, since the built-in Windows Defender software should be adequate.
Disable Secondary Connections
If you have more than one network connection available on your computer, try disabling the other connections and leave only the current connection enabled. Go to Network Connection settings. Right-click the Start menu and select "Network Connections", or go to Settings and click "Network & Internet".
Disable secondary connections step 1
In the Network & Internet settings window, select your connection type (in our case, "Ethernet") on the left pane and then click "Change adapter options" on the right pane.
Disable secondary connections step 2
Right-click on the other connection and select "Disable" from the drop-down menu. Apply this to all secondary
Disable secondary connections step 3
Disable Windows Update Peer-to-peer Feature
Windows 10 has a new feature that helps to save download bandwidth. It is a new peer-to-peer (P2P) delivery update mechanism. Using the P2P option, you can download a Windows update once, and then use that machine to spread the update to all computers on your local network, you can also download Windows updates from other users in your area. This feature can interfere with the DNS, and disabling it might fix the "DNS server is not responding" error. To disable this feature, go to Settings and select "Update & Security".
Disable windows update peer to peer feature step 1
Locate "Advanced options" under "Update settings" and click it.
Disable windows update peer to peer feature step 2
In the Advanced options window, click "Delivery Optimization".
Disable windows update peer to peer feature step 3
In the Delivery Optimization window, turn off the "Allow downloads from other PCs" option by toggling the switch. Check if the "DNS server is not responding" error persists.
Disable windows update peer to peer feature step 4
We hope that the methods described above helped you to fix the "DNS server is not responding" error and you are now able to connect to the Internet without any network connection problems. If none of the above solutions worked, the error might be caused by your Internet service provider. Wait until your Internet service provider fixes the technical issues and try connecting to the internet after few hours.
Hope this helps pal. Greetings!
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.
I'm running activator h2-browser command in a ubuntu 14.04 system in a directory containing associated files of a play framework project. when that command is executed my web application is running on localhost:9000. after running activator h2-browser in the root directory of my project I get the following message in terminal:
[info] Loading project definition from /XXXX/project
[info] Set current project to XXXX (in build file:/XXX/)
TCP server running at tcp://127.0.1.1:9092 (only local connections)
PG server running at pg://127.0.1.1:5435 (only local connections)
Web Console server running at http://127.0.1.1:8082 (only local connections)
after executing that command 127.0.1.1:8082 is opened. I expect to see the h2-browser but actually I get The connection was reset on firefox.
how can I possibly fix it?
Mine worked just as said in documention:
You can browse the contents of your database by typing h2-browser at the play console. An SQL browser will run in your web browser.
To get into play console, I tried activator first and then at the prompt, entered h2-browser.
Running activator h2-browser
has the same effect for me as for the OP. I also tried following the statement on the documentation, so I tried to get into play console by typing "activator", but that seems to start the application and leaves me with three [info]s, the last being
a.e.s.Slf4jLogger - Slf4jLogger started
and no way to enter h2-browser.
Edit: The answer was already posted here! Continuous mode did it for me.
I'm trying to remote debugg a chrome instance using the remote debug option in chrome:
chrome.exe --remote-debugging-port=1337
as described on google page: http://code.google.com/chrome/devtools/docs/remote-debugging.html
the problem is when i try to access it using IP it doesn't work, while testing it with localhost:1337 does work.
any idea?
You can setup an SSH tunnel in order to debug remotely. On the source machine execute:
ssh -L 0.0.0.0:9223:localhost:9222 localhost -N
Then on the other machine point Chrome browser to http://source-machine-ip:9223
I don't think Chrome accepts connections from outside of localhost (for security reasons).
I would suggest you have to build small proxy on the same host where Chrome is.
The following worked for me when running a Chrome remote debugging host on Windows 8.
Add an Inbound Rule to Windows Firewall
Search for "Windows Firewall" and select the "Windows Firewall" result
On the left of the "Windows Firewall" control panel window, click "Advanced Settings". This will open up "Windows Firewall with Advanced Security".
In the tree view on the left, click "Inbound Rules"
On the far right, click "New Rule..."
Select "Port" (Click Next)
Select TCP and set "Specific local ports" to 9222 (Click Next)
Select "Allow the connection" (Click Next)
Choose the profile access (Domain, Private, Public) to suit your needs (Click Next)
Give it a name like Chrome Remote Debugging (9222) (Click Finish)
Follow user3445047's instructions on port forwarding:
Run Chrome on the Windows host:
chrome.exe --remote-debugging-port=9222
Set up port forwarding on the Windows host:
Open up a cmd window. You must "Run as administrator".
Enter the following into the cmd window:
netsh
interface
portproxy
add v4tov4 listenport=9222 connectaddress=127.0.0.1
On the client, navigate to http://THE_HOST_IP_ADDRESS:9222 and you should be presented with a list of "Inspectable Pages".
The easiest way of sharing your debugging session with another computer is with socat.
For example, if you've enabled the remote debugging protocol on port 1337 using
chromium --remote-debugging-port=1337
Then, you can create a tunnel using socat,
socat tcp-listen:5656,fork tcp:localhost:1337
After doing this, anyone can just visit http://<YOUR_IP_OR_HOSTNAME>:5656/ and immediately use the debugger.
When you're done, press Ctrl + C to terminate socat and thus stop the tunneling.
If the previous code does not work, check whether the firewall (e.g. iptables) is blocking access. If the firewall is OK, check whether the IP address or host name is actually correct. To see whether the traffic is correctly forwarded/tunnelled, visit http://localhost:5656/ and verify that there's a Webkit debugger instance running.
Start the headless server
chrome.exe --remote-debugging-port=9222
Set up Port forwarding on windows
netsh interface portproxy add v4tov4^
listenport=9222 listenaddress=0.0.0.0^
connectaddress=127.0.0.1 connectport=9222
recent Chrome versions support the commandline switch "--remote-debugging-address" so the workarounds listed above should no longer be necessary.
Here the description:
"Use the given address instead of the default loopback for accepting remote debugging connections. Should be used together with --remote-debugging-port. Note that the re-mote debugging protocol does not perform any authentica-tion, so exposing it too widely can be a security risk."
You can create simple TCP proxy with netcat:
EXTERNAL_PORT=1338
CHROME_DEBUG_PORT=1337 # This is the port specified with --remote-debugging-port
nc -l -p ${EXTERNAL_PORT} -c "nc 127.0.0.1 ${CHROME_DEBUG_PORT}"
Try changing port number
That works for me.