Hi I successfully run my webapp in STS builtin tc Server.
I can access it from localhost but not from remote computers.
Any ideas?
I think it is not a problem with spring / tc Server.
try to ping the server from your remote computer
get the IP of your server with ipconfig then try to ping it
ping http://10.xx.xxx.12/yourapp
Then check if you have any firewall that blocks the incoming network traffic.
or other program such as Norton / Symantec antivirus that include a "Network Security Threat" feature to block the traffic.
If you have such program, create a rule to grant access to the clients you want to access your server
Related
Currently I am using SwiftNIO and have a echo server and client. I was using SquidMan to create a local proxy, then I configured the proxy on my machine via system preferences. When I look at my Wireshark captures, I only see packets go directly from my client to my server and vice-versa. How can I configure it so that my client must go through the proxy first?
Note: I've also tried running my server on a VM and running a proxy on a separate Windows Laptop on my Network.
When I go to System Preferences -> Advance -> Network -> Proxies on my Mac I configured HTTPS/HTTP to point to the proxy I have running on my Windows Laptop. Is there something more I have to do?
on the machine running SwiftNIO echo server/client service, repoint your TCP/IP default gateway to the address of your Proxy server....proxy server will then NAT translate for your SwiftNIO and return correct packets on your behalf
I may not be understanding your issue, but this seems easy
I have a few virtual machines that are set up on bridge network. One of this virtual machines (HDP sandbox) has the web ui and I wanna use it but it's IP is not opened on the browser. What's should i do?
As i understand it,your vm has a web server.if so,check the status of apache service.If it is not running,you have to start it.
service apache2 status
service apache2 start
after you run the commands above(command may be different due to linux distro),
enter ip address into the web browser.
also,you must be sure that HDP services are running.
I don't have a public ip address so I'm looking to host a server while connected to a VPN, the VPN server is running on a VPS that I own and its running SoftEther VPN server.
In my machine I connect to the VPN and then run the server app, however I check in http://www.canyouseeme.org/ to see if its successfully hosted and can be accessed from internet but its not and it shows "connection refused", if I host the server on the VPS machine it works, but I don't want that, it should be hosted on my machine and should be accessible using the ip address of the VPS/VPN.
You probably want to set up port forwarding on your VPN server.
When you connect to the VPN, your traffic goes through it, but you don't "become" it - the traffic directed to the VPN server (like an attempt to connect to your app) will not be forwarded to your VPN client machine - this is not the purpose of VPNs.
There is a page with port forwarding setup here. This is to be done on the VPN server.
The alternative I use is to setup port forwarding via SSH on the application server and ditch the need for VPN. Check Remote Port Forwarding here. It works fine, encrypts your data between the application server and the gateway, but there might be bigger overhead and it may be more prone to die when the network connection is temporarily lost.
I have got chef-server installed on a centos machine.
Everything is working as expected except that I cannot access the chef-server web interface from another machine on my local network.
I can access the web interface from the centos machine itself:
telnet mychefserver.local 4000
Connected
If I do the same from my machine I have got:
telnet: Unable to connect to remote host: No route to host
I can successfully ping mychefserver.local from my machine
Any idea how to configure nginx with chef-server to access the chef-server from the network?
Since Chef Server 10, the web interface uses normal HTTPS (TCP 443), it only listens on the high ports locally, and nginx proxies as needed to the different backend services. I would try with a normal web browser as telnet isn't exactly great at error messages. Normally I would expect that to mean telnet is getting TCP transmission errors, but maybe it is just confused? If it is really a TCP transmit error then more likely the internal DNS is having issues. .local often means mDNS which has uneven support in some places, I would try an actual IP address to be sure.
My issue was iptables.
I stopped iptables and I can access the chef-server from my local network again.
I deployed a web site into a Azure VM and did the following
1) Create a HTTP Endpoint with TCP protocol and port 80 (both
internal and external) for the VM
2) configure the web site to be assigned with the internal IP
assigned
I can browse to the site within the VM, but can not connect to it from external using either the DNS or the public VIP assigned by Azure. the browser said "can not connect to [vip]".
Have I missed any steps or any advice on how to trouble shoot this issue?
If this is a "normal" VM and not a Cloud Service then you need to connect to the VM and open port 80 in the Windows Firewall directly on the machine as well.
In the end, i found it is caused by the selection of "direct connect" at the Endpoint setting.
Untick it, it works...