I'm following the Micro cloud Foundry Quick-Start guide here:
http://support.cloudfoundry.com/entries/20316811-micro-cloud-foundry-getting-started-guide
I'm on step 10: registering a new user and I'm not able to connect:
$ vmc target api.lsmith.cloudfoundry.me Host is not available or is
not valid: 'http://api.lsmith.cloudfoundry.me' Would you like see the
response? [yN]: y HTTP exception: Errno::ECONNREFUSED:Connection
refused - connect(2)
My VM is in NAT mode. The Current Configuration in my VM is listed as:
Current Configuration: Identity: lsmith.cloudfoundry.me (ok) IP
Address: 172.16.x.x (network up)
When I run the host command in my console I get:
$ host api.lsmith.cloudfoundry.me api.lsmith.cloudfoundry.me is an
alias for lsmith.cloudfoundry.me. lsmith.cloudfoundry.me has address
127.0.0.1
I'm not able to reach the vmc target in my browswer but when I visit http://172.16.x.x/info I get:
VCAP ROUTER: 404 - DESTINATION NOT FOUND
I think this is a DNS issue but have no idea what I need to do to fix it. I tried changing the nameserver IP in my /etc/resolv.conf from 127.0.0.1 to 172.16.x.x but that didn't work.
I was able to resolve this by reconfiguring my domain (option 4 in the VM) using a newly generated domain token at https://micro.cloudfoundry.com/dns
Related
I am facing one error while installing FCL-CLI on my system (linux).
The command I have used is : sh -ci "$(curl -fsSL https://raw.githubusercontent.com/onflow/flow-cli/master/install.sh)" .
Error: curl: (28) Failed to connect to raw.githubusercontent.com port 443...NEED HELP!
Set DNS 8.8.8.8 in network will resolve this
Faced the same issue while trying to install nvm on ubuntu. Following steps solved my issue:
1)Open the /etc/hosts file using
$ sudo nano /etc/hosts
2)Enter your password.
3)Add the following IP address at the end of the file:
185.199.108.133 raw.githubusercontent.com
4)Save and close the file.
5)Now Try installing Again.
This my fix your problem.
Change from network in setting.
Open the /etc/hosts file using
$ sudo nano /etc/hosts
and then add following IP
185.199.108.133 raw.githubusercontent.com
save it and reinstall it again
For Windows Users:
Go to the Control Panel.
Click Network and Internet > Network and Sharing Center > Change adapter settings.
Select the connection for which you want to configure Google Public DNS. For example:
3.1 To change the settings for an Ethernet connection, right-click the Ethernet
interface and select Properties.
3.2 To change the settings for a wireless connection, right-click the Wi-Fi
interface and select Properties.
If you are prompted for an administrator password or confirmation, type the password or provide confirmation.
Select the Networking tab. Under This connection uses the following items, select Internet Protocol Version 4 (TCP/IPv4) or Internet Protocol Version 6 (TCP/IPv6) and then click Properties.
Click Advanced and select the DNS tab. If there are any DNS server IP addresses listed there, write them down for future reference, and remove them from this window.
Click OK.
Select Use the following DNS server addresses. If there are any IP addresses listed in the Preferred DNS server or Alternate DNS server, write them down for future reference.
Replace those addresses with the IP addresses of the Google DNS servers:
For IPv4: 8.8.8.8 and/or 8.8.4.4.
For IPv6: 2001:4860:4860::8888 and/or 2001:4860:4860::8844.
For IPv6-only: you can use Google Public DNS64 instead of the IPv6 addresses in the previous point.
Test that your setup is working correctly; see Test your new settings.
Repeat the procedure for additional network connections you want to change.
Ref: [https://developers.google.com/speed/public-dns/docs/using][Configure your network settings to use Google Public DNS]
Use a VPN or go to 1.1.1.1 in your browser and use WRAP by Cloudflare. Worked for me 👍
I have set up a VPN to an Azure IKEv2 gateway following instructions from these sites:
full tutorial
Create Certificate
I had originally used the StrongSwan Gui version but after checking found that none of the configuration mentioned in the cli version had been completed so I worked through the cli version. When I start the VPN I get no errors and I can see logs in syslog that indicate the connection is set up. When I browse to a page that I need the connection for I get an error page stating DNS error. It has connected on more than one occasion and I have used the page but then if I turn it off and start it up again it does not work. I haven't found a pattern for it working yet and seems to be genuinely random.
I am on Ubuntu Linux
inxi -S
System: Host: lg-MS-7A71 Kernel: 4.15.0-51-lowlatency x86_64 bits: 64 Desktop: Gnome 3.28.3
Distro: Ubuntu 18.04.2 LTS
inxi -i
Network: Card: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169
IF: enp3s0 state: down mac: 30:9c:23:61:4b:25
WAN IP: 2.124.241.7
IF: enp3s0 ip-v4: N/A ip-v6-link: N/A
IF: docker0 ip-v4: 172.17.0.1 ip-v6-link: N/A
IF: wlxbcec23c34e3a ip-v4: 192.168.0.20 ip-v6-link: fe80::96fb:6e3b:1233:79dc
not sure if it is clear from that but I don't use the on board network card and instead have a usb wifi adapter installed.
lshw (irrelavant removed)
*-network:0
description: Wireless interface
physical id: 2
bus info: usb#1:8
logical name: wlxbcec23c34e3a
serial: bc:ec:23:c3:4e:3a
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=rtl88x2bu ip=192.168.0.20 multicast=yes wireless=IEEE 802.11AC
I did try to switch to the on board network interface but that wasn't an improvement so I just kept trying to work on the wifi.
I have no idea what is wrong here but the connection is being made I am sure of it. When viewing the syslog I can see the subnet address I have been given from Azure which is also listed on the dashboard when I have connected. So it must be connecting except that if I ping the test address I have it does not resolve. That leaves the certificates or my configuration/set up. If the certificates were bad I would not connect (I don't think) so what do I need extra on my set up.
It is almost as though the connection is good but the link between my browser and the network doesn't recognise it. Is this possible?
[edit: more info]
I have gone through this again with more detailed instructions and I an now sure that I am connecting to the azure vpn but I am not getting the dns servers added:
adding DNS server failed
adding DNS server failed
handling INTERNAL_IP4_DNS attribute failed
adding DNS server failed
handling INTERNAL_IP4_DNS attribute failed
installing new virtual IP 172.20.20.130
CHILD_SA dv0_vnet{1} established with SPIs cd6f6be2_i 8c59932a_o and TS 172.20.20.130/32 === 10.216.0.0/17 172.20.20.0/24 183.3.0.0/22 183.3.5.128/25 183.3.6.0/25
connection 'dv0_vnet' established successfully
Finally I have figured this out. The last problem I had was a DNS problem setting dns server from Azure gateway. To fix this I had to install resolvconf and configure it for dynamic updates.
I had to:
install and configure strongswan (best instructions I found)
set mss/mtu in the charon configuration (as mentioned in this
post)
Install & configure resolvconf (as in answer here)
Set up network manager vpn (The graphical element for top right of
menu)
when that is done I bring up the connection
sudo ipsec up <vpn name as in ipsec.conf>
start the network manager client
and then I can browse to my test site in the vpn.
I am installing eucalyptus 4.4.4 on centos 7 and i have done all the installation steps but DNS is still not working. When i using ping to check it is showing error that cannot find service.
To check the status of the eucalyptus dns service you can use:
# euserv-describe-services --filter service-type=dns --expert
SERVICE arn:euca:bootstrap:api.10.117.111.14:dns:api.10.117.111.14.dns/ enabled 21 http://192.168.111.14:8773/services/Dns
If the service is not enabled then the most likely reason is that another service is installed and using the dns port.
If the service is enabled then you can check the output using dig:
dig +short ec2.internal #192.168.111.14
192.168.111.14
In this example my dns and ec2 (compute) services are on the same host.
If you see a response such as:
Warning: query response not set
from the dig command then you may not have enabled dns functionality, to check and then enable dns run:
# euctl dns.enabled
# euctl dns.enabled=true
It is also a good idea to review other setting described in the documentation to verify dns settings:
http://docs.eucalyptus.cloud/eucalyptus/4.4.5/index.html#shared/setting_up_dns.html
We have deployed a K8S cluster using ACS engine in an Azure public cloud.
We are able to create deployments and services but when we enter a pod using "kubectl exec -ti (pod name) (command)" we are receiving the below error,
Error from server: error dialing backend: dial tcp: lookup (node hostname) on 168.63.129.16:53: no such host
I looked all over the internet and performed all I could to fix this issue but no luck so far.
The OS is Ubuntu and 168.63.129.16 is a public IP from Azure used for DNS.(refer below link)
https://blogs.msdn.microsoft.com/mast/2015/05/18/what-is-the-ip-address-168-63-129-16/
I've already added host entries to /etc/hosts and entries into resolv.conf of the master/node server and nslookup resolves the same. I've also tested by adding --resolv-conf flag to the kubelet but still it fails. I'm hoping that someone from this community can help us fix this issue.
Verify the node on which your pod is running can be resolved and reached from inside the API server container. If you added entries to /etc/resolv.conf on the master node verify they are visible in the APIserver container, if they are not, restarting the API server pod might be helpful
The problem was in VirtualBox layer
sudo ifconfig vboxnet0 up
Solution is taken from here https://github.com/kubernetes/minikube/issues/1224#issuecomment-316411907
Hi StackOverflow members,
I have an issue with ssh connection on my Debian 7 system to a remote OpenSSH server located on the same network. It looks like there is some network configuration problem but I cann't find where it lays. This two debian machines are connect with a switch that is NOT connected to a router. So the two machines have no internet connection.
A-Debian 7
IP: 192.168.1.2
MASK: 255.255.255.0
GW: 192.168.1.1
B-Debian 7
IP: 192.168.1.3
MASK: 255.255.255.0
GW: 192.168.1.1
With that configuration the ssh command prompts my for a password in less then a second. But the with the following network configuration I get the password prompt after a 10+ second delay:
A-Debian 7
IP: 10.10.1.83
MASK: 255.255.255.128
GW: 10.10.1.1
B-Debian 7
IP: 10.10.1.82
MASK: 255.255.255.128
GW: 10.10.1.1
The ssh connection from the server A -> B runs with both configs on custom 1111 port.
The B machine has also a Web server running on port 8080 that has no delays with both net configurations.
Thank you in advance for any clues or tips how to solve that problem.
SOLVED: Removing of the gateway parameter "GW: 10.10.1.1" in the network settings has solved the problem.
The usual culprits here are IPv6 and DNS lookups.
SSH might try to connect via IPv6, first, but the timeout is too low for that. You can see whether IPv6 is enabled with
cat /proc/sys/net/ipv6/conf/eth0/disable_ipv6
To disable:
echo 1 > /proc/sys/net/ipv6/conf/eth0/disable_ipv6
The second culprit is DNS; my guess is that DNS lookups don't work correctly with the second configuration. Try host www.google.com to test this theory.
If that also has a delay, you need to fix your DNS setup.
If that's not it, check the rest of your networking parameters: Gateway, cables, etc.
Start to ping the other host. Is that fast & reliable?
Next, try remote login (ssh, telnet). Note that you can give telnet a port to connect to, so if you have DB server running, you can still use telnet to connect to the server. It will print an error but it allows you to test the TCP/IP connection without any extra error sources.