I am running this example http://kaaproject.github.io/kaa/docs/v0.10.0/Programming-guide/Your-first-Kaa-application/ .
But data is not storing on the server side.
What should I do now?
When I running db.logs_my_application_token.
find() from mongo console,
it is showing nothing.
Do I have to provide some IP or host in my code, I am using KAA SANDBOX from AWS.
Console Output of Raspberry Pi attachedenter image description here here...
Finally I am able to do that using ..
Perform these two steps may be this can solve your problem.
Just run this command on host machine
sudo /usr/lib/kaa-sandbox/bin/change_kaa_host.sh $new host name/ip$
Then change the IP address of using Admin UI, for that you need to
sign in using username : kaa and passwword : kaa123
then go to setting > general setting then change the IP address preceded by :8080, enter your machine's public IP address, that can be easily accessible from anywhere.
Tips :: if you are using AWS instance then use public IP address of your instance.
Further error persist then drop your previous instance and launch a new instance.
For more details go the official documentation page
Hope it will be helpful for you.
You do not need to provide IP address.
You should download the generated SDK file and compile it with the source code. and then run it.
Related
I install OpenVPN from its original source on google cloud instance and installed correctly. it is working and connect from OpenVPN client and also change IP of PC but when I type example google.com no open
but when I type any IP address of any working server it shows and opens websites from IP but not domain.
As you are able to browse with IP but not with DNS name it seems like a DNS resolver issue. For this reason,I would start troubleshooting by checking the internal name resolver
cat /etc/resolv.conf
What we are looking in here is the information about the name server your are using.
At this point you might want to check "~/client-configs/base.conf" file as per the OpneVPN configuration documention:
Finally, add a few commented out lines. We want to include these with
every config, but should only enable them for Linux clients that ship
with a /etc/openvpn/update-resolv-conf file. This script uses the
resolvconf utility to update DNS information for Linux clients.
"~/client-configs/base.conf
"# script-security 2"
"# up /etc/openvpn/update-resolv-conf"
"# down /etc/openvpn/update-resolv-conf"
If your client is running Linux and has an
/etc/openvpn/update-resolv-conf file, you should uncomment these lines
from the generated OpenVPN client configuration file.
I would also check the OpenVPN "/etc/openvpn/server.conf" and make sure DNS configuration in plance. It would be also worthwhile to check network configuration specially IP forwading and make sure default route going out through intended interface
As per "How To Set Up an OpenVPN Server on Ubuntu 16.04" document the recommendation is:
Your public interface should follow the word "dev". For example, this
result shows the interface named wlp11s0, which is highlighted below:
default via x.x.x.x dev wlp11s0 proto static metric 600
I have a google VM. I got public as well for the same (using which I am RDP'ing to that VM). But when I am trying to access any webservice hosted in VM from outside world using ip:port, it is not connecting to that webservice.
To be more precise :
I have hosted a sample webservice using nodejs on port 8080.
I have tried accessing http://:8080 . No luck. But it is working with localhost:8080 inside VM.
I have googled about external ip etc, but all went out of my head. Can any one please help me how to resolve this issue ? do I need to make any config changes etc? if yes, could you please provide me the required steps.
Update :
I have created fire wall rule saying : port : allow all, target tags : all instances, IP : 0.0.0.,0/0 . even then it is not working.
OS : windows 10
As I understand, the GCP firewall rules are applicable on the network level. You might need to configure the virtual machine specific firewall rules (according to the OS you are using). For example, in CenOS you may need to use firewall-cmd commands to configure the internal firewall.
Finally solved this. All the time I was thinking to enable port in networks for google cloud, but the problem is at my windows firewall. once I disabled it, I could access my webserver from outside environment.
I have two instances. They are going to run the same app, but one is set up with a slightly different configuration. Right now I can go to their assigned elasticip and see that my site works on both. Th eonly other difference is that one is a micro instance and one is a small instance. Also, I have a bunch of DNS records pointing my domain name to the ip of the micro instance.
But what I want to do is swap them so that the small instance is now my main instance that has my domain pointing to it. I was hoping I could just disassociate the ip's and then reassociate the ip's only flipped around. But when I do that and then try to go to my domain.com I just get an error page. When I swap them back they both seem to work again. Is there something a more complicated I have to do?
edit:
When I try to SSH I also get all this stuff:
###########################################################
# WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! #
###########################################################
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
d6:ed:23:65:9c:da:0c:1b:2d:94:34:18:4d:68:8f:a5.
Please contact your system administrator.
Add correct host key in /Users/croberts/.ssh/known_hosts to get rid of this message.
Offending RSA key in /Users/croberts/.ssh/known_hosts:17
RSA host key for 54.183.212.154 has changed and you have requested strict checking.
Host key verification failed.
Something nasty! haha.
The error message is indicating that the remote computer does not match the computer previously recorded in the known_hosts file.
When using ssh, each computer generates a fingerprint and this is recorded against the computer identifier (eg IP Address) that you are using to connect to the remote machine.
If you are switching an Elastic IP address between instances and also using the Elastic IP address to ssh into the instance, then the error quite correctly is warning you that the computer is not the same computer to which you last connected on that address.
You can remove the offending entry from the known_hosts file, or even delete the whole known_hosts file (which admittedly will remove such warnings even if they are legitimate).
You should have no problem swapping the elastic IP from one instance to another. It can take a few minutes to take effect, so make sure that you can reach the correct instance before testing.
You don't describe the error, but if you are using name-based virtual hosts, and are using a different name, that could be one cause. If you restart apache after swapping EIPs, does the problem go away?
Finally, to fix the ssh error, remove the entry from the known_hosts file - if you read the error message, it's on line 17.
I am migrating my vCenter Server 5.5 to a new server (databases have already been moved to a new SQL server and all is OK on existing vCenter Server 5.5 implementation). When I begin the simple install process on the new vCenter Server host the Single Sign-On component presents me with an IP address of 10.10.10.117 as the ip address of the FQDN file01.xxxxxxxxx.com. This is the iSCSI interface address. I need it to use the 10.1.1.17 ip address that is the address of the production NIC that the ESXi 5.5 hosts will be communicating with. I have already changed the binding order of the NIC cards and flushed the DNS cache. I also added file01.xxxxxxxx.com with the proper IP address to the hosts file and also file01 to the hosts file. Still, during the install, 10.10.10.117 is discovered. Thanks in advance! Babak C.
Just to get a quick clarification...are you freshly installing vCenter 5.5? Or are you migrating an existing vCenter server to a new host and using the update utility to upgrade? I am assuming you are doing a fresh install based on your details about the SQL server and SSO. Here is my suggestion, in case it is a fresh install.
We had a similar problem with 5.5 on a new install where the IP address that was discovered during the actual vCenter Server install was that of the public facing NIC which we never use for management traffic (it's for internet access on the vC server, for update manager, etc.)
The strange thing is that there had NEVER been an entry in ANY of our DNS servers for that interface. So, after looking into it a little bit, I started thinking the IP that was returned during install was not a DNS result at all. Rather, it was (most likely) simply gathered from the interfaces on the Server based on binding order (e.g. which NIC has the default gateway.)
In order to save having to uninstall and clean up a major mess if the install completed wrong, we stopped and got in touch with VMware support. They suggested we clear all of the temporary files both in the standard "temporary" folder on windows as well as under /ApplicationData/vmware/xxx, where 'xxx' would be whatever product is giving you trouble and HAS NOT been FULLY INSTALLED* (e.g. you started the install and noticed the incorrect IP, so you terminated the installer and there is metadata and cached files remaining from the partially run install).
Basically, what we had to do, was clear the temporary files and then make sure the NIC Binding Priority was correct (so you should check in Network Adapters|(press-alt)|Advanced Settings. Make sure the correct binding is checked (e.g. if you don't use IPv6 on the private network, clear it) and make sure that the Windows Network is at the top of the priority list on the second pane of the advanced settings. This helps tremendously with SSO by making sure the Windows Network stack is the first queried when you are signing in and SSO must submit a kerberos ticket to the AD DC for validation.
It is possible, that once you delete the partial install files and temporary files and fix the network settings (probably be a good idea to reboot as well), the next time you run the installer you might have success.
I will try to check this post later to see if it helped you at all... or it I just succeeded in making your life even more difficult (which I certainly hope not!) :)
One more thing...prior to initializing the installer, open up a PS session, perform ipconfig /flushdns and then ping the hostname of your vCenter server in order to get it in the DNS cache. You should also perform the following:
nslookup
NS>{your vcenter server IP address}
/* make sure the resulting hostname is correct..this ensures your PTRs and rDNS is working correctly. vCenter HEAVILY relies on accurate reverse DNS configuration...then do the following lookup for forward DNS */
NS>{your vcenter server FQDN}
Hope it helps. Best of luck my friend!
SIETEC
Win7 PC running Rails in an Ubuntu VM via VMWare Player. I'm working on a site and would like to show it to a friend who's outside my network.
I found this blog post, which got me very close: http://blog.fardad.com/2012/06/vmware-player-and-custom-nat-port-map.html
OK, so I have the VM that is using NAT. As I understand it, that means that the VM will appear to have the same IP address as the parent machine to outside traffic.
I went into NAT settings and added port forwarding:
Host Port: 8200 Type: UDP Virtual IP Address: 192.168.198.184:3000
OK so my understanding is that I should now be able to go to 192.168.1.1xx:8200 (the IP of my 'real' PC) and access the webserver running in the VM. But when I go to that address, I don't get anything. I can ping 192.168.198.184 (the VM) from the PC.
What I want to be able to do is go into my router and set up a port that will eventually forward into the VM.
It seems like I'm missing something very small but I don't know what that is. Help, please.
If anyone is curious how to get the Virtual Network Editor:
go to the vmware-directory and run in elevated cmd.exe-box
rundll32.exe vmnetui.dll VMNetUI_ShowStandalone
http://communities.vmware.com/message/2155960#2155960
Find the vmnetnat.conf file, usually located in
C:\ProgramData\VMware\vmnetnat.conf
or
C:\Users\Application Data\VMware\vmnetnat.conf
Edit vmnetnat, add similar line in the [incomingtcp] section
8200=192.168.198.184:3000
Restart VMware NAT Service.
Try using Bridged network option in vmware player instead of NAT. It replicates your physical network.
You can use an http proxy to do that, by doing that you don't need to expose your entire private network, check out this blog post for more information how to access docker containers from external devices