ng-forward | default solution for those that want to write | Frontend Framework library

If you look at nmap output you can see the port is reported as filtered. That means one of these:

• The routing from Docker network (typocally 172.17. 0.0/16 ) is not setup correctly
• Each container is running it's own separate network with a overlapping subnet which prevents packets to route back correctly
• or there is a packet filter (iptables) which prevents which prevents packets to reach to the destination correctly.

What I need in addition to debug the issue, is route table (ip route), packet filter output (iptables -S), and docker inspect from each container.

Update:

These are the potential problems that I see:

Fix the current setup:

• You have -P FORWARD DROP in your iptables, this prevents the access, use: sudo iptables -P FORWARD ACCEPT to enable that.
• Please check sysctl net.ipv4.conf.all.forwarding that should be set to 1 if not edit /etc/sysctl.conf to fix that, and reload the settings with sysctl -p.

OR

• Alternatively you can use postgresql ip 172.17.0.4 to access the database.
• Another option is to set postgresql network to --net=host and then you should be able to get around the iptables.
• Alternatively you can connect your app to postgresql network by specifying --net=container: and use localhost to access the database.
• You can create a separate network in docker and run all the containers there so your are able to access from anywhere to anywhere without routing through your host IP

Probably there are a few other way to achieve this, but I leave it to you to figure out :)

Update 2:

-P INPUT DROP is also an issue, use this for fix it: sudo iptables -P INPUT ACCEPT

If you choose the first option for fix your current settings, make sure iptables changes are persisted otherwise you'll lose them on reboot. Consult your Linux distro manual for figure out how to do that.

There is an open issue tracking this (currently in the Github team's backlog).

The reason that this worked before is because in previous versions the resource definition automatically included a scope with the same name.

Please note, MyApi is here the scope name, which is equal to the resource name.

Using Steve Kinzler's align util:

Well it seems that Ubuntus default rules disallow https and just adding ufw on top doesn't solve it. So what I did was, reset the whole iptable to a clean state and then setup ufw and enable the the protocols that I need. Now it's configured correctly and https is accessible.

The problem is that in

Try the below fieldType for your field "VivaTour_TourName".

In Docker generally the localhost 127.0.0.1 address means "this container". If you start a server process and tell it to listen on 127.0.0.1, it will only accept connections originating from within the same container. You almost always want to set servers to listen on the magic 0.0.0.0 "all interfaces" address, at which point they will be able to accept connections from other containers and the host.

In your setup, this just involves changing the configuration value "server": {"ip": "0.0.0.0"}.

One of the keys to a successful upgrade is to do it incrementally, by running the two frameworks side by side in the same application, and porting AngularJS components to Angular one by one. This makes it possible to upgrade even large and complex applications without disrupting other business, because the work can be done collaboratively and spread over a period of time. The upgrade module in Angular has been designed to make incremental upgrading seamless.

For more information, see Angular Developer Guide - Upgrading from AngularJS

The DEMO on PLNKR